Cannot create passkeys #2161

Closed
opened 2025-11-26 23:10:36 -06:00 by GiteaMirror · 23 comments
Owner

Originally created by @nordic-style on GitHub (Feb 1, 2025).

Steps To Reproduce

  1. Go to any website that supports passkeys. For this bug i use "https://passkeys.io"
  2. Click on "Don't have an account?"
  3. Fill e-mail address
  4. Click on Continue
  5. Click on "Create a passkey"
  6. Make sure bitwarden is selected and click on "create"
  7. Click on "Save as new ..." in the bitwarden app
  8. Click on "save"
  9. Authenticate with BIO or Password
  10. You are redirected to the website which says "The request either timed out, was canceled ot the device is already registered. Please try again or try using another device."

Expected Result

Create a passkey in bitwarden that is linked to the website (in this case passkeys.io).

Actual Result

A passkey is created in bitwarden but is not linked with the website.

Screenshots or Videos

Image
Image

Additional Context

This is different from the report of #4331 so i created a new one.

Build Version

19622

What server are you connecting to?

EU

Self-host Server Version

No response

Environment Details

Google Pixel 9 Pro (Android 15) and Galaxy S23 (Android 14)with current Chrome Browser

Issue Tracking Info

  • I understand that work is tracked outside of Github. A PR will be linked to this issue should one be opened to address it, but Bitwarden doesn't use fields like "assigned", "milestone", or "project" to track progress.
Originally created by @nordic-style on GitHub (Feb 1, 2025). ### Steps To Reproduce 1. Go to any website that supports passkeys. For this bug i use "https://passkeys.io" 2. Click on "Don't have an account?" 3. Fill e-mail address 4. Click on Continue 5. Click on "Create a passkey" 6. Make sure bitwarden is selected and click on "create" 7. Click on "Save as new ..." in the bitwarden app 8. Click on "save" 9. Authenticate with BIO or Password 10. You are redirected to the website which says "The request either timed out, was canceled ot the device is already registered. Please try again or try using another device." ### Expected Result Create a passkey in bitwarden that is linked to the website (in this case passkeys.io). ### Actual Result A passkey is created in bitwarden but is not linked with the website. ### Screenshots or Videos ![Image](https://github.com/user-attachments/assets/48557b3b-5a3d-4b5d-b817-83dad98e955b) ![Image](https://github.com/user-attachments/assets/0538aa9f-0341-4651-b677-008b2b174baf) ### Additional Context This is different from the report of #4331 so i created a new one. ### Build Version 19622 ### What server are you connecting to? EU ### Self-host Server Version _No response_ ### Environment Details Google Pixel 9 Pro (Android 15) and Galaxy S23 (Android 14)with current Chrome Browser ### Issue Tracking Info - [x] I understand that work is tracked outside of Github. A PR will be linked to this issue should one be opened to address it, but Bitwarden doesn't use fields like "assigned", "milestone", or "project" to track progress.
GiteaMirror added the bug-passkeyapp:password-managerbug labels 2025-11-26 23:10:36 -06:00
Author
Owner

@bitwarden-bot commented on GitHub (Feb 1, 2025):

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

@bitwarden-bot commented on GitHub (Feb 1, 2025): Thank you for your report! We've added this to our internal board for review. ID: PM-17870
Author
Owner

@SaintPatrck commented on GitHub (Feb 3, 2025):

Hi @nordic-style

I was able to replicate your issue but it seems to be isolated to passkeys.io. The passkey is successfully created in Bitwarden, and we provide the expected response to the calling application.

I suspect this is a bug in the webpage itself as I am able to create and use passkeys with other websites. For example, https://learnpasskeys.io, https://webauthn.io, https://passkeys-demo.appspot.com, and many other production sites.

I suggest reaching out to the author of that site and reporting the issue if you have not already done so.

If there are other sites or applications you are seeing issues with, feel free to provide details and we can try to identify if there's a common cause between them.

@SaintPatrck commented on GitHub (Feb 3, 2025): Hi @nordic-style I was able to replicate your issue but it seems to be isolated to `passkeys.io`. The passkey is successfully created in Bitwarden, and we provide the expected response to the calling application. I suspect this is a bug in the webpage itself as I am able to create and use passkeys with other websites. For example, https://learnpasskeys.io, https://webauthn.io, https://passkeys-demo.appspot.com, and many other _production_ sites. I suggest reaching out to the author of that site and reporting the issue if you have not already done so. If there are other sites or applications you are seeing issues with, feel free to provide details and we can try to identify if there's a common cause between them.
Author
Owner

@nordic-style commented on GitHub (Feb 3, 2025):

