Passkey creation fails on Android

That is unfortunate indeed. If you still have the ticket number, maybe let @dwbit know of it.

From your other thread:

Realized earlier today many more websites I can not create passkeys including Amazon, MyChart, and eBay using my Android mobile.

I just tested this a bit. I can successfully create a passkey for Amazon via my Android 15 device (Bitwarden vault of course – PS: and only via the Amazon app!). – eBay was not successful for me, and I just wrote a comment in this GitHub issue about that – I think it was wrongfully closed.

Creating passkeys Logging in with a passkey to a Google account on mobile seems to be an open issue, according to this comment from a BW developer.

I didn’t test “MyChart”.

Hm, as it works (at least) with Amazon, it doesn’t seem to be a general issue. Maybe have a look into this general guide also for the latest tips for setting it up: [Short Guide / Tips] Autofill on Android


PS: I now tried to create a passkey for this forum, and that fails also with the mobile app. But as I wanted to re-create my “old passkey” now, it also fails with the browser extension. (with the same error message) :thinking:

(extension 2025.9.0 – mobile app 2025.9.1)


PPS: Maybe some of those passkey issues on mobile might be resolved with one of the next releases (according to this comment from a BW developer).

Hi there,

I’m a little lost here.

I tried setting up a passkey on ebay but that failed multiple times. It worked with the Google password manager. I also tried creating a passkey for the Bitwarden community and guess what: again the Bitwarden passwordmanager failed and Google worked flawlessly.

I’m on a Pixel 6 with the latest android 16, all apps are up to date and I’m using brave. The experimental autofill-update-context-for-web-contents brave flag is also set but that shouldn’t really matter here.

Any ideas? Is this the correct thread?

@Printable Welcome to the party. – I’m not sure if you saw that, but I can confirm what you described (just above your post).

Yeah… but if it’s not a configurational issue (and some things here definitely aren’t), then bugs have to be reported and discussed on GitHub… see above for a few existing issues on GitHub…

I thought maybe it would resolve by Android 16 update that I received , but it did not.

Happy to report, it’s working now. I assume a Bitwarden update fixed the issue. Moto g 2025, android 16, Brave, Gboard.