bitwarden
No TouchID on MS Edge Plugin on MacOS 15
Steps To Reproduce
1.Open the Microsoft Edge browser on macOS/ Windows 2.Ensure the Bitwarden native app is open, unlocked, and the Touch ID integration is enabled in the app. 3.Attempt to unlock the Bitwarden plugin using Touch ID.
Expected Result
The plugin should unlock successfully when using Touch ID.
Actual Result
No response occurs when attempting to unlock with Touch ID; the plugin remains locked.
Screenshots or Videos
No response
Additional Context
No response
Operating System
macOS, Windows
Operating System Version,
macOS 15 Sequoia, Windows 11 Pro
Web Browser
Chrome, Microsoft Edge
Browser Version
No response
Build Version
2024.9.0
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.
Can also reproduce on Brave Browser on macOS 15. Using "inspect popup" on extension shows these error messages on console when initiating unlock with biometrics:
I am facing the same issue and confirm this unexpected behaviour. I have tried re-installing all the client apps thinking there was something wrong until I found this bug report. Hope this gets fixed soon.
I installed Bitwarden from App Store just because of this feature, now it feels senseless to use the App Store version. (Have my own reservations against limiting that feature to App Store version and not enabling it for Bitwarden installed via brew or dmg file, but it's broken anyway)
Hello everyone,
Please note that this is reproducible also on Windows 11 Pro with Bitwarden browser extension 2024.9.1 in Edge 129.0, Chrome 129.0, Brave 1.70.117 and Vivaldi 6.9.3447.46, when used with Bitwarden desktop 2024.8.2.
Update: This works as expected when using the 2024.9.1 browser extension with desktop client version 2024.9.0. If you're running Windows, you can download a fresh new .exe installer to manually update the desktop client.
All the best,
Bitwarden browser extension "2024.9.1" is the problem 2024.9.0 works fine with chrome update to 2024.9.1 than touch id promp never appears, sometimes extention give some errors.
Hello everyone,
Please note that this is reproducible also on Windows 11 Pro with Bitwarden browser extension 2024.9.1 in Edge 129.0, Chrome 129.0, Brave 1.70.117 and Vivaldi 6.9.3447.46, when used with Bitwarden desktop 2024.8.2.
Update: This works as expected when using the 2024.9.1 browser extension with desktop client version 2024.9.0. If you're running Windows, you can download a fresh new .exe installer to manually update the desktop client.
All the best,
I can confirm that manually updating to 2024.9.0 with the installer (since check for update does not show an update) resolves the issue ! Thanks !
I can confirm this is also an issue for:
2024.9.0 Bitwarden Password Manager Extension on Arc Version 1.61.0 (53949) on macOS 14.2.1 (23C71)
macOS Version: 15.0 Sequoia Bitwarden Desktop Version: 2024.8.2 (29359) Google Chrome Version: 129.0.6668.60 (Official Build) (arm64) Bitwarden Chrome Extension Version: 2024.9.1 The Touch ID unlock feature in the Chrome extension does not work after the extension was updated.
Updating the desktop version to 2024.9.0 might solve the problem (as in Windows versions): (Did solve the problem)
The App Store version did not receive this update. The GitHub release (via DMG file) cannot use Touch ID (only App Store apps can). What am I supposed to do to fix this issue?
It is now on the app store :
Updating to Version 2024.9.0 did solve the problem for me. Needed a restart(keep in mind)
@NovaSilentium , I can confirm this is now fixed in v2024.9.0.
Since it was my support ticket that caused this issue to be opened it can be closed for me.
I am using the 2024.9.1 extension {Edge} and the 2024.9.0 client and it is NOT working for me.
Can confirm Biometrics not working on:
- macOS 15.0 (24A335)
- Bitwarden App 2024.3.0
- FireFox 131.0 (aarch64)
- Bitwarden Add-On 2024.9.1
I downgraded the Add-On in the meantime as a temporary solution to v2024.9.0 from https://addons.mozilla.org/de/firefox/addon/bitwarden-password-manager/versions/
Can someone please explain how to fix this issue, I have read the thread comments above but can't see the process to resolve, other than to update Bitwarden. I am on 2024.10.0 and still have this issue.
Tony
Having the issue on the desktop client (2024.9.0) and on the edge extension (2024.10.0) too.
- Bitwarden client is already on latest
- Edge does not allow installing specific versions
Is there an ETA for the fix and any tips to prevent such issues in the future?
I don't know why my ticket (https://github.com/bitwarden/clients/issues/11553) got closed and referred here. But the issue I have is that the browser extension is dependent on the desktop app when I want to log into with biometrics. In my opinion, it should be independent
@Toryalai1 The bitwarden extension requires the started desktop app for biometric unlocks. The encryption key is stored there iirc.
Getting this error when I try to enable browser integration in desktop app. using v2024.10.0
Getting this error when I try to enable browser integration in desktop app. using v2024.10.0
Same here. bitwarden Version 2024.10.0 (31484)
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.
Can confirm: Fixed in app store version 2024.11.0 for Brave with extension version 2024.11.0.
Same error here using latest bitwarden desktop available at appstore: 2024.11.0 (33157)
@ian-pascoe:
I am still having this issue with helium (ungoogled chromium)
I think "Ungoogled Chromium" is not supported as a browser at this point in time by Bitwarden,
I am still having this issue with helium (ungoogled chromium)
I think "Ungoogled Chromium" is not supported as a browser at this point in time by Bitwarden,
Everything else is working to this point. Right now, just using PIN unlock as a workaround
As a workarround you can manually copy the NativeMessagingHosts file from a supported browser to the one you are using. Instructions for chromium based browsers:
- go to chrome://version and check the profile path. you will need to use this path, just without the profile. for chrome its
~/Library/Application Support/Google/Chrome, for Helium~/Library/Application Support/net.imput.helium. - copy the
com.8bit.bitwarden.jsonfile from theNativeMessagingHostsdirectory (in the path from earlier) from a supported browser to the one you want to use. in my case it was helium and i also needed to create the NativeMessagingHosts directory.
mkdir "~/Library/Application Support/net.imput.helium/NativeMessagingHosts"
chmod 700 "~/Library/Application Support/net.imput.helium/NativeMessagingHosts"
cp "~/Library/Application Support/Google/Chrome/NativeMessagingHosts/com.8bit.bitwarden.json" "~/Library/Application Support/net.imput.helium/NativeMessagingHosts/"
i opend a PR (#17293) for adding support for Helium, but we would need to do this for every browser. Maybe a setting could be added in the future, where the user can set which browser they want to use?
