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

When using the "sync" feature: Adding new TOTP seed codes "locally" is only possible with manually entering the seed code, not by scanning a QR code #2275

New Issue
Open
opened 2025-11-26 23:14:15 -06:00 by GiteaMirror · 1 comment
GiteaMirror commented 2025-11-26 23:14:15 -06:00
Owner
Copy Link

Originally created by @pamperer562580892423 on GitHub (Jul 7, 2025).

Steps To Reproduce

  1. Precondition: sync with at least one BW vault is active for the authenticator app.
  2. Open the authenticator app.
  3. Click on "+".
  4. Click on "Scan a QR code" / "Enter key manually".

Expected Result

I can choose whether to store the TOTP seed code locally in the authenticator app or in my password manager vault - regardless of choosing "Scan a QR code" or "Enter key manually".

Actual Result

When I choose "Scan a QR code", I can't choose to store it locally in the authenticator app - the BW password manager (mobile) automatically opens and wants to add the TOTP seed code to my BW vault.

Only when I choose "Enter key manually", I can then choose between "Store in Bitwarden (vault" or "Save here (locally in the authenticator app).

Screenshots or Videos

(I hope it is clear without screenshots)

Additional Context

As always, I don't know if the same thing happens on iOS...

Build Version

2025.6.0 (475)

What server are you connecting to?

EU

Self-host Server Version

(not self-hosting)

Environment Details

  • Fairphone 5
  • Android 14

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 (Jul 7, 2025). ### Steps To Reproduce 1. Precondition: sync with at least one BW vault is active for the authenticator app. 2. Open the authenticator app. 3. Click on "+". 4. Click on "Scan a QR code" / "Enter key manually". ### Expected Result I can choose whether to store the TOTP seed code locally in the authenticator app or in my password manager vault - regardless of choosing "Scan a QR code" or "Enter key manually". ### Actual Result When I choose "Scan a QR code", I can't choose to store it locally in the authenticator app - the BW password manager (mobile) automatically opens and wants to add the TOTP seed code to my BW vault. Only when I choose "Enter key manually", I can then choose between "Store in Bitwarden (vault" or "Save here (locally in the authenticator app). ### Screenshots or Videos (I hope it is clear without screenshots) ### Additional Context As always, I don't know if the same thing happens on iOS... ### Build Version 2025.6.0 (475) ### What server are you connecting to? EU ### Self-host Server Version (not self-hosting) ### Environment Details - Fairphone 5 - Android 14 ### 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:14:15 -06:00
GiteaMirror commented 2025-11-26 23:14:15 -06:00
Author
Owner
Copy Link

@bitwarden-bot commented on GitHub (Jul 7, 2025):

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

@bitwarden-bot commented on GitHub (Jul 7, 2025): Thank you for your report! We've added this to our internal board for review. ID: PM-23482
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#2275
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?