github-starred/android
2
0
Fork 0
mirror of https://github.com/bitwarden/android.git synced 2026-03-19 05:02:48 -05:00
Code Issues 144 Packages Projects Releases 116 Wiki Activity

[Android] Tresor won't unlock if fingerprint mismatches at the first try #960

New Issue
Closed
opened 2025-11-26 22:35:26 -06:00 by GiteaMirror · 4 comments
GiteaMirror commented 2025-11-26 22:35:26 -06:00
Owner
Copy Link

Originally created by @sidenico on GitHub (Mar 21, 2020).

Originally assigned to: @mpbw2 on GitHub.

Describe the Bug

I setup Bitwarden to unlock with my fingerprint. If I want to use Bitwarden the following happens:

  • I open the app
  • fingerprint prompt appears
  • first fingerprint mismatches
  • second (or a following try) succeeds
  • fingerprint prompt disappears
  • tresor still locked

After that nothing happens. I have to tap on "use biometric data to unlock" or enter the password. That happens again and again until I succeed at the first try with my fingerprint.

Steps To Reproduce

  1. Setup Bitwarden to unlock with fingerprint
  2. Lock Bitwarden if needed
  3. Open Bitwarden / use biometric data to unlock
  4. Fail on the first try at unlocking with your fingerprint
  5. Succeed on a following try
  6. Fingerprint prompt disappears and Bitwarden won't unlock.

Expected Result

If the fingerprint matches at any try (even if the first try fails) your tresor should unlock.

Actual Result

Nothing happens / tresor won't unlock. You're still on the main screen and have to unlock Bitwarden via password or biometric data.

Screenshots or Videos

Can't take a screenshot or video from Bitwarden. The app blocks both of it.

Environment

  • Device: Huawei P30
  • Operating system: Android 10 / EMUI 10.0.0
  • Build Version (go to "Settings" → "About" in the app): 10.0.0.186 (C432E22R2P5)
  • Is this a Beta release? No
  • Bitwarden Version: 2.3.1
Originally created by @sidenico on GitHub (Mar 21, 2020). Originally assigned to: @mpbw2 on GitHub. ## Describe the Bug I setup Bitwarden to unlock with my fingerprint. If I want to use Bitwarden the following happens: - I open the app - fingerprint prompt appears - first fingerprint mismatches - second (or a following try) succeeds - fingerprint prompt disappears - tresor still locked After that nothing happens. I have to tap on "use biometric data to unlock" or enter the password. That happens again and again until I succeed at the first try with my fingerprint. ## Steps To Reproduce 1. Setup Bitwarden to unlock with fingerprint 2. Lock Bitwarden if needed 3. Open Bitwarden / use biometric data to unlock 4. Fail on the first try at unlocking with your fingerprint 5. Succeed on a following try 6. Fingerprint prompt disappears and Bitwarden won't unlock. ## Expected Result If the fingerprint matches at any try (even if the first try fails) your tresor should unlock. ## Actual Result Nothing happens / tresor won't unlock. You're still on the main screen and have to unlock Bitwarden via password or biometric data. ## Screenshots or Videos Can't take a screenshot or video from Bitwarden. The app blocks both of it. ## Environment - Device: Huawei P30 - Operating system: Android 10 / EMUI 10.0.0 - Build Version (go to "Settings" → "About" in the app): 10.0.0.186 (C432E22R2P5) - Is this a Beta release? No - Bitwarden Version: 2.3.1
GiteaMirror commented 2025-11-26 22:35:26 -06:00
Author
Owner
Copy Link

@watk commented on GitHub (Apr 22, 2020):

I'm still seeing the issue. Could we reopen the issue please? I can reproduce it on the tip of master, built today. May I ask whether you verified that updating the libraries fixed this?

Thanks

@watk commented on GitHub (Apr 22, 2020): I'm still seeing the issue. Could we reopen the issue please? I can reproduce it on the tip of master, built today. May I ask whether you verified that updating the libraries fixed this? Thanks
GiteaMirror commented 2025-11-26 22:35:26 -06:00
Author
Owner
Copy Link

@mpbw2 commented on GitHub (Apr 22, 2020):

@watk The fix isn't in master yet. [Edit] Sorry, I meant public release, not master branch. Coffee hasn't kicked in yet. I'll take a look at the PR.

@mpbw2 commented on GitHub (Apr 22, 2020): @watk The fix isn't in master yet. [Edit] Sorry, I meant public release, not master branch. Coffee hasn't kicked in yet. I'll take a look at the PR.
GiteaMirror commented 2025-11-26 22:35:26 -06:00
Author
Owner
Copy Link

@watk commented on GitHub (Apr 23, 2020):

No problem, thanks!

@watk commented on GitHub (Apr 23, 2020): No problem, thanks!
GiteaMirror commented 2025-11-26 22:35:26 -06:00
Author
Owner
Copy Link

@mpbw2 commented on GitHub (Apr 23, 2020):

@watk Updating the libraries did indeed fix this on a Pixel 3, but I have since added additional devices to my test bed and confirmed it did not work across the board. Your fix seems to fill the gap. Thanks!

@mpbw2 commented on GitHub (Apr 23, 2020): @watk Updating the libraries did indeed fix this on a Pixel 3, but I have since added additional devices to my test bed and confirmed it did not work across the board. Your fix seems to fill the gap. Thanks!
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
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#960
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?