MACOS: Requires master password on lock every time even though I have it set to unlock with fingerprint
Steps To Reproduce
I have the chrome extension installed and set to unlock with fingerprint as well, not sure if that's relevant.
- Set up the desktop app to lock on system lock
- Set up to unlock with Touch ID
- Close laptop screen
- Open laptop screen
- Desktop app is locked and requires master password. Never prompts for Touch ID.
Expected Result
I expect the desktop app to prompt for TouchID to unlock the app, like I have it set in the settings
Actual Result
It forces me to use the master password every time.
Screenshots or Videos
No response
Additional Context
No response
Operating System
macOS
Operating System Version
Senoma 14.5
Installation method
Direct Download (from bitwarden.com)
Build Version
2024.7.1 (27455)
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.
Hi there,
Thank you for your report!
I was able to reproduce this issue, and I have flagged this to our engineering team.
If you wish to add any further information/screenshots/recordings etc., please feel free to do so at any time - our engineering team will be happy to review these.
Thanks once again!
I have similar / related issues:
- Bitwarden keeps asking for Touch ID when opened but not used
- the Chrome extension Touch ID unlock doesn't work if the desktop app is not unlocked; it was working before the latest update
Steps To Reproduce
I have the chrome extension installed and set to unlock with fingerprint as well, not sure if that's relevant.
- Set up the desktop app to lock on system lock
- Set up to unlock with Touch ID
- Close laptop screen
- Open laptop screen
- Desktop app is locked and requires master password. Never prompts for Touch ID.
Expected Result
I expect the desktop app to prompt for TouchID to unlock the app, like I have it set in the settings
Actual Result
It forces me to use the master password every time.
Screenshots or Videos
No response
Additional Context
No response
Operating System
macOS
Operating System Version
Senoma 14.5
Installation method
Direct Download (from bitwarden.com)
Build Version
2024.7.1 (27455)
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.
+1 on this exact issue...extremely uncomfortable bug...
Same here, the Mac desktop app sometimes doesn't show the Touch ID option, way too often for a once-in-a-while password reminder.
And the browser extension stopped working if the desktop app is locked. This used to work, and 1Password allows this flow. Very inconvenient having to open and unlock the desktop app every time.
+1, the chrome extension hasn't prompted me for touch id once in the last few weeks, master pw every time. I should also add l clicking "Unlock with biometrics" doesn't do anything at all, that button is unresponsive
Same issue: Version: 2024.10.0 Server version (Third-party): 2024.2.0
- deleted the extension
- add the extension from Web Extensions Store
- select self hosted and add my url
- enter email
- and Master Password
- enter TOTP
- Unlock option change to Fingerprint
- lock
- click on Unlock with biometrics
- No pop up to ask for finger print
This is back to working for me on the latest update
2024.9.0 works for me, 2024.9.1 breaks it. On the latest, it seems like it's failing to trigger the TouchID OS dialog. I see something try to load in the Dock, but then it immediately disappears. When I downgraded my extension version to 2024.9.1, it started working reliably to trigger Touch ID again. When I disable and re-enable the setting in Account Security, that process does trigger Touch ID. But the "unlock with biometrics" fails 100% of the time to actually trigger TouchID.
MacOS 15.0.1 Extension Version 2024.9.1 LibreWolf 131.0.2-1
I see the same symptoms on macOS 14.7 and Firefox 131.0.3 using 2024.10.0 of the addon. Furthermore, I tried to disable touch ID ("unlock with biometrics") in the addon settings and then re-enable it. It won't re-enable but tries to open some app as described by @plmcgrn in the previous comment. It doesn't make a difference whether the desktop app is running or not, unlocked or not.
It feels like less of an issue triggering the touch ID dialog but rather opening/activating the desktop app. Then again, I believe to have read in one of the recent changelogs that the desktop app would no longer be a requirement for touch ID in the browser, but I might have interpreted this incorrectly.
I'm having the exact same issue with Firefox 131.0.3 on macOS 15.1 with extension version 2024.10.0. As said previously, toggling biometrics off and back on does trigger the desktop app to prompt for TouchID. However, once my vault is locked, the prompt to unlock with TouchID from the desktop app does not appear and clicking the "Unlock with biometrics" button in the addon does nothing.
edit: Just noticed that I was on a very old (2024.3.0) version of the Bitwarden desktop application. The Mac app store has been trying to update it, but the update kept failing (I thought Bitwarden was just pushing a lot of updates because it would prompt to update about once a week). I deleted the old version of the desktop application and reinstalled 2024.10.0. Exited both my browser and desktop application completely. Disabled and re-enabled biometrics in the browser addon and it appears to be working now.
For those having this issue, ensure your Bitwarden desktop app is up to date. It appears there is an issue with the app store updating it, where you have to manually quit the app from the menu bar, before it'll succeed. I can confirm that desktop app version Version 2024.11.0 (33157) and Firefox extension version 2024.10.1 do work properly in allowing TouchID unlock of the browser vault.
Hi, this should be fixed in 2025.1.2 and later. Firefox is still taking a bit to review the extension update. If the issue re-occurs on the aforementioned version, please re-open the issue.