[PM-26002] Bug: Bitwarden Passkey Not Found After Website Refresh (Android 15, Edge/Chrome Browsers)

[Jiejd]

Origin

Native Application (non-browser app)

Web URL or App name

https://webauthn.io

Passkey Action

• Creating new passkey (Registration)
• Signing in (Authentication)

Build Information

I encountered an issue on the Android version of Bitwarden when using passkeys to authenticate on websites, specifically when testing with the webauthn.io demo site. The issue occurs as follows:

1. I opened the webauthn.io site and registered a passkey (username: 12345).
2. Registration was successful, and the passkey was stored in Bitwarden.
3. After confirming the registration, everything seemed to work fine.
4. However, when I clicked on "Try Again" (to reattempt the process) and then returned to the homepage to confirm, I received the error: "Passkey for 12345 not found."
5. If I re-register with the same username (12345), Bitwarden stores the new passkey successfully, and the verification process works.
6. The problem persists when refreshing the webpage or trying to verify the passkey again: it fails to locate the stored passkey for 12345, even though it is saved in Bitwarden.

This issue also affects other websites, including GitHub, where logging in with passkeys results in a message stating that no passkey was found, even though Bitwarden contains the correct passkey.

Steps to Reproduce:

1. Open the webauthn.io site on an Android 15 device using either Edge or Chrome browser.
2. Register a new passkey (e.g., 12345).
3. Confirm successful registration and save the passkey in Bitwarden.
4. Refresh the page or navigate to another page and attempt to verify the passkey again.
5. You will see the error message: "Passkey for 12345 not found."

Expected Behavior:

• Bitwarden should retain and correctly identify the passkey after a page refresh or when attempting to authenticate again, without any error messages stating the passkey is missing.

Actual Behavior:

• Passkeys are stored in Bitwarden, but refreshing the page or trying to authenticate again results in an error that the passkey cannot be found.

Environment:

• Android version: 15
• Bitwarden Android version: 2025.8.1 (20670)
• SDK: 1.0.0-2450-9fe3aeda
• Browsers: Edge , Chrome

Additional Information

• This issue seems specific to the Bitwarden Android app and passkey management, as the same passkeys work fine when using Bitwarden on other platforms (e.g., browser extensions).
• I have attempted to clear cache and restart the app, but the issue persists.
• Version: 2025.7.1 (20513) can discover and use passkey normally when the password vault is unlocked.

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.

[bitwarden-bot]

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

[Jiejd]

Passkey cannot be used, even after installing the latest version 2025.9.0. In version 2025.7.1, unlocking the password vault allows one to find and use Passkey, but in versions 2025.8.0 to 2025.9.0, even after unlocking the password vault, Passkey cannot be found and it directly prompts that there is no key.

[samwathegreat]

Passkey cannot be used, even after installing the latest version 2025.9.0. In version 2025.7.1, unlocking the password vault allows one to find and use Passkey, but in versions 2025.8.0 to 2025.9.0, even after unlocking the password vault, Passkey cannot be found and it directly prompts that there is no key.

@Jiejd Your screenshot indicates that it's looking for the passkey in GOOGLE PASSWORD MANAGER, not bitwarden. It's really clear from your screenshot.

There is another bug report that references a similar issue. Try going into settings, and changing your default password manager to GOOGLE password manager, SAVING IT, then change it back to BITWARDEN, save it, and try again.

[Jiejd]

即使安装了最新版本的2025.9.0,也无法使用Passkey。在2025.71版本中,解锁密码库允许用户查找和使用Passkey,但在版本2025.8.0至2025.9.0中,即使解锁了密码库,Passkey仍无法找到,并直接提示没有密钥。

@Jiejd 你的截图表明它正在寻找谷歌密码管理器中的密码,而不是比特雷丁。从你的截图中可以说得很清楚。

还有一份漏洞报告提到了类似的问题。尝试进入设置,然后将默认密码管理器更改为GOOGLE密码管理器,保存它,然后将其重新更改为BITWARDEN,保存后再重试。

I'm glad you responded to me. The screenshot shows that the key cannot be found and gives a prompt. When testing passkey registration on the webauthn.io website, it can be called and stored in Bitwarden, and then login verification is successful. However, when I click 'Try again,' it shows that the passkey cannot be found like in the screenshot. In version 2025.7.1, if I don't unlock the Bitwarden vault, it will also prompt that the passkey cannot be found. If I unlock it, the passkey can be discovered and used normally. But in version 2025.9.1, even after unlocking, it still prompts that the passkey cannot be found. ...

[samwathegreat]

Have you tried going into settings, and changing your default password manager to GOOGLE password manager, SAVING IT, then change it back to BITWARDEN, save it, and try again?

[Jiejd]

你有没有尝试进入设置,将默认密码管理器更改为GOOGLE密码管理器,保存它,然后将其重新更改为BITWARDEN,保存后再重试?

I tried it, and I did go through these steps to use the passkey, but in the latest version, as I described, Bitwarden can only be used during registration. After registering and refreshing the page, Bitwarden is no longer detected.

[samwathegreat]

OK, I don't think I have any more input then, unfortunately.

See the similar issue reported here (and resolution in last comment): #5499 (comment)

[Jiejd]

This is a screenshot of the process

好吧,很遗憾,我觉得我再也没有什么意见了。

参见此处报道的类似问题(以及上一条评论中的解决方法):第5499条(评论)

[samwathegreat]

Can you show us the process of you going into android settings, changing passkey manager to google, saving, setting it back to bitwarden, saving, and trying again? The report I linked is from people with the same issue with the same version.

[Jiejd]

您能否向我们展示你进入安卓设置、将密码管理器更改为谷歌、保存、重新设置为比特瓦卡、保存并再次尝试的过程?我所链接的报告来自同一版本有相同问题的人。

ok

[samwathegreat]

Great - That seems to be exactly what the users in the other thread did. And does the same issue still persist now?

[Jiejd]

很好——这似乎正是其他帖子中用户所做的。同样的问题现在仍然存在吗?

After this operation process, Bitwarden passkey can be used. Without this, the passkey cannot be used. My issue is that in the latest few versions, registration works but the passkey cannot be detected or used. In version 2025.7.1, after unlocking the vault, the passkey can be detected and used. Could the issue be due to some mechanism of the passkey being updated after version 2025.7.1?