Hi @SaintPatrck, thanks for the quick reply. It was late yesterday and I forgot some information in my ticket.

I originally found the problem on https://www.amazon.de/ where I can still reproduce the problem. After that I went to passkeys.io so you don't have to create a German Amazon account. With the firfox plugin both sites work fine. The Google password manager on Android also works without any problems. Could it be that there is a function that we are missing on both sites?

Best
Martin

@nordic-style commented on GitHub (Feb 3, 2025): Hi @SaintPatrck, thanks for the quick reply. It was late yesterday and I forgot some information in my ticket. I originally found the problem on https://www.amazon.de/ where I can still reproduce the problem. After that I went to passkeys.io so you don't have to create a German Amazon account. With the firfox plugin both sites work fine. The Google password manager on Android also works without any problems. Could it be that there is a function that we are missing on both sites? Best Martin
Author
Owner

@SaintPatrck commented on GitHub (Feb 3, 2025):

Thank you for the additional details. I'll do some testing with Amazon to see if anything stands out.

In the meantime, I've reached out to Hanko (owners of passkeys.io) and they are investigating on their end. I'll post updates as they're available.

@SaintPatrck commented on GitHub (Feb 3, 2025): Thank you for the additional details. I'll do some testing with Amazon to see if anything stands out. In the meantime, I've reached out to Hanko (owners of passkeys.io) and they are investigating on their end. I'll post updates as they're available.
Author
Owner

@FlxMgdnz commented on GitHub (Feb 4, 2025):

Thank you for reporting the problem @nordic-style and for the tip @SaintPatrck. We are investigating the issue and will get back to you as soon as we know what's going on.

@FlxMgdnz commented on GitHub (Feb 4, 2025): Thank you for reporting the problem @nordic-style and for the tip @SaintPatrck. We are investigating the issue and will get back to you as soon as we know what's going on.
Author
Owner

@FreddyDevelop commented on GitHub (Feb 5, 2025):

Hey @SaintPatrck,

I just looked into the problem and I can also reproduce it but I'm not sure why it occurs.

When creating a passkey with Bitwarden the browser always returns this error:
NotReadableError: An unknown error occurred while talking to the credential manager.

I used this statement to test:

navigator.credentials.create({publicKey: {challenge: Uint8Array.from("12345678901234567890".split('').map(letter => letter.charCodeAt(0))), user:{id: Uint8Array.from("12345678901234567890".split('').map(letter => letter.charCodeAt(0))), name: "testname", displayName: "testName"}, pubKeyCredParams:[{type:"public-key", alg: -7},{type:"public-key", alg: -257}], rp:{name:"passkeys.io", id:"passkeys.io"}, authenticatorSelection: {residentKey: "required", requireResidentKey: true, userVerification: "required"}, attestation: "direct"}})

I also changed some options (e.g. attestation, authenticatorSelection) but still got the same error.

@FreddyDevelop commented on GitHub (Feb 5, 2025): Hey @SaintPatrck, I just looked into the problem and I can also reproduce it but I'm not sure why it occurs. When creating a passkey with Bitwarden the browser always returns this error: `NotReadableError: An unknown error occurred while talking to the credential manager.` I used this statement to test: ```javascript navigator.credentials.create({publicKey: {challenge: Uint8Array.from("12345678901234567890".split('').map(letter => letter.charCodeAt(0))), user:{id: Uint8Array.from("12345678901234567890".split('').map(letter => letter.charCodeAt(0))), name: "testname", displayName: "testName"}, pubKeyCredParams:[{type:"public-key", alg: -7},{type:"public-key", alg: -257}], rp:{name:"passkeys.io", id:"passkeys.io"}, authenticatorSelection: {residentKey: "required", requireResidentKey: true, userVerification: "required"}, attestation: "direct"}}) ``` I also changed some options (e.g. `attestation`, `authenticatorSelection`) but still got the same error.
Author
Owner

@MasterKeyxda commented on GitHub (Mar 3, 2025):

I have the same issue when creating passkeys on Android 15 (Pixel 6) with accounts on Amazon and Google. Cannot link the passkey to accounts. Bitwarden creates the passkey successfully but the accounts error out and cannot use the passkey.

@MasterKeyxda commented on GitHub (Mar 3, 2025): I have the same issue when creating passkeys on Android 15 (Pixel 6) with accounts on Amazon and Google. Cannot link the passkey to accounts. Bitwarden creates the passkey successfully but the accounts error out and cannot use the passkey.
Author
Owner

@oystersuki commented on GitHub (Mar 4, 2025):

