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

If you unlock your vault with your fingerprint immediately after the Bitwarden Biometric Verification screen slides up the matched logins screen is empty. #1213

New Issue
Closed
opened 2025-11-26 22:42:08 -06:00 by GiteaMirror · 1 comment
GiteaMirror commented 2025-11-26 22:42:08 -06:00
Owner
Copy Link

Originally created by @jredders on GitHub (Feb 18, 2021).

Describe the Bug

If I haven't used Bitwarden in a while and try to auto-fill a username/password in the Brave Browser from my vault and respond to the Bitwarden Biometric Verification immediately after it slides up by pressing my finger to the fingerprint reader, the vault unlocks, but the matched logins page is empty.

NOTE: It may not just be a Brave browser issue, but that's where I've definitely seen it happen from.

Steps To Reproduce

  1. Don't use Bitwarden for a while
  • I can't really be more specific here because it doesn't always happen. I have Bitwarden set to auto-lock the vault after 15 minutes and have Unlock with Biometrics enabled. It might require the phone to have gone into deep sleep since the last time Bitwarden has been used?
  1. Click on a username or password field in Brave for a site you have a login saved for
  2. Click on the button to auto-fill from your vault
  3. Immediately after Bitwarden opens and the Bitwarden Biometric Verification screen slides up from the bottom, press your finger to the fingerprint reader as fast as you can
  4. The fingerprint is successfully read and the vault unlocks, but the matched logins page is empty

NOTE: At this point going back to Brave and then clicking the button to auto-fill from your vault again will now take you to the still unlocked vault logins page and show the login(s).

NOTE: I also just had it go to the main vault page instead of showing the matching logins. Going back to Brave and clicking on the auto-fill from vault button again the second time took me to the matched logins.

NOTE: The first time I remember seeing this happen was in December of 2020.

Expected Result

Clicking on the auto-fill button to go to Bitwarden and responding to the Bitwarden Biometric Verification screen as quickly or slowly as you like should unlock the vault and show the matched logins to auto-fill with.

Actual Result

If you click too quickly on the fingerprint reader after the Bitwarden Biometric Verification screen slides up, sometimes the matched logins screen will be empty, even though there is a valid login in my vault. If you wait a few seconds from when the screen slides up before pressing the fingerprint reader it always works.

Environment

  • Pixel 4A
  • Android 11 with February 5, 2021 security update
  • Build Version 2.8.0 (3349)
  • Is this a Beta release? N
Originally created by @jredders on GitHub (Feb 18, 2021). ## Describe the Bug If I haven't used Bitwarden in a while and try to auto-fill a username/password in the Brave Browser from my vault and respond to the Bitwarden Biometric Verification immediately after it slides up by pressing my finger to the fingerprint reader, the vault unlocks, but the matched logins page is empty. NOTE: It may not just be a Brave browser issue, but that's where I've definitely seen it happen from. ## Steps To Reproduce 1. Don't use Bitwarden for a while - I can't really be more specific here because it doesn't always happen. I have Bitwarden set to auto-lock the vault after 15 minutes and have Unlock with Biometrics enabled. It might require the phone to have gone into deep sleep since the last time Bitwarden has been used? 2. Click on a username or password field in Brave for a site you have a login saved for 3. Click on the button to auto-fill from your vault 4. Immediately after Bitwarden opens and the Bitwarden Biometric Verification screen slides up from the bottom, press your finger to the fingerprint reader as fast as you can 5. The fingerprint is successfully read and the vault unlocks, but the matched logins page is empty NOTE: At this point going back to Brave and then clicking the button to auto-fill from your vault again will now take you to the still unlocked vault logins page and show the login(s). NOTE: I also just had it go to the main vault page instead of showing the matching logins. Going back to Brave and clicking on the auto-fill from vault button again the second time took me to the matched logins. NOTE: The first time I remember seeing this happen was in December of 2020. ## Expected Result Clicking on the auto-fill button to go to Bitwarden and responding to the Bitwarden Biometric Verification screen as quickly or slowly as you like should unlock the vault and show the matched logins to auto-fill with. ## Actual Result If you click too quickly on the fingerprint reader after the Bitwarden Biometric Verification screen slides up, sometimes the matched logins screen will be empty, even though there is a valid login in my vault. If you wait a few seconds from when the screen slides up before pressing the fingerprint reader it always works. ## Environment - Pixel 4A - Android 11 with February 5, 2021 security update - Build Version 2.8.0 (3349) - Is this a Beta release? N
GiteaMirror commented 2025-11-26 22:42:08 -06:00
Author
Owner
Copy Link

@jredders commented on GitHub (Feb 19, 2021):

I'm now wondering if it just shows the matched logins screen before it's really finished searching, because I saw once yesterday that it showed up blank and just as I swiped to go back to Brave I saw the login appear. Maybe it needs some kind of spinner to show it's still working? I'll be sure to wait for a while if I see the issue again.

@jredders commented on GitHub (Feb 19, 2021): I'm now wondering if it just shows the matched logins screen before it's really finished searching, because I saw once yesterday that it showed up blank and just as I swiped to go back to Brave I saw the login appear. Maybe it needs some kind of spinner to show it's still working? I'll be sure to wait for a while if I see the issue again.
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#1213
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?