github-starred/android
2
0
Fork 0
mirror of https://github.com/bitwarden/android.git synced 2026-05-06 15:58:22 -05:00
Code Issues 1.1k Packages Projects Releases 122 Wiki Activity

[GH-ISSUE #6550] [PM-32378] Can't authenticate using fingerprint #15107

New Issue
Open
opened 2026-04-15 01:28:42 -05:00 by GiteaMirror · 16 comments
GiteaMirror commented 2026-04-15 01:28:42 -05:00
Owner
Copy Link

Originally created by @carolfs on GitHub (Feb 17, 2026).
Original GitHub issue: https://github.com/bitwarden/android/issues/6550

Steps To Reproduce

  1. Use Bitwarden to fill in password. It asks for fingerprint, as previously set up.

Expected Result

The app will unlock.

Actual Result

A green "verified" mark appears, indicating the fingerprint recognition was successful, but a dialogue window from Bitwarden pops up and says that the unlock failed, and biometrics unlock must be re-enabled in the app. Then it asks for the master password.

Screenshots or Videos

No response

Additional Context

No response

Build Version

2026.1.1 (21176)

What server are you connecting to?

US

Self-host Server Version

No response

Environment Details

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 @carolfs on GitHub (Feb 17, 2026). Original GitHub issue: https://github.com/bitwarden/android/issues/6550 ### Steps To Reproduce 1. Use Bitwarden to fill in password. It asks for fingerprint, as previously set up. ### Expected Result The app will unlock. ### Actual Result A green "verified" mark appears, indicating the fingerprint recognition was successful, but a dialogue window from Bitwarden pops up and says that the unlock failed, and biometrics unlock must be re-enabled in the app. Then it asks for the master password. ### Screenshots or Videos _No response_ ### Additional Context _No response_ ### Build Version 2026.1.1 (21176) ### What server are you connecting to? US ### Self-host Server Version _No response_ ### Environment Details 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:password-managerbug labels 2026-04-15 01:28:42 -05:00
GiteaMirror commented 2026-04-15 01:28:44 -05:00
Author
Owner
Copy Link

@bitwarden-bot commented on GitHub (Feb 17, 2026):

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

<!-- gh-comment-id:3915761070 --> @bitwarden-bot commented on GitHub (Feb 17, 2026): Thank you for your report! We've added this to our internal board for review. ID: [PM-32378](https://bitwarden.atlassian.net/browse/PM-32378) [PM-32378]: https://bitwarden.atlassian.net/browse/PM-32378?atlOrigin=eyJpIjoiNWRkNTljNzYxNjVmNDY3MDlhMDU5Y2ZhYzA5YTRkZjUiLCJwIjoiZ2l0aHViLWNvbS1KU1cifQ
GiteaMirror commented 2026-04-15 01:28:46 -05:00
Author
Owner
Copy Link

@SaintPatrck commented on GitHub (Feb 17, 2026):

Hi @carolfs,

Out of curiosity, did this occur after a recent OS update or modification of existing biometrics (like adding or removing a fingerprint)?

<!-- gh-comment-id:3915939050 --> @SaintPatrck commented on GitHub (Feb 17, 2026): Hi @carolfs, Out of curiosity, did this occur after a recent OS update or modification of existing biometrics (like adding or removing a fingerprint)?
GiteaMirror commented 2026-04-15 01:28:47 -05:00
Author
Owner
Copy Link

@carolfs commented on GitHub (Feb 17, 2026):

@SaintPatrck I think it might be related to adding a fingerprint.

<!-- gh-comment-id:3916251613 --> @carolfs commented on GitHub (Feb 17, 2026): @SaintPatrck I think it might be related to adding a fingerprint.
GiteaMirror commented 2026-04-15 01:28:49 -05:00
Author
Owner
Copy Link

@Tipoff4317 commented on GitHub (Feb 17, 2026):

If you add a fingerprint, that's the normal behavior on Android. It's probably related to security. Someone else with your Android PIN can add a fingerprint but still cannot access Bitwarden.

<!-- gh-comment-id:3917198910 --> @Tipoff4317 commented on GitHub (Feb 17, 2026): If you add a fingerprint, that's the normal behavior on Android. It's probably related to security. Someone else with your Android PIN can add a fingerprint but still cannot access Bitwarden.
GiteaMirror commented 2026-04-15 01:28:52 -05:00
Author
Owner
Copy Link

@carolfs commented on GitHub (Feb 17, 2026):

I added the fingerprint more than a month ago and have already entered the master password several times, as well as re-enabled biometrics unlock an equal number of times. I accessed my vault on my phone every day since adding this fingerprint. This makes no sense. It is a bug.

<!-- gh-comment-id:3917273078 --> @carolfs commented on GitHub (Feb 17, 2026): I added the fingerprint more than a month ago and have already entered the master password several times, as well as re-enabled biometrics unlock an equal number of times. I accessed my vault on my phone every day since adding this fingerprint. This makes no sense. It is a bug.
GiteaMirror commented 2026-04-15 01:28:53 -05:00
Author
Owner
Copy Link

@pamperer562580892423 commented on GitHub (Feb 17, 2026):

@carolfs Could you add the full "Environmental details" from your phone? You can copy & paste them in here (or in your OP), when you enter the BW app --> Settings --> About --> Version.

<!-- gh-comment-id:3917309199 --> @pamperer562580892423 commented on GitHub (Feb 17, 2026): @carolfs Could you add the full "Environmental details" from your phone? You can copy & paste them in here (or in your OP), when you enter the BW app --> Settings --> About --> Version.
GiteaMirror commented 2026-04-15 01:28:54 -05:00
Author
Owner
Copy Link

@carolfs commented on GitHub (Feb 17, 2026):

© Bitwarden Inc. 2015-2026

Version: 2026.1.1 (21176)
📱 google Pixel 5 🤖 14@34 📦 prod
🧱 commit: bitwarden/android/release/2026.1-rc45@0ee3e2e24968837b9c8b260e105751750271540f
💻 build source: bitwarden/android/actions/runs/21527118876/attempts/1
🦀 SDK: 2.0.0-4676-0544ddec
🌩 Server: 2026.1.1 @ US

<!-- gh-comment-id:3917327671 --> @carolfs commented on GitHub (Feb 17, 2026): © Bitwarden Inc. 2015-2026 Version: 2026.1.1 (21176) 📱 google Pixel 5 🤖 14@34 📦 prod 🧱 commit: bitwarden/android/release/2026.1-rc45@0ee3e2e24968837b9c8b260e105751750271540f 💻 build source: bitwarden/android/actions/runs/21527118876/attempts/1 🦀 SDK: 2.0.0-4676-0544ddec 🌩 Server: 2026.1.1 @ US
GiteaMirror commented 2026-04-15 01:28:54 -05:00
Author
Owner
Copy Link

@pamperer562580892423 commented on GitHub (Feb 17, 2026):

@carolfs Thanks!

Hm. If I were you (and BTW, I'm only another user - not a Bitwarden employee)... and as the app sometimes can get a "hiccup"... I probably would do the following now:

  1. Delete the app data of the BW app (in the Android Settings --> Apps).
  2. Remove/deinstall the BW app.
  3. Restart the phone.
  4. Reinstall the BW app.
  5. Log in again (and set everything up again).

(= kind of a general troubleshooting tip...)

<!-- gh-comment-id:3917362656 --> @pamperer562580892423 commented on GitHub (Feb 17, 2026): @carolfs Thanks! Hm. If I were you (and BTW, I'm only another user - not a Bitwarden employee)... and as the app sometimes can get a "hiccup"... I probably would do the following now: 1. Delete the app data of the BW app (in the Android Settings --> Apps). 2. Remove/deinstall the BW app. 3. Restart the phone. 4. Reinstall the BW app. 5. Log in again (and set everything up again). (= kind of a general troubleshooting tip...)
GiteaMirror commented 2026-04-15 01:28:55 -05:00
Author
Owner
Copy Link

@carolfs commented on GitHub (Feb 17, 2026):

I had already tried to delete the data and uninstall/reinstall, but without restarting my phone. That worked, thanks!

<!-- gh-comment-id:3917412785 --> @carolfs commented on GitHub (Feb 17, 2026): I had already tried to delete the data and uninstall/reinstall, but without restarting my phone. That worked, thanks!
GiteaMirror commented 2026-04-15 01:28:55 -05:00
Author
Owner
Copy Link

@pamperer562580892423 commented on GitHub (Feb 18, 2026):

@carolfs Glad I could help. - And if it remains resolved for you, you could close this issue eventually.

<!-- gh-comment-id:3922381700 --> @pamperer562580892423 commented on GitHub (Feb 18, 2026): @carolfs Glad I could help. - And if it remains resolved for you, you could close this issue eventually.
GiteaMirror commented 2026-04-15 01:28:56 -05:00
Author
Owner
Copy Link

@carolfs commented on GitHub (Feb 18, 2026):

The bug still exists. Reinstalling the app is just a workaround.

<!-- gh-comment-id:3922398094 --> @carolfs commented on GitHub (Feb 18, 2026): The bug still exists. Reinstalling the app is just a workaround.
GiteaMirror commented 2026-04-15 01:28:57 -05:00
Author
Owner
Copy Link

@pamperer562580892423 commented on GitHub (Feb 18, 2026):

Ah, so you still get the popup which says that unlock fails?

<!-- gh-comment-id:3922421558 --> @pamperer562580892423 commented on GitHub (Feb 18, 2026): Ah, so you still get the popup which says that unlock fails?
GiteaMirror commented 2026-04-15 01:28:59 -05:00
Author
Owner
Copy Link

@carolfs commented on GitHub (Feb 18, 2026):

No, but I had to reinstall. It's not correct behaviour for an app if users have to reinstall the app every time they add or remove a fingerprint.

<!-- gh-comment-id:3922435699 --> @carolfs commented on GitHub (Feb 18, 2026): No, but I had to reinstall. It's not correct behaviour for an app if users have to reinstall the app every time they add or remove a fingerprint.
GiteaMirror commented 2026-04-15 01:28:59 -05:00
Author
Owner
Copy Link

@pamperer562580892423 commented on GitHub (Feb 18, 2026):

@carolfs Thanks for clarifying. But now I'm curious:

I added the fingerprint more than a month ago and have already entered the master password several times, as well as re-enabled biometrics unlock an equal number of times. I accessed my vault on my phone every day since adding this fingerprint. This makes no sense. It is a bug.

If I understood you correctly here, you didn't get that unlock error immediately after changing your fingerprint, right? And you didn't experience the unlock error for the whole "more than a month", right?

🤔

<!-- gh-comment-id:3922602541 --> @pamperer562580892423 commented on GitHub (Feb 18, 2026): @carolfs Thanks for clarifying. But now I'm curious: > I added the fingerprint more than a month ago and have already entered the master password several times, as well as re-enabled biometrics unlock an equal number of times. I accessed my vault on my phone every day since adding this fingerprint. This makes no sense. It is a bug. If I understood you correctly here, you didn't get that unlock error immediately after changing your fingerprint, right? And you didn't experience the unlock error for the whole "more than a month", right? 🤔
GiteaMirror commented 2026-04-15 01:29:00 -05:00
Author
Owner
Copy Link

@carolfs commented on GitHub (Feb 18, 2026):

I wish I could remember when I first noticed the issue. I'm not sure it was exactly after adding the fingerprint. At one point, I disabled locking to get rid of the error.

<!-- gh-comment-id:3922620417 --> @carolfs commented on GitHub (Feb 18, 2026): I wish I could remember when I first noticed the issue. I'm not sure it was exactly after adding the fingerprint. At one point, I disabled locking to get rid of the error.
GiteaMirror commented 2026-04-15 01:29:01 -05:00
Author
Owner
Copy Link

@molitar commented on GitHub (Feb 22, 2026):

Let me add some feedback to this issue as It just started for me after I installed the Android 16 February Security update. If I use pin code it works fine but not with Biometric.

Go to browser and click in field and Bitwarden option pops open. Unlock with BIometric now nothing works. You can't click on the option to unlock, you close Bitwarden and you can not click on any home icons. You can't do anything until you toggle display than it works again. So Biometric is broken in Android Bitwarden after the Feb 2026 Android 16 security update.

I found a fix for this issue and it has to do with Android itself.

  1. Disable Biometrics in Bitwarden
  2. Go into Android Security and delete ALL fingerprints
  3. Add new fingerprints
  4. Reboot Mobile Phone
  5. Enable Biometrics in Bitwarden

This is what fixed it for me in Android 16 After the Feb Security update.

<!-- gh-comment-id:3940234888 --> @molitar commented on GitHub (Feb 22, 2026): Let me add some feedback to this issue as It just started for me after I installed the Android 16 February Security update. If I use pin code it works fine but not with Biometric. Go to browser and click in field and Bitwarden option pops open. Unlock with BIometric now nothing works. You can't click on the option to unlock, you close Bitwarden and you can not click on any home icons. You can't do anything until you toggle display than it works again. So Biometric is broken in Android Bitwarden after the Feb 2026 Android 16 security update. I found a fix for this issue and it has to do with Android itself. 1. Disable Biometrics in Bitwarden 2. Go into Android Security and delete ALL fingerprints 3. Add new fingerprints 4. Reboot Mobile Phone 5. Enable Biometrics in Bitwarden This is what fixed it for me in Android 16 After the Feb Security update.
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:password-manager 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#15107
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?