I am also experiencing the same issue. On Bitwarden for Android devices, a Passkey is created on the Bitwarden side, but an error occurs. The Passkey is not registered on the website, and I cannot log in.

  • device:
    • Xiaomi 13t pro
  • OS:
    • HyperOS 2.0.2.0 (Android 15 AP3A.240617.008)
@oystersuki commented on GitHub (Mar 4, 2025): I am also experiencing the same issue. On Bitwarden for Android devices, a Passkey is created on the Bitwarden side, but an error occurs. The Passkey is not registered on the website, and I cannot log in. - device: - Xiaomi 13t pro - OS: - HyperOS 2.0.2.0 (Android 15 AP3A.240617.008)
Author
Owner

@ghost commented on GitHub (Apr 4, 2025):

Same problem here
Pixel 9
Android 15

@ghost commented on GitHub (Apr 4, 2025): Same problem here Pixel 9 Android 15
Author
Owner

@serfriz commented on GitHub (Apr 24, 2025):

Same problem, Pixel 8 Pro, last OS update. I tried with Chrome and I get the same error. Firefox doesn't even give the option to add the passkey to Bitwarden.

@serfriz commented on GitHub (Apr 24, 2025): Same problem, Pixel 8 Pro, last OS update. I tried with Chrome and I get the same error. Firefox doesn't even give the option to add the passkey to Bitwarden.
Author
Owner

@mattjago commented on GitHub (Apr 28, 2025):

Also the same issue for me on numerous sites. I am able to create passkeys using the browser extension and then use them to login on Android, but I can't create them with the android app.

Pixel 9 pro fold
Android 15

@mattjago commented on GitHub (Apr 28, 2025): Also the same issue for me on numerous sites. I am able to create passkeys using the browser extension and then use them to login on Android, but I can't create them with the android app. Pixel 9 pro fold Android 15
Author
Owner

@timmish commented on GitHub (May 14, 2025):

Same here!

@timmish commented on GitHub (May 14, 2025): Same here!
Author
Owner

@wirmi commented on GitHub (May 25, 2025):

Same problem here. Xiaomi 15 (Android 15 and HyperOS 2.0)

@wirmi commented on GitHub (May 25, 2025): Same problem here. Xiaomi 15 (Android 15 and HyperOS 2.0)
Author
Owner

@TerranceSigl commented on GitHub (Jun 24, 2025):

Bitwarden Android Build Version:
Version: 2025.5.0 (20269)

What server are you connecting to?:
US

Self-host Server Version:
No Response

Environment Details:
Google Pixel 9a (Android 16)


I am also having issues creating Passkeys on my Pixel 9a. The device is updated to the latest update which is in June. It is on Android 16.

I have tried Microsoft, Amazon, Google, PlayStation, etc.

Bitwarden creates and stores the passkey. But then the website receives some sort of error. The created passkey in Bitwarden then is unusable as the site does not acknowledge that the passkey was created.

I have used 1Password on these same sites and 1Password is able to successfully create the passkey for the site. I don't know why Bitwarden can't?

Some steps I have done to try to fix the issue with no success:

I set on the "Autofill using another service" under the "Autofill services" setting in Chrome.

Then in my Pixel 9a settings in the password menu I set Bitwarden as my preferred service. But I still receive these errors with Passkeys.

Is there any timeline on a fix as this has been happening for months. I have uninstalled the app and reinstalled it. But nothing seems to work.

@TerranceSigl commented on GitHub (Jun 24, 2025): **Bitwarden Android Build Version:** Version: 2025.5.0 (20269) **What server are you connecting to?:** US **Self-host Server Version:** No Response **Environment Details:** Google Pixel 9a (Android 16) _______________________________________________ I am also having issues creating Passkeys on my Pixel 9a. The device is updated to the latest update which is in June. It is on Android 16. I have tried Microsoft, Amazon, Google, PlayStation, etc. Bitwarden creates and stores the passkey. But then the website receives some sort of error. The created passkey in Bitwarden then is unusable as the site does not acknowledge that the passkey was created. I have used 1Password on these same sites and 1Password is able to successfully create the passkey for the site. I don't know why Bitwarden can't? **Some steps I have done to try to fix the issue with no success:** I set on the "Autofill using another service" under the "Autofill services" setting in Chrome. Then in my Pixel 9a settings in the password menu I set Bitwarden as my preferred service. But I still receive these errors with Passkeys. Is there any timeline on a fix as this has been happening for months. I have uninstalled the app and reinstalled it. But nothing seems to work.
Author
Owner

@ballerbude commented on GitHub (Aug 3, 2025):

Same issue here. Pixel 8 Pro, latest stable update. When using passkeys.io, I get:

