github-starred/android
2
0
Fork 0
mirror of https://github.com/bitwarden/android.git synced 2026-05-07 03:23:29 -05:00
Code Issues 1.1k Packages Projects Releases 122 Wiki Activity

[GH-ISSUE #4737] Biometric login fails with 2 accounts logged in on Android #50259

New Issue
Closed
opened 2026-05-01 12:15:04 -05:00 by GiteaMirror · 3 comments
GiteaMirror commented 2026-05-01 12:15:04 -05:00
Owner
Copy Link

Originally created by @TapGhoul on GitHub (Feb 18, 2025).
Original GitHub issue: https://github.com/bitwarden/android/issues/4737

Steps To Reproduce

  1. Add an account and enable biometreic login on it
  2. Add another account and enable biometric login on it

Expected Result

Log in is successful in both cases

Actual Result

App crash on attempt to use biometrics with any account that is not the most recent to enable biometrics

Screenshots or Videos

No response

Additional Context

You can successfully use biometrics to log into the last account you enabled biometric login with, but when you switch accounts, it will crash on attempt to log in. This occurs both from the logged out state and the locked state. Switching the currently broken account's biometrics off and back on will cause that to be the correctly functioning app.

Note, pin codes do not have any such issue.

Build Version

2025.1.2 (19740)

What server are you connecting to?

US

Self-host Server Version

No response

Environment Details

  • Device: Pixel 8a
  • OS: Graphene OS, Android 15, Build 2025021100

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 @TapGhoul on GitHub (Feb 18, 2025). Original GitHub issue: https://github.com/bitwarden/android/issues/4737 ### Steps To Reproduce 1. Add an account and enable biometreic login on it 2. Add another account and enable biometric login on it ### Expected Result Log in is successful in both cases ### Actual Result App crash on attempt to use biometrics with any account that is not the most recent to enable biometrics ### Screenshots or Videos _No response_ ### Additional Context You can successfully use biometrics to log into the last account you enabled biometric login with, but when you switch accounts, it will crash on attempt to log in. This occurs both from the logged out state and the locked state. Switching the currently broken account's biometrics off and back on will cause that to be the correctly functioning app. Note, pin codes do not have any such issue. ### Build Version 2025.1.2 (19740) ### What server are you connecting to? US ### Self-host Server Version _No response_ ### Environment Details - Device: Pixel 8a - OS: Graphene OS, Android 15, Build 2025021100 ### 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 bug label 2026-05-01 12:15:04 -05:00
GiteaMirror commented 2026-05-01 12:15:13 -05:00
Author
Owner
Copy Link

@bitwarden-bot commented on GitHub (Feb 18, 2025):

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

<!-- gh-comment-id:2664942577 --> @bitwarden-bot commented on GitHub (Feb 18, 2025): Thank you for your report! We've added this to our internal board for review. ID: PM-18389
GiteaMirror commented 2026-05-01 12:15:16 -05:00
Author
Owner
Copy Link

@TapGhoul commented on GitHub (Feb 18, 2025):

Worth an extra note: turning off biometrics on the account not currently uses it does not cause biometrics to be disabled on the app altogether. It's only when reenabled on the second account does the functioning biometrics change.

<!-- gh-comment-id:2664945442 --> @TapGhoul commented on GitHub (Feb 18, 2025): Worth an extra note: turning off biometrics on the account not currently uses it does not cause biometrics to be disabled on the app altogether. It's only when reenabled on the second account does the functioning biometrics change.
GiteaMirror commented 2026-05-01 12:15:19 -05:00
Author
Owner
Copy Link

@SaintPatrck commented on GitHub (Feb 18, 2025):

Hi @TapGhoul

This has already been resolved (#4696) and the fix will be available in the next release. Note that you may need to re-enable biometrics one last time after the update to ensure each account is assigned a unique key.

If you continue having problems after the next release let us know and we will re-open this issue.

<!-- gh-comment-id:2667023476 --> @SaintPatrck commented on GitHub (Feb 18, 2025): Hi @TapGhoul This has already been resolved (#4696) and the fix will be available in the next release. Note that you may need to re-enable biometrics one last time after the update to ensure each account is assigned a unique key. If you continue having problems after the next release let us know and we will re-open this issue.
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 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#50259
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?