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-195] Auth does not update username field when Bitwarden updated #2361

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

Originally created by @andbenn on GitHub (Sep 26, 2025).

Steps To Reproduce

  1. Have Auth syncing with Bitwarden
  2. Change the Username field on a Bitwarden entry that sync's the TOTP token to Auth
  3. Save the entry. Sync Bitwarden
  4. Open Auth
  5. Search for the site
  6. Username has not been updated

Expected Result

I expect the username field in Auth from a synced Bitwarden session to get updated.

Actual Result

Auth continues to use old, prior username as a field.
Due to it being a synced item, it can't be edited to be corrected either.

Screenshots or Videos

No response

Additional Context

No response

Build Version

2025.9.0

What server are you connecting to?

US

Self-host Server Version

No response

Environment Details

Pixel 7a up to date Android

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 @andbenn on GitHub (Sep 26, 2025). ### Steps To Reproduce 1. Have Auth syncing with Bitwarden 2. Change the Username field on a Bitwarden entry that sync's the TOTP token to Auth 3. Save the entry. Sync Bitwarden 4. Open Auth 5. Search for the site 6. Username has not been updated ### Expected Result I expect the username field in Auth from a synced Bitwarden session to get updated. ### Actual Result Auth continues to use old, prior username as a field. Due to it being a synced item, it can't be edited to be corrected either. ### Screenshots or Videos _No response_ ### Additional Context _No response_ ### Build Version 2025.9.0 ### What server are you connecting to? US ### Self-host Server Version _No response_ ### Environment Details Pixel 7a up to date Android ### 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:16:46 -06:00
GiteaMirror commented 2025-11-26 23:16:47 -06:00
Author
Owner
Copy Link

@bitwarden-bot commented on GitHub (Sep 26, 2025):

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

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

@rmcdowell-bitwarden commented on GitHub (Sep 29, 2025):

Hi there,

Thank you for your report!

I was able to reproduce this issue, and I have flagged this to our engineering team.

If you wish to add any further information/screenshots/recordings etc., please feel free to do so at any time - our engineering team will be happy to review these.

Thanks once again!

@rmcdowell-bitwarden commented on GitHub (Sep 29, 2025): Hi there, Thank you for your report! I was able to reproduce this issue, and I have flagged this to our engineering team. If you wish to add any further information/screenshots/recordings etc., please feel free to do so at any time - our engineering team will be happy to review these. Thanks once again!
GiteaMirror commented 2025-11-26 23:16:47 -06:00
Author
Owner
Copy Link

@andbenn commented on GitHub (Nov 4, 2025):

On a quick check, I think this might be fixed in 2025.10.1, but I haven't been thorough enough to tell. Changing the Is it potentially resolved?

Being that, changing details about an entry in the Bitwarden Android password app then sync those updates if there's an entry in Android's Bitwarden Authenticator

@andbenn commented on GitHub (Nov 4, 2025): On a quick check, I think this might be fixed in 2025.10.1, but I haven't been thorough enough to tell. Changing the Is it potentially resolved? Being that, changing details about an entry in the Bitwarden Android password app then sync those updates if there's an entry in Android's Bitwarden Authenticator
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#2361
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?