Bitwarden 30 June update
Android 15 Security Patch Level 1 June 2025 - updated 25 June
Samsung Galaxy S24
I had no problems until today but in a couple of different applications I’m getting “authentication failed” error in one application (GitHub - but username and password with 2FA is fine) and “the interaction with your security device was cancelled or timed out” in another. Bitwarden doesn’t even pop up for the biometrics.
Everything is fine in desktop and iPad.
I’ve tried powering off and restarting the phone but still no joy.
This looks like the real risk with passkeys, ie I can just copy/retype passwords into another device, but if there is a bug and passkeys stored in password manager are involved, I’m blocked from using the device.
Sounds like testing should be ramped up significantly for bitwarden testing different platforms and devices even ahead of their releases. Otherwise with increasing shift to passkeys these kinds of problems will regularly lead to serious problems for users
Yes, as it happens I first ran into this in an application that is passkey access-only, unlike GitHub. This is the new Internet Identity associated with the Internet Computer Protocol project. This is used as a “key” (login) to most of the applications in the ecosystem. So, on mobile, I cannot currently access any of them. But desktop and iPad are fine.
There is this banner on the Welcome page, which I assume covers us
Bitwarden is aware of an issue with biometric unlock when using the Firefox and Opera browser extension. The issue will be resolved as soon as the 2025.6.0 version of the browser extension is approved and available for those browsers.
In my case, I am in fact using Opera on Android. I think I could set up a new passkey via another browser but, as this is not urgent for me right now, I’ll wait to see if this update resolves it.
The banner is there because of biometric unlock problems on desktop, so I don’t think it is directly related to the passkey problems on Android… but it might be a good idea to try it with a different browser, nonetheless!
Yes, it refers to desktop but there’s a chance it might fix my problem too, especially as they explicitly mention Opera, which is where mine was set up.
Hey all, I work a lot on our passkey features. Thanks for bringing this up so we can look into fixing it.
I just want to grab some more info:
This is only happening on Android, correct?
What version of Bitwarden are you running?
What version of Android, and what browser?
If Chrome, what version of Chrome?
We’re currently having a conversation with the Chrome team who recently launched an update that causes quite a few autofill failures, so I just want to make sure we’re nailing this down to be a bitwarden specific issue and not related to the recent chrome update.
Does downgrading the Bitwarden app resolve the issue?
is this happening on a specific website or App - or on all websites and/or apps?
Yes, only on Android. No problem on PC (Windows) and iPad
Android 15 Security Patch Level 1 June 2025
Bitwarden 2025.6.1 (20398)
Opera - Chromium 137, Security Updates 2025-07-02
On Android I’ve verified that I can sign into GitHub with passkey using Vivaldi instead of Opera.
I can also sign into another application that I think is using the passkey stored in the device, rather than Bitwarden.
But I can’t do either of these operations in Opera. It might actually be a problem with Opera actually, or perhaps a combination of the two? It’s a bit confusing.
But I can’t do either of these operations in Opera. It might actually be a problem with Opera actually, or perhaps a combination of the two? It’s a bit confusing.
Yes - I don’t believe Opera works with any third passkey provider at the moment(?). Could anyone from the community verify that for me?
@kevinmcfarlane Did Opera passkeys + bitwarden work your at any point in the past?