mirror of
https://github.com/bitwarden/android.git
synced 2026-03-09 03:33:36 -05:00
Can't create passkeys on Android browsers #2071
Open
opened 2025-11-26 23:06:56 -06:00 by GiteaMirror
·
37 comments
No Branch/Tag Specified
main
crowdin-pull
PM-33266-crashlytics-bug
PM-32123/cookie-sync-error-message
PM-29861-update-overflow-content-description
PM-33227/clear-cookies-debug-button
update-agp
PM-26059-remove-cipher-key-encryption-flag
remove-remember-viewmodel
PM-29871-external-links
PM-29673/flight-recorder-export-header-info
renovate/lock-file-maintenance
sdlc/sdk-update
release/2026.3-rc48
PM-24380/flight-recorder-redact-hostname
release/2026.2-rc47
PM-32714/fallback-to-web-vault-host
pr-6572
PM-28834/setting-app-layout-horizonos
PM-26896-autofill-fix
vvolkgang/process-release-notes-v2
PM-26577-app-links-support
release/2026.2-rc46
release/2026.1-rc45
PM-30644/added-logs-for-debug
PM-30644/quicktile-nav-not-showing-migration
minor-gradle-updates
release/2026.1-rc42
release/2026.1-rc44
release/2026.1-rc43
PM-28834/set-landscape-on-horizonos-devices
context-rules
devclarity/update-code-review-command
PM-20026/force-ltr-passwords-and-codes
release/2025.12-rc41
cmcg/testCoverage
claude-skill/creating-feature-flags
PM-29014/talkback-support-for-passwords
release/2025.12-rc40
BRE-1305/publish_test
accept-user-certs
autofill-permissions
release/2025.11-rc39
PM-22479/check-all-certificates-validate-asset-links
release/2025.10-rc38
agalles/android-latest
optimize-test-workflows
tier2-test-sharding
retro-agent
PM-27001/skip-account-selection-only-one-exists-cxp
release/2025.10-rc37
agalles/test-1118
release/2025.10-rc36
PM-20593-token-refresh
QA-1126b/adding-native-sanity-test
release/2025.9-rc35
pm-25933/sdk-update-password
release/2025.9-rc34
release/2025.8-rc33
agalles/20250821-release
debug-release-issues
pm-24249-allow-automated-prs-for-sdk-updates
release/2025.8-rc32
release/WORKFLOW-TEST-2025.8-rc28
agalles/20250807release
release/2025.07-rc25
release/hotfix-v2025.7.0-bwa
pm-23311/export-vault-policy-bypass
release/2025.07-rc24
authenticator-pm-sync-flags-issue
ps/implement-sdk-repository-example
release/hotfix-v2025.6.0-bwpm
release/2025.06-rc21
agalles/automate-android-fastlane-patch
release/2025.05-rc20
release/2025.04-rc19
languages/basque
release/2025.03-rc19
update-readme
qrcode/feature
innovation/archive/pm-19153-archive-items
qrcode/2-ui-fields
qrcode/1-page
hold-on-biometric-prompt-alternative
release-notes-process
release/2025.02-rc16
bwa-monorepo
PM-8223/new-device-verification-ux-improvements
pm-18451/exempt-from-policies
test-bwa
cs-workaround-linked-0-copy
release/2025.01-rc15
release/2025.01-rc14
release/2024.12-rc13
pm-16670/sync-leave-notice
821
PM-16695/backport-lean-more-new-device-verification
km/15084-testing
release/hotfix-v2024.11.7
release/2024.11-rc1
pm-11304/collection-add-item-button
PM-14241/disabling-logs-app-crash
poc/offline-editing
new-version-calc
pm-11649/expired-link-services
pm-6702/add-feature-flag
pm-6702/email-verification-feature
pm-9933/marketing-copy-update
pm-6702/registration-flows
update-templates
pm-6701/email-verification-selfhost-registration
v2026.2.1-bwpm
v2026.2.1-bwa
v2026.2.0-bwpm
v2026.2.0-bwa
v2026.1.1-bwa
v2026.1.1-bwpm
temp-test
v2026.1.0-bwpm
v2026.1.0-bwa
v2025.12.1-bwa
v2025.12.1-bwpm
v2025.12.0-bwa
v2025.12.0-bwpm
v2025.11.1-bwpm
v2025.11.1-bwa
v2025.11.0-bwpm
v2025.11.0-bwa
v2025.10.1-bwa
v2025.10.1-bwpm
v2025.10.0-bwa
v2025.10.0-bwpm
v2025.9.1-bwa
v2025.9.1-bwpm
v2025.9.0-bwa
v2025.9.0-bwpm
v2025.8.1-bwa
v2025.8.1-bwpm
v2025.8.0-bwa
v2025.8.0-bwpm
v2025.7.2-bwa
v2025.7.2-bwpm
v2025.7.1-bwa
v2025.7.1-bwpm
v2025.7.0-bwa
v2025.7.0-bwpm
v2025.6.1-bwpm
v2025.6.0-bwa
v2025.6.0-bwpm
v2025.1.0-bwa
v2025.5.0-bwa
v2025.5.0-bwpm
v2025.5.999
2025.4.0
v2025.4.0
untagged-4731eaadac73f3dfbbb8
v2025.3.0
v2025.2.0
untagged-815a165c5d70ffe75bc7
v2025.1.2
v2025.1.1
v2025.1.0
v2024.12.0
untagged-5a76b6392a4c8998c63a
v2024.11.7
v2024.11.6
v2024.11.5
v2024.11.4
v2024.11.3
v2024.11.2
v2024.11.1
v2024.11.0
v2024.10.2
v2024.10.1
v2024.10.0
v2024.9.0
v2024.8.1
v2024.8.0
v2024.7.3
v2024.7.2
v2024.7.1
v2024.7.0
v2024.6.1
v2024.6.0
v2024.5.1
v2024.4.1
v2024.4.2
v2024.4.0
v2024.3.3
v2024.3.1
v2024.3.0
v2024.2.1
v2024.2.0
v2024.1.1
v2024.1.0
v2023.12.0
v2023.10.0
v2023.9.2
maui-single-project-android
v2023.9.1
v2023.9.0
v2023.8.0
v2023.7.0
v2023.5.0
v2023.4.0
v2023.3.2
v2023.3.1
v2023.3.0
v2023.2.0
v2023.1.0
v2022.11.0
v2022.10.0
v2022.9.1
v2022.9.0
v2022.8.0
v2022.6.2
v2022.6.1
v2022.6.0
v2022.05.0
v2.18.0
v2.17.0
v2.16.4
v2.16.3
v2.16.2
v2.16.1
v2.15.0
v2.14.2
v2.14.1
v2.14.0
v2.13.0
v2.12.0
v2.11.3
v2.11.2
v2.11.1
v2.11.0
v2.10.0
v2.9.1
v2.9.0
v2.8.2
v2.8.1
v2.8.0
v2.7.2
v2.7.0
v2.6.1
v2.6.0
v2.5.6
v.2.5.5
v2.5.5
v2.5.4
v2.5.3
v2.5.2
v2.5.1
v2.5.0
v2.4.3
v2.4.2
v2.4.1
v2.4.0
v2.3.1
v2.3.0
v2.2.8
v2.2.7
v2.2.6
v2.2.2
v2.2.1
v2.2.0
v2.1.2
v2.1.0
v2.0.6
v2.0.5
v2.0.4
v2.0.3
v2.0.2
v2.0.1
v2.0.0
v1.22.1
v1.22.0
v1.21.0
v1.20.0
v1.19.0
v1.18.1
v1.18.0
v1.17.0
v1.16.0
v1.15.2
v1.15.1
v1.15.0
v1.14.4
v1.14.1
v1.14.0
v1.13.0
v1.12.2
v1.12.1
v1.12.0
v1.11.1
v1.11.0
v1.10.0
v1.9.0
v1.8.1
v1.8.0
v1.7.0
v1.6.5
v1.6.1
v1.6.0
v1.5.1
v1.5.0
v1.4.4
v1.4.3
v1.4.0
v1.3.0
v1.2.1
v1.2.0
v1.1.0
v1.0.0
v0.0.6
v0.0.5
v0.0.4
v0.0.3
v0.0.2
v0.0.1
Milestone
No items
No Milestone
Projects
Clear projects
No project
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/android#2071
Reference in New Issue
Block a user
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @ExtendedGuru4883 on GitHub (Nov 19, 2024).
Steps To Reproduce
Expected Result
Bitwarden pops up as passkey manager and lets you save the passkey
Actual Result
Google password manager pops up as passkey manager (example on Amazon.it)




