Bitwarden Firefox entension no longer unlocks using biometrics

[godfrey62]

Steps To Reproduce

1. In Firefox (version 131.0 aarch64, macOS Sonoma) go to a web page that requires a login
2. Bitwarden Extension icon has a padlock (i.e. it's locked)
3. Click the Bitwarden Extension
4. The Extension opens, the options are to enter Master Password or unlock with biometrics
5. Click "Unlock with biometrics" - nothing happens, usually another window opens requestion touch ID to unlock
6. This problem happens even when Bitwarden Desktop app (version 2024.8.0 (28594)) is running and has been unlocked.
7. This problem was first observed on 25-Sep-2024

Expected Result

When "Unlock with biometrics" is clicked another window (from macOS) requests Touch ID

Actual Result

When "Unlock with biometrics" is clicked nothing happens and Bitwarden Extension remains locked. It can only be opened using Master Password even when Bitwarden Desktp app is running and unlocked.

Screenshots or Videos

Screen.Recording.2024-10-03.at.13.28.50.mp4

Additional Context

No response

Githash Version

I don't have a GitHub domain

Environment Details

macOS Sonoma 14.7 on M1 MacBook Air

Database Image

No response

Issue-Link

#2480

Issue Tracking Info

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

[Krychaz]

Hey,

Can you please confirm which version of Bitwarden Unified you are running?

[godfrey62]

Hello, I am running: Desktop app version 2024.8.0 (28594) Firefox extension version 2024.9.1 on macOS Sonoma 14.7

…

On 7 Oct 2024, at 07:37, Krystian Kan ***@***.***> wrote: Hey, Can you please confirm which version of Bitwarden Unified you are running? — Reply to this email directly, view it on GitHub <#4847 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AL4CDFGWPM7X5KWJ6MMR6IDZ2IT27AVCNFSM6AAAAABPJWHEEWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGOJWGAZDIOJTGE>. You are receiving this because you authored the thread.

[Krychaz]

You've marked this issue as Bitwarden Unified. Can you confirm if you are indeed running a self-hosted Unified deployment?

[godfrey62]

I don’t understand what Bitwarden Unified is, I don’t know what a “self-hosted Unified deployment” is, I’m a tech savvy home user but I don’t have servers or any self-hosting gear at home. If I marked it as self-hosting then it was in error. GitHub is not a great place to raise Bitwarden issues, it assumes a level of technical expertise that I do not have.

…

On 7 Oct 2024, at 13:14, Krystian Kan ***@***.***> wrote: You've marked this issue as Bitwarden Unified. Can you confirm if you are indeed running a self-hosted Unified deployment? — Reply to this email directly, view it on GitHub <#4847 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AL4CDFCNACXI5D6NGES7PLDZ2J3I5AVCNFSM6AAAAABPJWHEEWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGOJWG43DANBSHE>. You are receiving this because you authored the thread.

[Krychaz]

Hi,

We use GitHub issues as a place to track bugs and other development related issues. If your issue persists, please write us back using our “Contact support” form located on our Help Center (https://bitwarden.com/help/).

You can include a link to this issue in the message content.

Alternatively, you can also search for an answer in our help documentation or get help from other Bitwarden users on our community forums (https://community.bitwarden.com/c/support/).

The issue here will be closed.