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

Sync Verification Codes functionality not working #2276

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

Originally created by @rmcdowell-bitwarden on GitHub (Jul 9, 2025).

Steps To Reproduce

  1. Have the latest version of the Bitwarden and the Bitwarden Authenticator apps installed
  2. Open the Bitwarden app
  3. Tap Settings
  4. Tap "Account security"
  5. Enable "Allow authenticator syncing"

Expected Result

TOTP codes are synced to the Bitwarden Authenticator app

Actual Result

Nothing happens

Screenshots or Videos

No response

Additional Context

This was tested on multiple additional devices and I have included their information below:

Device: Google Pixel 8a
OS: Android 16
Android version: 16
Bitwarden version: 2025.6.1 (20398)
Authenticator version: 2025.6.0 (475)

Device: Xiaomi 11T Pro
OS: Android 14
Bitwarden version: 2025.6.1 (20398)
Authenticator version: 2025.6.0 (475)

Build Version

2025.6.0 (475)

What server are you connecting to?

US

Self-host Server Version

No response

Environment Details

Device: Samsung Galaxy S25+
OS: One UI version 7.0
Android version: 15
Bitwarden version: 2025.6.1 (20398)

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 @rmcdowell-bitwarden on GitHub (Jul 9, 2025). ### Steps To Reproduce 1. Have the latest version of the Bitwarden and the Bitwarden Authenticator apps installed 2. Open the Bitwarden app 3. Tap Settings 4. Tap "Account security" 5. Enable "Allow authenticator syncing" ### Expected Result TOTP codes are synced to the Bitwarden Authenticator app ### Actual Result Nothing happens ### Screenshots or Videos _No response_ ### Additional Context This was tested on multiple additional devices and I have included their information below: Device: Google Pixel 8a OS: Android 16 Android version: 16 Bitwarden version: 2025.6.1 (20398) Authenticator version: 2025.6.0 (475) Device: Xiaomi 11T Pro OS: Android 14 Bitwarden version: 2025.6.1 (20398) Authenticator version: 2025.6.0 (475) ### Build Version 2025.6.0 (475) ### What server are you connecting to? US ### Self-host Server Version _No response_ ### Environment Details Device: Samsung Galaxy S25+ OS: One UI version 7.0 Android version: 15 Bitwarden version: 2025.6.1 (20398) ### 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:16 -06:00
Author
Owner
Copy Link

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

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

@bitwarden-bot commented on GitHub (Jul 9, 2025): Thank you for your report! We've added this to our internal board for review. ID: PM-23560
GiteaMirror commented 2025-11-26 23:14:16 -06:00
Author
Owner
Copy Link

@pamperer562580892423 commented on GitHub (Jul 9, 2025):

@rmcdowell-bitwarden I noticed the same on my Android 14 device.

But did you test the following (?): after enabling "Allow authenticator syncing" in the mobile password manager app - if you delete the app data of the authenticator app (of course, only do that if you don't have any important data in it - or made a backup of it), then the sync worked for me. I guess the same would work, when the authenticator would be installed the first time at all on the device.

But I agree, if you don't want to delete the app data, something blocks the sync from being initiated in the authenticator app.

@pamperer562580892423 commented on GitHub (Jul 9, 2025): @rmcdowell-bitwarden I noticed the same on my Android 14 device. But did you test the following (?): after enabling "Allow authenticator syncing" in the mobile password manager app - if you delete the app data of the authenticator app (of course, only do that if you don't have any important data in it - or made a backup of it), then the sync worked for me. I guess the same would work, when the authenticator would be installed the first time at all on the device. But I agree, if you don't want to delete the app data, something blocks the sync from being initiated in the authenticator app.
GiteaMirror commented 2025-11-26 23:14:16 -06:00
Author
Owner
Copy Link

@vineet4183 commented on GitHub (Jul 10, 2025):

@pamperer562580892423

I have multiple times tried to do a clean install of authenticator, but the sync doesn't happen.

@vineet4183 commented on GitHub (Jul 10, 2025): @pamperer562580892423 I have multiple times tried to do a clean install of authenticator, but the sync doesn't happen.
GiteaMirror commented 2025-11-26 23:14:16 -06:00
Author
Owner
Copy Link

@chuegel commented on GitHub (Aug 27, 2025):

Same issue here with a Google Pixel 8 Pro

@chuegel commented on GitHub (Aug 27, 2025): Same issue here with a Google Pixel 8 Pro
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#2276
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?