Open pqhf5kd opened 2 years ago
I have this exact same issue on Mac OS 12.3, when in clamshell mode trying to unlock the Safari browser extension states "Browser biometrics is not supported on this device" error.
I think something isn't implemented on the Safari extension to detect biometrics when the device is in clamshell mode. When I have my MacBook in clamshell mode it works with biometrics when using the Chrome Bitwarden extension (unlocks via my Apple Watch double tap side button)
I have the same problem, I was playing with the idea of using Safari, but this is a dealbreaker. I'm using the Macbook 99% of the time in clamshell mode and I can't unlock Bitwarden in Safari using Apple Watch. It works in Chrome / Brave.
I can confirm this behavior under Safari 15.5 (17613.2.7.1.8) + Bitwarden Extension 2022.05.0 Edge/Chrome Extension works in clam-shell mode, and so does the Desktop version of Bitwarden.
Have the same issue when using my Macbook with clamshell mode and trying to unlock with Apple Watch. Works in Firefox.
MacOS 12.5.1. Safari 15.6.1. BitWarden Safari 2022.8.0
Sorry to bring up an old thread, but this also impacts Mac desktops that do not have TouchID (or a keyboard with TouchID), such as the Mac Mini or Mac Studio.
The Chrome extension does work to unlock via an Apple Watch, and so does the desktop app, but when trying to setup biometric unlock on Safari, it fails without event prompting for authentication via the Watch.
The linked PR hasn't had any traction in quite some time...
+1 for really wanting this feature. I use Safair as my main browser on macOS (MacBook Pro) because of it's integration with the rest of the Apple ecosystem like SMS OTP codes, etc but getting this popup every time I try to login to the browser extension in clamshell mode is really annoying and frustrating. Biometric login in the desktop app works perfectly with the watch
Same here.
Same issue on latest stable Brave, Chrome, Edge, FF, and Safari + macOS 14.5 arm64.
It appears to be a common behavior where then browser extension fails to check if TouchID is available on a system that already had it.
Proper UX would wait for the user to open the lid or cancel rather than waste users' time with misinformation.
Given it's been 2 years so far, it's never going to be fixed.
Steps To Reproduce
While using a MacBook with TouchID in clamshell mode without a second biometric option
Expected Result
I expect the extension panel to ask for my master password as if no biometric option is setup.
Actual Result
the extension tells me that biometrics are unavailable on this device.
Screenshots or Videos
No response
Additional Context
This is unnecessary information
Operating System
macOS
Operating System Version
12.2.1
Web Browser
Safari
Browser Version
15.3
Build Version
1.56.6