You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Bitwarden present one confirmation dialog, and when the passkey is confirmed, you login successfully
Actual Result
Bitwarden present me with 2 confirmation dialogs (at the same time) and immediatly fails to login.
Screenshots or Videos
No response
Additional Context
Around the time of the great UI update, passkeys login broke for me.
I get two passkey confirmation dialogs instead of one, but no matter which or if I click both, the passkey login fails. In fact, it fails before I even click. On passkey.io, I immediately get a "The request either timed out, was canceled or the device is already registered. Please try again or try using another device." When trying to register a new account passkey as a test (Using a fresh email address I have never used on passkey.io before).
This problem occurs on Google with both of my google accounts (A business account for my custom domain as well as an gmail account).
It also occurs on my self-hosted Authentik instance when trying to login to my self hosted apps. Please note I am using a Bitwarden.com account, not a self hosted instance of bitwarden.
What I Tried:
At first I just reinstalled the newest version of the Firefox plugin, but that did not resolve the issue. So I reverted to the old version from 2024.11.2, and the old version works fine. This confirms for me that the issue is in fact with the newer version.
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.
The text was updated successfully, but these errors were encountered:
I just wanted to update this with some more info- I installed Firefox Developer Edition as I need to do some web development- and the newest Bitwarden is working fine with passkeys on it so far.
It seems like there may be a conflict with the new Bitwarden version and Firefox ESR releases.
I am unable to reproduce this issue on Firefox 128.5.1 esr, and it has been escalated for further investigation.
If you have more information that can help us, please add it below.
Steps To Reproduce
Try to login to an account with passkeys.
Expected Result
Bitwarden present one confirmation dialog, and when the passkey is confirmed, you login successfully
Actual Result
Bitwarden present me with 2 confirmation dialogs (at the same time) and immediatly fails to login.
Screenshots or Videos
No response
Additional Context
Around the time of the great UI update, passkeys login broke for me.
I get two passkey confirmation dialogs instead of one, but no matter which or if I click both, the passkey login fails. In fact, it fails before I even click. On passkey.io, I immediately get a "The request either timed out, was canceled or the device is already registered. Please try again or try using another device." When trying to register a new account passkey as a test (Using a fresh email address I have never used on passkey.io before).
This problem occurs on Google with both of my google accounts (A business account for my custom domain as well as an gmail account).
It also occurs on my self-hosted Authentik instance when trying to login to my self hosted apps. Please note I am using a Bitwarden.com account, not a self hosted instance of bitwarden.
What I Tried:
At first I just reinstalled the newest version of the Firefox plugin, but that did not resolve the issue. So I reverted to the old version from 2024.11.2, and the old version works fine. This confirms for me that the issue is in fact with the newer version.
My System:
Debian: uname -a: Linux office1 6.1.0-28-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.119-1 (2024-11-22) x86_64 GNU/Linux
Firefox: 128.5.1esr
Operating System
Linux
Operating System Version
Debian 12
Web Browser
Firefox
Browser Version
128.5.1esr
Build Version
2024.12.3
Issue Tracking Info
The text was updated successfully, but these errors were encountered: