Yesterday I wanted to recreate a passkey, but it failed. Tried the same for multiple logins (Amazon, eBay, PayPal, …), but none of the passkeys could be created.
Bitwarden saves the new passkey in the selected login, but the server seems to not receive any passkey data and returns a general error message to retry.
Using the Bitwarden App on Android 15 with a Pixel 7a if it helps.
Existing passkeys still work.
Testing with another Android device, although being the default autofill app, bitwarden never starts or is recognized but the default Google password manager happily shows up.
While this is another common problem with bitwarden…Can you still create passkeys?
Everything works as expected with the Google Password Manager, so it is definitely a Bitwarden issue.
Passkeys are still iffy in general currently due to the varied ways different sites implement them (and the degree that they implement them correctly).
I experience enough challenges trying to set them up on some sites using the browser extension - I don’t think I’d even try to create one using a mobile app. Can you create them using the browser extension, for the sites that you are having problems with?
Something which I found as a weird fix is that if you have an iPhone and an Android device, you can download the app / open the website you want to create the passkey on, select the QR code option on the iPhone, scan it with your android, and it will register on both the android device and the website/App and can be usable on android since it got saved when you try and login.
Obviously it’s not a perfect solution, and it required 2 devices, but if you do have that option, and you are desperate for your passkey to be saved, it can resolve it for you until the Bitwarden team can find a solution for this problem.
I reported this a year ago, but was told to set up chrome flags (they were set), and the issue was closed.
As I had some other issues with passkeys on the device at the time (Xiaomi 12 Pro), I attributed it to that.
Have changed devices in the meantime (Xiaomi 15), but this still doesn’t work. Neither on passkeys.io, nor on passkeys.eu.
I’ve never tried using BW to create a Passkey, only to log in with them.
Passkeys are still way too buggy within the websites that utilize them (inconsistent functionality) so I always create new Passkeys using the web browser interface.
As it works with the browser extension ( guess this is what you meant) and other password managers (Google, MS,…), it is obviously a Bitwarden-Android issue, not an Amazon or PayPal one.
It is promoted, documented and released, but doesn’t work for quite some time. Has this ever been tested?
I can live without being able to create passkeys using the app. Just make it clear that it is not supported and remove the functionality.
Same for autofill. Works most of the times with the extension, on Android almost every time the browser or app needs to be restarted. Sometimes autofill never shows, or when it does, fields are not populated.
Maybe it’s just me, but either fix it or let it go.
I can USE existing passkeys (created elsewhere - like iOS or Desktop, and saved to bitwarden) just fine. But if I try to create a new passkey on Android (Android 15, bitwarden 2025.8.0), it will “save” a passkey to bitwarden, but it doesn’t communicate something that is required back to the website or app so it fails. Then if I try to log in with the newly saved passkey, it fails because the creation wasn’t successful on the application/website end.
I don’t exactly understand what communication is happening between the website/app and bitwarden, but something isn’t getting communicated back that is necessary for the passkey creation to be successful.
But if I create it on desktop or iOS and save it to bitwarden, I can successfully log into the same website or app on the same anrdoid device using bitwarden.
Same here. I wonder what details or progress has been made about the passkey creation failures with Android. So far, on my own, I rely on desktop to create the passkeys and hope Android can use it (so far ok), but very irritating to depend on computer when Google Password Manager does it without hiccup.
This is still broken. There was a recent update to the android app that sounded like it may have addressed the issue, but alas, it still doesn’t work even with the most recent update. That is unfortunate.
I agree with @discernment - it’s odd that this is still not working when it works perfectly fine with the native google password manager and other 3rd party solutions.
Thanks for the reply. That comment involves a different issue where it was trying to save passkeys to google instead of bitwarden. I didn’t have that issue.
Nonetheless, I did it anyways (changed it back to google, then changed it back to bitwarden).
Still having the same issue. The passkey DOES successfully save to bitwarden, but doesn’t communicate something back to the app/website. So the website errors out “The request either timed out, was canceled, or the device is already registered. Please try again.”
Tried it on amazon - same thing. Saves to bitwarden, but then amazon says “Hmm, try setting up your passkey again. Make sure to follow the instruction in the next step”. As such, the saved passkey is not valid and doesn’t work for login. A passkey appears in Bitwarden afterwards, but amazon still shows no passkey set up…
@samwathegreat Okay, just in short: I would continue this discussion on GitHub issues then, as bugs are reported there, and we can’t do much about real bugs on the Community Forum here. – The first bug report I reported here is still open - it seems the second one was closed a few days ago.
Thank you for your response samwathegreat. My comments and posts have been unnoticed everywhere. Im currently using Proton with no issues, I like Bitwarden, but I have gotten no support response fix.
