bitwarden / clients

Bitwarden client apps (web, browser extension, desktop, and cli).
https://bitwarden.com
Other
9.3k stars 1.25k forks source link

No TouchID on MS Edge Plugin on MacOS 15 #11168

Open NovaSilentium opened 1 month ago

NovaSilentium commented 1 month ago

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

erdh commented 1 month ago

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: Screenshot 2024-09-20 at 21 32 40

piyushaswani55 commented 1 month ago

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)

SergeantConfused commented 1 month ago

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,

bmmuratcan commented 1 month ago

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.

SuperMari0s commented 1 month ago

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 !

samholmes commented 1 month ago

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)

HomeQi commented 1 month ago

What can I do if the Appstore cannot return older versions?

bmmuratcan commented 1 month ago

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?

nicolasnoel commented 1 month ago

It is now on the app store :

image
martinjgrunwald commented 1 month ago

Updating to Version 2024.9.0 fixed the issue for me

bmmuratcan commented 1 month ago

It is now on the app store : image

Updating to Version 2024.9.0 did solve the problem for me. Needed a restart(keep in mind)

mcx808 commented 1 month ago

@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.

pistolwhip-justin commented 1 month ago

I am using the 2024.9.1 extension {Edge} and the 2024.9.0 client and it is NOT working for me.

damitti444 commented 1 month ago

Can confirm Biometrics not working on:

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/

TTECGH commented 1 month ago

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

PcFan commented 1 month ago

Having the issue on the desktop client (2024.9.0) and on the edge extension (2024.10.0) too.

Is there an ETA for the fix and any tips to prevent such issues in the future?

Toryalai1 commented 3 weeks ago

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

PcFan commented 3 weeks ago

@Toryalai1 The bitwarden extension requires the started desktop app for biometric unlocks. The encryption key is stored there iirc.

opswiz commented 2 weeks ago
Screenshot 2024-10-26 at 11 41 37 AM

Getting this error when I try to enable browser integration in desktop app. using v2024.10.0

jaschaschopfer commented 2 weeks ago
Screenshot 2024-10-26 at 11 41 37 AM

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)

huylv commented 1 day ago

Same problem with version 2024.10.1 on macOS/Chrome