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

[GH-ISSUE #658] Android - Bitwarden prompts for biometrics when locking #20132

New Issue
Closed
opened 2026-04-16 19:59:22 -05:00 by GiteaMirror · 3 comments
GiteaMirror commented 2026-04-16 19:59:22 -05:00
Owner
Copy Link

Originally created by @nkm8 on GitHub (Nov 22, 2019).
Original GitHub issue: https://github.com/bitwarden/android/issues/658

I am using a Pixel 3 running Android 10 and I am able to reproduce this issue on a different device (also a Pixel 3 running Android 10). I have already tried uninstalling/re-installing Bitwarden.

Steps to reproduce:

  1. Set 'Lock Options' setting to 1 minute (the issue occurs with any of the values in minutes)
  2. Open a different application (I am done using Bitwarden at this point)
  3. After the lock timeout, the system 'Use biometrics to verify' fingerprint prompt shows up (it shouldn't)

The issue still occurs even if the device is no longer being used. I have ambient display enabled, so the biometrics prompt appears on the lock screen and keeps the screen active until you either hit cancel or validate your fingerprint.

Originally created by @nkm8 on GitHub (Nov 22, 2019). Original GitHub issue: https://github.com/bitwarden/android/issues/658 I am using a Pixel 3 running Android 10 and I am able to reproduce this issue on a different device (also a Pixel 3 running Android 10). I have already tried uninstalling/re-installing Bitwarden. Steps to reproduce: 1. Set 'Lock Options' setting to 1 minute (the issue occurs with any of the values in minutes) 2. Open a different application (I am done using Bitwarden at this point) 3. After the lock timeout, the system 'Use biometrics to verify' fingerprint prompt shows up (it shouldn't) The issue still occurs even if the device is no longer being used. I have ambient display enabled, so the biometrics prompt appears on the lock screen and keeps the screen active until you either hit cancel or validate your fingerprint.
GiteaMirror commented 2026-04-16 19:59:25 -05:00
Author
Owner
Copy Link

@kspearrin commented on GitHub (Nov 22, 2019):

This should be fixed in the latest beta in the play store. Can you give that a try?

<!-- gh-comment-id:557544823 --> @kspearrin commented on GitHub (Nov 22, 2019): This should be fixed in the latest beta in the play store. Can you give that a try?
GiteaMirror commented 2026-04-16 19:59:26 -05:00
Author
Owner
Copy Link

@nkm8 commented on GitHub (Nov 22, 2019):

Tested as resolved on beta version 2.2.6.

I'm not sure if it is intended, but I had my lock timeout set to 1 minute for testing before the upgrade. After the upgrade, the timeout was set to 5 minutes - I had to manually set it back to 1 minute to validate the fix.

<!-- gh-comment-id:557550207 --> @nkm8 commented on GitHub (Nov 22, 2019): Tested as resolved on beta version 2.2.6. I'm not sure if it is intended, but I had my lock timeout set to 1 minute for testing before the upgrade. After the upgrade, the timeout was set to 5 minutes - I had to manually set it back to 1 minute to validate the fix.
GiteaMirror commented 2026-04-16 19:59:27 -05:00
Author
Owner
Copy Link

@kspearrin commented on GitHub (Nov 22, 2019):

I don’t know why your timeout setting would have changed.

<!-- gh-comment-id:557550510 --> @kspearrin commented on GitHub (Nov 22, 2019): I don’t know why your timeout setting would have changed.
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#20132
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?