You are redirected to the website which says "The request either timed out, was canceled ot the device is already registered. Please try again or try using another device.

Same goes for other sites. The passkey is created inside Bitwarden, but it's not recognized by the sites afterwards.

That's very unfortunate. I would love to use something like pocket-id as my OIDC provider, but Bitwarden refuses to work properly.

@ballerbude commented on GitHub (Aug 3, 2025): Same issue here. Pixel 8 Pro, latest stable update. When using passkeys.io, I get: > You are redirected to the website which says "The request either timed out, was canceled ot the device is already registered. Please try again or try using another device. Same goes for other sites. The passkey is created inside Bitwarden, but it's not recognized by the sites afterwards. That's very unfortunate. I would love to use something like pocket-id as my OIDC provider, but Bitwarden refuses to work properly.
Author
Owner

@john-crane-69 commented on GitHub (Aug 4, 2025):

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.

Hope this helps.

@john-crane-69 commented on GitHub (Aug 4, 2025): 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. Hope this helps.
Author
Owner

@joel-bourquard commented on GitHub (Aug 13, 2025):

Problem persists with the recent 2025.7.2 upgrade of the BitWarden app (Pixel 8 Pro, Android 16). Tested with Amazon website.

@joel-bourquard commented on GitHub (Aug 13, 2025): Problem persists with the recent 2025.7.2 upgrade of the BitWarden app (Pixel 8 Pro, Android 16). Tested with Amazon website.
Author
Owner

@samwathegreat commented on GitHub (Aug 26, 2025):

I’m having this same issue.

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.

It’s frustrating. Any input is welcome.

Thanks

@samwathegreat commented on GitHub (Aug 26, 2025): I’m having this same issue. 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. It’s frustrating. Any input is welcome. Thanks
Author
Owner

@joel-bourquard commented on GitHub (Aug 26, 2025):

I’m having this same issue.

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.

It’s frustrating. Any input is welcome.

Thanks

Hi @samwathegreat ,
Yes, this is frustrating indeed. In the meantime try browsing with "Firefox Nightly" from Play Store: the passphrase saving should work.

@joel-bourquard commented on GitHub (Aug 26, 2025): > I’m having this same issue. > > 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. > > It’s frustrating. Any input is welcome. > > Thanks Hi @samwathegreat , Yes, this is frustrating indeed. In the meantime try browsing with "Firefox Nightly" from Play Store: the passphrase saving should work.
Author
Owner

@ivansenx commented on GitHub (Aug 28, 2025):

Another user here with the same problem: the passkey is generated on the Bitwarden side, but the other one only prompts an error saying that the passkey creation has failed.

Other password managers works flawlessly with passkeys on Android, and given the comments here, the issue seems to be on the Bitwarden Android app.

Google Pixel 8a - Android 16

@ivansenx commented on GitHub (Aug 28, 2025): Another user here with the same problem: the passkey is generated on the Bitwarden side, but the other one only prompts an error saying that the passkey creation has failed. Other password managers works flawlessly with passkeys on Android, and given the comments here, the issue seems to be on the Bitwarden Android app. Google Pixel 8a - Android 16
Author
Owner

@JeffBail commented on GitHub (Sep 5, 2025):

I'm having the same issue on my S21U, fully updated chrome and android 15 with OneUI 7. Many web sites return an error which simply says "no passkey created" even though bitwarden is storing them.

@JeffBail commented on GitHub (Sep 5, 2025): I'm having the same issue on my S21U, fully updated chrome and android 15 with OneUI 7. Many web sites return an error which simply says "no passkey created" even though bitwarden is storing them.
Author
Owner

@aj-rosado commented on GitHub (Oct 6, 2025):

We have just made a change on https://github.com/bitwarden/android/pull/5964 that we expect to fix this issue. 🎉

Thank you for your patience and feedback!

@aj-rosado commented on GitHub (Oct 6, 2025): We have just made a change on https://github.com/bitwarden/android/pull/5964 that we expect to fix this issue. 🎉 Thank you for your patience and feedback!
Author
Owner

@armujahid commented on GitHub (Nov 16, 2025):

Facing similar issue on android while trying to create passkeys on X app.

  1. bitwarden creates and saves the pass key
  2. buy X apps did not detect that the passkey has been saved and we get this toast notification "Request canceled by X". Not sure if this is X issue or bidwarden's.
@armujahid commented on GitHub (Nov 16, 2025): Facing similar issue on android while trying to create passkeys on X app. 1) bitwarden creates and saves the pass key 2) buy X apps did not detect that the passkey has been saved and we get this toast notification "Request canceled by X". Not sure if this is X issue or bidwarden's.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/android#2161