github-starred/android
2
0
Fork 0
mirror of https://github.com/bitwarden/android.git synced 2026-03-09 03:33:36 -05:00
Code Issues 144 Packages Projects Releases 116 Wiki Activity

[BWA-179] Export is now confusing for users and not clear what it does or does not #2304

New Issue
Open
opened 2025-11-26 23:15:01 -06:00 by GiteaMirror · 3 comments
GiteaMirror commented 2025-11-26 23:15:01 -06:00
Owner
Copy Link

Originally created by @pamperer562580892423 on GitHub (Aug 3, 2025).

Steps To Reproduce

  1. Prerequisite: have the TOTP sync between password manager/vault and authenticator app active - and the synced TOTP codes get shown in the authenticator app. (besides locally stored TOTP codes in the authenticator app)
  2. Go to the Authenticator app und "unlock" it.
  3. Go to Settings.
  4. Choose "Export" (and then either json or csv and follow through with the export)

Expected Result

The user gets informed, that the export only considers the locally stored TOTP seeds and DOESN'T include any synced codes.

Actual Result

There is no information about the fact that not "all" of your TOTP codes get exported (the synced one's don't get exported!), but only the locally stored TOTP codes get exported.

Ideally, not only should the authenticator app show, that the synced TOTP codes don't get exported, but that those codes are still only exported, when one makes an export of the BW vault via one of the password manager clients.

Screenshots or Videos

No response

Additional Context

I really do consider it as a (UI/UX) "bug", that the export function of the authenticator app wasn't "updated" in that regard, to make it transparent to the user what export does (or does not) now since the "sync" functionality is also available - and you can have two "kinds" of TOTP codes in the authenticator app (locally v. synced), but the export function doesn't take into account that new situation.

Build Version

2025.7.1 (601) --> authenticator app

What server are you connecting to?

EU

Self-host Server Version

No response

Environment Details

  • Fairphone 5
  • Android 15

Issue Tracking Info

  • I understand that work is tracked outside of Github. A PR will be linked to this issue should one be opened to address it, but Bitwarden doesn't use fields like "assigned", "milestone", or "project" to track progress.
Originally created by @pamperer562580892423 on GitHub (Aug 3, 2025). ### Steps To Reproduce 1. Prerequisite: have the TOTP sync between password manager/vault and authenticator app active - and the synced TOTP codes get shown in the authenticator app. (besides locally stored TOTP codes in the authenticator app) 3. Go to the Authenticator app und "unlock" it. 4. Go to Settings. 5. Choose "Export" (and then either json or csv and follow through with the export) ### Expected Result The user gets informed, that the export only considers the locally stored TOTP seeds and DOESN'T include any synced codes. ### Actual Result There is no information about the fact that not "all" of your TOTP codes get exported (the synced one's don't get exported!), but only the locally stored TOTP codes get exported. Ideally, not only should the authenticator app show, that the synced TOTP codes don't get exported, but that those codes are still only exported, when one makes an export of the BW vault via one of the password manager clients. ### Screenshots or Videos _No response_ ### Additional Context I really do consider it as a (UI/UX) "bug", that the export function of the authenticator app wasn't "updated" in that regard, to make it transparent to the user what export does (or does not) now since the "sync" functionality is also available - and you can have two "kinds" of TOTP codes in the authenticator app (locally v. synced), but the export function doesn't take into account that new situation. ### Build Version 2025.7.1 (601) --> authenticator app ### What server are you connecting to? EU ### Self-host Server Version _No response_ ### Environment Details - Fairphone 5 - Android 15 ### Issue Tracking Info - [x] I understand that work is tracked outside of Github. A PR will be linked to this issue should one be opened to address it, but Bitwarden doesn't use fields like "assigned", "milestone", or "project" to track progress.
GiteaMirror added the app:authenticatorbug labels 2025-11-26 23:15:02 -06:00
GiteaMirror commented 2025-11-26 23:15:02 -06:00
Author
Owner
Copy Link

@bitwarden-bot commented on GitHub (Aug 3, 2025):

Thank you for your report! We've added this to our internal board for review.
ID: BWA-179

@bitwarden-bot commented on GitHub (Aug 3, 2025): Thank you for your report! We've added this to our internal board for review. ID: BWA-179
GiteaMirror commented 2025-11-26 23:15:02 -06:00
Author
Owner
Copy Link

@pamperer562580892423 commented on GitHub (Oct 1, 2025):

I would like to add, that besides a change in the apps, it also needs an info about what can or is being exported and what isn't in the corresponding Help Site: https://bitwarden.com/help/authenticator-import-export/#export-data

@pamperer562580892423 commented on GitHub (Oct 1, 2025): I would like to add, that besides a change in the apps, it also needs an info about what can or is being exported and what isn't **in the corresponding Help Site**: https://bitwarden.com/help/authenticator-import-export/#export-data
GiteaMirror commented 2025-11-26 23:15:02 -06:00
Author
Owner
Copy Link

@pamperer562580892423 commented on GitHub (Oct 1, 2025):

BTW, here is another "victim" of this situation : https://community.bitwarden.com/t/bug-export-function-does-not-work-on-android-app/89576

@pamperer562580892423 commented on GitHub (Oct 1, 2025): BTW, here is another "victim" of this situation : https://community.bitwarden.com/t/bug-export-function-does-not-work-on-android-app/89576
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
app:authenticator
app:password-manager
bug
bug-passkey
customer-support
duplicate
enhancement
good first issue
help wanted
needs-reply
needs-response
pull-request
Mirrored from GitHub Pull Request
 question
No Label app:authenticator bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/android#2304
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?