Passkeys can not be retrieved / verified

[profpepper58]

Production Build

• I'm using the legacy Bitwarden app pubicly available in App Store / Play Store and I'm aware that Bitwarden Beta bugs should be reported in bitwarden/android or bitwarden/ios

Steps To Reproduce

1. Use passkey to unlock accounts (happens on my banking app and also Github).
2. Unlock vault with biometrics OR password.

Expected Result

Passkey successfully unlocks account.

Actual Result

Get error "Passkey operation failed because user could not be verified" followed by "we were unable to process your request. Please try again or contact us"

Screenshots or Videos

Cannot screenshot the app

Additional Context

Passkeys used to work about a week ago.

Operating System

Android

Operating System Version

14

Device

Samsung Galaxy A35 5G

Build Version

2025.1.0

[abergs]

We'll take a look! Is this error occurring at a specific website or multiple sites?

[SaintPatrck]

Hi @profpepper58

We're not able to replicate the exact issue you're reporting. Some more details may assist in troubleshooting.

Were your errors encountered while attempting to use passkeys in the native GitHub and Banking applications, or through a web browser?

If you were using a web browser, could you provide details of the browser? Name and version should suffice for now.

If you could provide the name of the Banking application, that would be helpful as well.

[SaintPatrck]

Moving this ticket to the new native Android repo for tracking.

[bitwarden-bot]

Thank you for your report! We've added this to our internal board for review.
ID: PM-17215

[profpepper58]

Hi,

I tested it on github in the mobile Firefox browser (134.0.1) the github app (1.192.0), and my banking app which is ubank (11.91.0) in Australia. If you'd like me to test the passkey somewhere else let me know.

Thanks.

[nategasm]

Can confirm getting the same issue with the uBank app on my Samsung Galaxy S24+. The app just constantly says "Something went wrong" when trying to login with the passkey. It does not prompt to unlock the vault. It also doesn't even detect standard passwords no matter how many new entries you add.

Was previously working fine with the legacy Bitwarden app

More reports and response from ubank here
https://forums.whirlpool.net.au/thread/9pxj7pkp?p=9#r161
https://forums.whirlpool.net.au/thread/90kv06m3?p=751#r15005

[BakedCrossiant]

Before it says "Something went wrong" it also says that the "user cannot be verified". Tested on Pixel 6.

[vrbt150]

Same issue as @nategasm. Running Android 14 on Samsung Galaxy S24 FE. Legacy app worked fine tho.

Also noticed an issue in WhatsApp when trying to create a passkey with Bitwarden. Bitwarden seems to create it, but WhatsApp doesn't realise it has been created.

[RupertMichaelBear]

Just to add to t his, same issue with my Galaxy S22u, Android 14 and my Australian banking App (Ubank). Worked until the recent Bitwarden update. Still using email for 2FA here

[vrbt150]

Just upgraded to 2025.1.1 and issue is still persistent. Having to use another password manager to handle passkeys for UBank otherwise I need to login with username, password, and SMS 2FA every time (painful).

[SaintPatrck]

Hi all. We're still investigating the issue with uBank and will provide an update as soon as we have more information.

Regarding the WhatsApp problem: I believe this is a bug on WhatsApp's end.

I was able to replicate passkey creation failure when registration is triggered from the Settings screen in WhatsApp. There are no logs indicating anything is wrong on our end during this process. WhatsApp appears to silently fail when it receives our response.

However, if you choose to create a passkey while signing in to WhatsApp for the first time, registration completes on our end and WhatsApp accepts the response. Navigating to Settings > Passkeys, you can see the passkey was successfully registered in WhatsApp's system. Unfortunately there's nothing more we can do on our end at this time to improve the WhatsApp behavior. I suggest reaching out to WhatsApp and informing them of this issue if you're able to replicate it as consistently as I was.

[BJReplay]

Hi all. We're still investigating the issue with uBank and will provide an update as soon as we have more information.

Hi @SaintPatrck, issue #3866 provides additional information about the issue with UBank, including screenshots, and that Bitwarden legacy does work, KeyGuard does work, but that Bitwarden native (tested right up to:
© Bitwarden Inc. 2015-2025

Version: 2025.1.1 (19728)
📱 samsung SM-S908E 🤖 14@34 📦 beta
local) does not, all accessing the same passkey in the same vault.

[vrbt150]

Hi all. We're still investigating the issue with uBank and will provide an update as soon as we have more information.

Regarding the WhatsApp problem: I believe this is a bug on WhatsApp's end.

I was able to replicate passkey creation failure when registration is triggered from the Settings screen in WhatsApp. There are no logs indicating anything is wrong on our end during this process. WhatsApp appears to silently fail when it receives our response.

However, if you choose to create a passkey while signing in to WhatsApp for the first time, registration completes on our end and WhatsApp accepts the response. Navigating to Settings > Passkeys, you can see the passkey was successfully registered in WhatsApp's system. Unfortunately there's nothing more we can do on our end at this time to improve the WhatsApp behavior. I suggest reaching out to WhatsApp and informing them of this issue if you're able to replicate it as consistently as I was.

Hi, just to add, passkeys worked on WhatsApp with Bitwarden legacy and all other password managers I have tested with (1Password, Proton Pass, and Google Password Manager). Regardless, I will contact WhatsApp as suggested. Thanks