When instead trying to use a passkey already stored in Bitwarden, you get two different behaviours:
If you also have passkey for that website on google password manager, it will pop up first but allows you to see "more passkeys", at which point Bitwarden appears
If you don't have a passkey for that website on google password manager, Bitwarden appears first
Screenshots or Videos
No response
Additional Context
I was able to create passkeys before, the problem appeared suddenly.
Tested in Chrome and Brave with same results.
Build Version
2024.11.5
What server are you connecting to?
US
Self-host Server Version
No response
Environment Details
Issue Tracking Info
@bitwarden-bot commented on GitHub (Nov 19, 2024):
Thank you for your report! We've added this to our internal board for review.
ID: PM-15044
@Felitendo commented on GitHub (Nov 23, 2024):
I am experiencing the same issue
@rmcdowell-bitwarden commented on GitHub (Nov 25, 2024):
Hi there,
Thank you for your report!
I was able to reproduce this issue, and I have flagged this to our engineering team.
If you wish to add any further information/screenshots/recordings etc., please feel free to do so at any time - our engineering team will be happy to review these.
Thanks once again!
@lucasmz-dev commented on GitHub (Dec 10, 2024):
This has been happening for me for a while now and no Chromium browsers seem to properly work (except this weird #4449), the difference is, I'm using microG (replaces Google Play Services and by extension the Google Password Manager) and it doesn't support passkeys really, so it just breaks. I have not been able to get stuff working on any browser. This worked many many months ago if not a year ago, they removed the flag and then added it back but then broken... so.. hm. I suppose this isn't a BW issue though.
@ExtendedGuru4883 commented on GitHub (Dec 10, 2024):
I see how it could be a problem with the implementation of passkeys on Android and not with Bitwarden itself. However right now Bitwarden's support for passkeys on mobile just seems broken as it only works sometimes and in some situations, while on their website they try to present it as fully functional.
@koffiato commented on GitHub (Dec 18, 2024):
Unfortunately still the case.
@memories169 commented on GitHub (Feb 5, 2025):
I have same problem with sony's site like playstation.com, xenforo forum like voz.vn and microsoft account too
Android 15
Xperia 1 vi
Bitwadern app: 2025.1.1
@MasterKeyxda commented on GitHub (Mar 3, 2025):
I have the same issue. Also commented on #4669
@AlphaCraft9658 commented on GitHub (Mar 19, 2025):
Same issue here. Worked in the past.
@LaikeSF commented on GitHub (May 29, 2025):
I have run into the same issue. I am able to save a pass key to Proton Pass, but not Bitwarden. I am on Android 15 using a Pixel 8a
@WesVanVugt commented on GitHub (Jun 11, 2025):
Same issue on Pixel 7 Pro, Android 16, on Firefox/Chrome. Reinstalling the BitWarden app does not resolve the issue.
@cad42s13 commented on GitHub (Jun 20, 2025):
Same issue. Bitwarden saves the passkey but the website doesn't receive it.
To those arguing that the websites are at fault: try adding a passkey to the bitwarden site under security settings. It fails on the EU site in the same way as it does on every other site that I have tried.
Moto Edge 50 Fusion.
5.10.218-android12-9-00057-g5659b677bceb-ab12885890
#1 Wed Jan 8 09:35:07 UTC 2025
@cad42s13 commented on GitHub (Jun 20, 2025):
Workaround: windows offers to link to you mobile phone. I'm not sure if having Microsoft authenticator on the phone is a pre requisite for this, but I do, and I'm logged into the PC and authenticator with the same account. If I follow the prompts in windows to create a passkey on my phone and then follow the prompts in bitwarden, it is saved properly in both bitwarden and the website.
I can then access the site from the browser on my phone with the passkey stored in bitwarden.
@Jebble commented on GitHub (Jul 15, 2025):
Same issue on a Samsung S4 on One UI
87/Android 15 on the EU server. Passkey is stored in Bitwarden but the origin never receives it. I've encountered this issue on all kinds of random applications and in fact haven't ever succesfully stored one in the app.@AlphaCraft9658 commented on GitHub (Jul 15, 2025):
Don't you mean OneUI 7?
@Jebble commented on GitHub (Jul 16, 2025):
Yep, typo.
@john-crane-69 commented on GitHub (Aug 4, 2025):
I found a temporary solution if you have both an iPhone and an android device to successfully save a passkey for your android use.
https://github.com/bitwarden/android/issues/4669#issuecomment-3149833238
@wvanvugt-speedline commented on GitHub (Aug 5, 2025):
I tested passkey creation on https://www.passkeys.io/ after applying the latest security update to my Pixel 7 Pro today and the prompt showed correctly. Unsure if it was the security update or a BitWarden update, but it seems the issue may be resolved. Any other updated Pixel users find this?
@MasterKeyxda commented on GitHub (Aug 5, 2025):
@wvanvugt-speedline the passkey issue is still present with Amazon website
@wvanvugt-speedline commented on GitHub (Aug 8, 2025):
Having had a bit more time to test the issue, I've noticed that the behavior of this issue seems to have changed for me from what was originally described in this issue (ie. Google Password Manager responding to prompts for passkey creation, instead of BitWarden). Now the behavior seems to be that BitWarden shows the prompt and saves the passkey, but the website considers the passkey registration to be a failure. BitWarden is left with a stored passkey which does not work. I see a number of other users have also reported this new behavior.
I tested using Google Password Manager and the passkey registration works correctly.
@Zoran-B commented on GitHub (Aug 12, 2025):
Curiously, I reported this almost a year ago in #3743, but it was closed after just 5 days. My subsequent clarifications did not gain traction.
The difference now is that the passkeys.io website now displays an error box which a year ago it didn't
Curiously, I reported the mismatch in the logo displayed ("Google Password Manager" instead of "Bitwarden" in #3742, but that didn't gain traction as well.
Still happening:
Must be me or something'
@pamperer562580892423 commented on GitHub (Aug 16, 2025):
@Zoran-B I get the same error message with
passkeys.ioon my Android 15 device.PS: And this was also reported here in the meantime: https://github.com/bitwarden/android/issues/4669
@memories169 commented on GitHub (Aug 16, 2025):
I have same issue when use MS Edge android to create passkey on MS account and passkeys.io.
But when i switched to firefox nightly, it work perfect for me
@joel-bourquard commented on GitHub (Aug 16, 2025):
Ah indeed!
For me on Android it fails with Chrome (default settings) and with Firefox.
But it works on Firefox Nightly (tested with Google and Amazon). On the websites the passkey is labeled as "iCloud Keychain" though.
@Zoran-B commented on GitHub (Sep 8, 2025):
Android 16, Edge and Bitwarden 2025.8.1(20670) combo still suffers from the same issue.
@WingedSeal commented on GitHub (Sep 26, 2025):
Still having the same issue on Brave and Chrome, MagicOS9 (Android 15) honor phone.
@samwathegreat commented on GitHub (Oct 10, 2025):
same exact issue - more details here: https://community.bitwarden.com/t/passkey-creation-fails-on-android/82841/14
Here is the quick explanation:
When you try to generate a new passkey, it DOES successfully save to bitwarden, but something isn't communicated back to the website to complete the process, so even though a passkey is saved, it doesn't work and you get an error from the website that it was unsuccessful. Something like "Hmm, that didn't work. Please try again".
Frustrating because google password manager and other 3rd party implementations such as Proton Pass are working fine.
If you successfully generate a passkey on another platform (desktop chrome, iOS, etc) and save it to Bitwarden, you CAN use that passkey to LOGIN on the android device. But you CAN NOT generate a new passkey on the device due to this bug.
EDIT: As an update, I WAS just able to successfully create a passkey at webauthn.io and use it! But it still doesn't work for passkeys.io, or AMAZON, or several others I've tried. I wonder what the difference is here...
@pamperer562580892423 commented on GitHub (Oct 11, 2025):
@samwathegreat:
It worked for me on Amazon just today (Android 15, mobile app 2025.9.1). 🤔
@charlie2alpha commented on GitHub (Oct 11, 2025):
Same version, Android 16 on a Google Pixel 6 Pro, doesn't work. Same for my pixel tablet.
@charlie2alpha commented on GitHub (Oct 11, 2025):
@pamperer562580892423 that was on Chrome. Just doesn't work.
@pamperer562580892423 commented on GitHub (Oct 11, 2025):
@charlie2alpha Sorry, I deleted my previous post as I tested it at bit further (and I think I was wrong about using another browser successfully). Both Chrome and Brave fail for me, though differently. BUT: using the Amazon app does work for me - now, and I guess a few hours ago it was the Amazon app as well where it worked. Did you try it with the Amazon app directly?
PS: Probably still a bug, that it doesn't work in a browser... or Amazon restricts/prohibits that?!
@john-crane-69 commented on GitHub (Oct 13, 2025):
passkeys.io still not working with the latest update but also a new website which I didn't expect is account.nintendo.com you can login but cannot create a passkey, also gives out the error. It saves the passkey just like in passkeys.io but doesn't register in the website itself.
Many people mentioned amazon, it works on the app but not through the browser, very strange behavior.
@pamperer562580892423 commented on GitHub (Oct 13, 2025):
It also doesn't work on the Community Forum (https://community.bitwarden.com) at the moment. - I think I agree that there is something very wrong right now with passkey creation on Android.
A failed attempt on Android can also influence the browser extension - at least until the next "full sync", it seems: https://github.com/bitwarden/clients/issues/16842
@pamperer562580892423 commented on GitHub (Oct 13, 2025):
@john-crane-69 According to this comment, I think the fix for passkeys.io (and whatever other sites?!) is yet to come...
@pamperer562580892423 commented on GitHub (Oct 22, 2025):
As Android app version 2025.10.0 arrived for me yesterday, I now tested several things again.
So, now I can create passkeys (in some cases: again) successfully:
But:
For all collected "tips" regarding autofill on Android, I would also recommend this short guide on the Community Forum: https://community.bitwarden.com/t/short-guide-tips-autofill-on-android/88941
@john-crane-69 commented on GitHub (Oct 22, 2025):
I tested it on the previous mention of mine: accounts.nintendo.com and it seem to be working as well.
Thank you for the testing and thank you Bitwarden team for always fixing these bugs and giving us the best experience possible.
All is left is the ability to backup passkeys and Bitwarden will be the god of all password managers (I'm aware it's not in their hands yet and the devs of passkeys are working on it still)
@pamperer562580892423 commented on GitHub (Oct 22, 2025):
@john-crane-69:
I think you're alluding to CXP/CXF (https://www.corbado.com/blog/credential-exchange-protocol-cxp-credential-exchange-format-cxf), but when you make a JSON export of your Bitwarden vault, then passkeys are already included in that export.