bitwarden
When the vault automatically locks after time-out, it prompts for biometrics again
Steps To Reproduce
- Configure your vault to time-out after 5 minutes.
- Configure your vault to unlock with Windows Hello biometrics.
- Unlock your vault with biometrics.
- Wait 5 minutes.
- The vault will lock, and you'll get the Windows Hello biometrics prompt again (even though you most likely don't want to unlock the vault at this point, you just want it to auto-lock).
Expected Result
Biometrics prompt should not show.
Actual Result
Biometrics prompt shows.
Screenshots or Videos
No response
Additional Context
No response
Operating System
Windows
Operating System Version
No response
Installation method
Direct Download (from bitwarden.com)
Build Version
Version 2024.6.3 Shell 29.4.2 Renderer 122.0.6261.156 Node 20.9.0 Architecture x64
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.
Adding to the issue, the browser extension is unable to "Unlock with biometrics" when the desktop app is locked.
I have Vault timeout with lock on the browser extension (30m) and the desktop app (5m), and prior to last week's update, the browser extension would unlock the desktop vault using biometrics when the desktop app is locked (correct me if im wrong here, I've never checked if desktop app is unlocked when i unlock the browser extension). Now it just shows "User locked or logged out" and doesnt attempt to unlock the vault. After I unlock the desktop app (also using biometrics), the "Unlock with biometrics" option works as expected.
Web Browser
Firefox 127.0.2 (64-bit)
Operating System
macOS Sonoma 14.5 (23F79)
Installation method
Mac App Store (otherwise biometrics integration doesnt work)
Build Version
Version 2024.6.3 Shell 29.4.2 Renderer 122.0.6261.156 Node 20.9.0 Architecture arm64
@c3JpbmkK this is a separate issue, could you please open a new issue for this example? Thank you!
Hi there,
I am unable to reproduce this issue, it has been escalated for further investigation. If you have more information that can help us, please add it below.
Thanks!
Adding to the issue, the browser extension is unable to "Unlock with biometrics" when the desktop app is locked.
I have Vault timeout with lock on the browser extension (30m) and the desktop app (5m), and prior to last week's update, the browser extension would unlock the desktop vault using biometrics when the desktop app is locked (correct me if im wrong here, I've never checked if desktop app is unlocked when i unlock the browser extension). Now it just shows "User locked or logged out" and doesnt attempt to unlock the vault. After I unlock the desktop app (also using biometrics), the "Unlock with biometrics" option works as expected.
Yep, I've also noticed this regression as well.
Same annoying behavior on Mac too. When BW desktop app auto-locks in the background the Touch ID fingerprint prompt pops up. I have the setting "Ask for Touch ID on app start" enabled. But it should be smart and not ask for it on auto-lock or manual lock, or only do it if the app is in the foreground, if it's in the background just lock it quietly and pop up the Touch ID prompt next time I bring the app to the foreground.
I can confirm, that it is correlated to the "Ask for Touch ID on app start" option. When it is disabled, the Desktop App does not prompt the Touch ID popup, if the App is in the background.
I see this behaviour on a Mac (M2 Air, Ventura 13.6.9) too and that disabling "Ask for Touch ID on app start" prevents it happening.
⚠️ Stale Issue Notice
This issue has been automatically marked as stale due to inactivity. It will be closed in 2 weeks (October 15, 2025) if no further activity occurs.
If this issue is still relevant and you would like to keep it open, please:
- Comment on this issue to show continued interest
- Provide any additional information or updates
- Confirm that the issue still exists in the latest version
Thank you for your contribution to this project! 🙏
🔒 Issue Closed Due to Inactivity
This issue has been automatically closed due to lack of activity for an extended period. We periodically review and close inactive issues to help maintain our issue tracker and focus on current priorities.
If this issue is still relevant:
- Please create a new issue with updated information
- Include steps to reproduce the problem if it's a bug report
- Mention if this issue still occurs in the latest version
Thank you for your contribution to this project. Your feedback helps us improve! 🙏