github-starred/android
2
0
Fork 0
mirror of https://github.com/bitwarden/android.git synced 2026-05-06 07:48:22 -05:00
Code Issues 1.1k Packages Projects Releases 122 Wiki Activity

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

New Issue
Closed
opened 2026-04-16 22:10:46 -05:00 by GiteaMirror · 21 comments
GiteaMirror commented 2026-04-16 22:10:46 -05:00
Owner
Copy Link

Originally created by @Jiejd on GitHub (Sep 19, 2025).
Original GitHub issue: https://github.com/bitwarden/android/issues/5911

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

Image

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.
Originally created by @Jiejd on GitHub (Sep 19, 2025). Original GitHub issue: https://github.com/bitwarden/android/issues/5911 ### Origin Native Application (non-browser app) ### Web URL or App name https://webauthn.io ### Passkey Action - [x] Creating new passkey (Registration) - [x] 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](https://webauthn.io/) demo site. The issue occurs as follows: 1. I opened the [webauthn.io](https://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](https://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 ![Image](https://github.com/user-attachments/assets/5fbcd0c0-69e6-4aa4-ac2f-4cdc75f73904) ### 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 - [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-manager labels 2026-04-16 22:10:46 -05:00
GiteaMirror commented 2026-04-16 22:10:47 -05:00
Author
Owner
Copy Link

@bitwarden-bot commented on GitHub (Sep 19, 2025):

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

<!-- gh-comment-id:3311623918 --> @bitwarden-bot commented on GitHub (Sep 19, 2025): Thank you for your report! We've added this to our internal board for review. ID: PM-26002
GiteaMirror commented 2026-04-16 22:10:47 -05:00
Author
Owner
Copy Link

@Jiejd commented on GitHub (Oct 2, 2025):

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.

<!-- gh-comment-id:3359918374 --> @Jiejd commented on GitHub (Oct 2, 2025): 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.
GiteaMirror commented 2026-04-16 22:10:47 -05:00
Author
Owner
Copy Link

@samwathegreat commented on GitHub (Oct 10, 2025):

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.

<!-- gh-comment-id:3390667076 --> @samwathegreat commented on GitHub (Oct 10, 2025): > 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.
GiteaMirror commented 2026-04-16 22:10:47 -05:00
Author
Owner
Copy Link

@Jiejd commented on GitHub (Oct 10, 2025):

即使安装了最新版本的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. ...

<!-- gh-comment-id:3390807149 --> @Jiejd commented on GitHub (Oct 10, 2025): > > 即使安装了最新版本的2025.9.0,也无法使用Passkey。在2025.71版本中,解锁密码库允许用户查找和使用Passkey,但在版本2025.8.0至2025.9.0中,即使解锁了密码库,Passkey仍无法找到,并直接提示没有密钥。 > > [@Jiejd](https://github.com/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. ...
GiteaMirror commented 2026-04-16 22:10:48 -05:00
Author
Owner
Copy Link

@samwathegreat commented on GitHub (Oct 10, 2025):

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?

<!-- gh-comment-id:3390816988 --> @samwathegreat commented on GitHub (Oct 10, 2025): 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?
GiteaMirror commented 2026-04-16 22:10:48 -05:00
Author
Owner
Copy Link

@Jiejd commented on GitHub (Oct 10, 2025):

你有没有尝试进入设置,将默认密码管理器更改为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.

<!-- gh-comment-id:3390832131 --> @Jiejd commented on GitHub (Oct 10, 2025): > 你有没有尝试进入设置,将默认密码管理器更改为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.
GiteaMirror commented 2026-04-16 22:10:48 -05:00
Author
Owner
Copy Link

@samwathegreat commented on GitHub (Oct 10, 2025):

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

See the similar issue reported here (and resolution in last comment): https://github.com/bitwarden/android/issues/5499#issuecomment-3389374465

<!-- gh-comment-id:3390882510 --> @samwathegreat commented on GitHub (Oct 10, 2025): OK, I don't think I have any more input then, unfortunately. See the similar issue reported here (and resolution in last comment): https://github.com/bitwarden/android/issues/5499#issuecomment-3389374465
GiteaMirror commented 2026-04-16 22:10:49 -05:00
Author
Owner
Copy Link

@Jiejd commented on GitHub (Oct 10, 2025):

This is a screenshot of the process
Image

Image

Image

Image

Image

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

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

<!-- gh-comment-id:3390901413 --> @Jiejd commented on GitHub (Oct 10, 2025): This is a screenshot of the process ![Image](https://github.com/user-attachments/assets/ae2dafec-6ef2-4be6-90f2-4fd03ff3d15b) ![Image](https://github.com/user-attachments/assets/ea30ecc2-ec3d-4acb-921a-443f775f53f6) ![Image](https://github.com/user-attachments/assets/678f8717-5c61-4bf3-8d0f-eb0246996bdc) ![Image](https://github.com/user-attachments/assets/b5445429-dd48-4e54-bd4b-0019d8ba9418) ![Image](https://github.com/user-attachments/assets/6e7410fb-8241-46db-bb19-b50af9343fd6) > 好吧,很遗憾,我觉得我再也没有什么意见了。 > > 参见此处报道的类似问题(以及上一条评论中的解决方法[):第5499条(评论)](https://github.com/bitwarden/android/issues/5499#issuecomment-3389374465)
GiteaMirror commented 2026-04-16 22:10:49 -05:00
Author
Owner
Copy Link

@samwathegreat commented on GitHub (Oct 10, 2025):

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.

<!-- gh-comment-id:3390921831 --> @samwathegreat commented on GitHub (Oct 10, 2025): 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.
GiteaMirror commented 2026-04-16 22:10:49 -05:00
Author
Owner
Copy Link

@Jiejd commented on GitHub (Oct 10, 2025):

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

ok

Image

Image

Image

Image

Image

Image

<!-- gh-comment-id:3390948904 --> @Jiejd commented on GitHub (Oct 10, 2025): > 您能否向我们展示你进入安卓设置、将密码管理器更改为谷歌、保存、重新设置为比特瓦卡、保存并再次尝试的过程?我所链接的报告来自同一版本有相同问题的人。 ok ![Image](https://github.com/user-attachments/assets/66584480-6af4-46dd-b6f7-5f3c1b89bccf) ![Image](https://github.com/user-attachments/assets/70648fc5-e4e1-4a0e-a655-54630f01caa0) ![Image](https://github.com/user-attachments/assets/d9281bb2-05e3-4b64-9b2e-ff833f59f652) ![Image](https://github.com/user-attachments/assets/a7384d02-e935-40c9-a8db-ea45c08c8da0) ![Image](https://github.com/user-attachments/assets/702e683c-1e10-4ebf-abaf-01a143d1c652) ![Image](https://github.com/user-attachments/assets/0c526583-a5e1-4a5e-9d6d-e4e7280e2d9b)
GiteaMirror commented 2026-04-16 22:10:50 -05:00
Author
Owner
Copy Link

@samwathegreat commented on GitHub (Oct 10, 2025):

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

<!-- gh-comment-id:3390966114 --> @samwathegreat commented on GitHub (Oct 10, 2025): Great - That seems to be exactly what the users in the other thread did. And does the same issue still persist now?
GiteaMirror commented 2026-04-16 22:10:50 -05:00
Author
Owner
Copy Link

@Jiejd commented on GitHub (Oct 10, 2025):

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

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?

<!-- gh-comment-id:3390991070 --> @Jiejd commented on GitHub (Oct 10, 2025): > 很好——这似乎正是其他帖子中用户所做的。同样的问题现在仍然存在吗? 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?
GiteaMirror commented 2026-04-16 22:10:50 -05:00
Author
Owner
Copy Link

@Jiejd commented on GitHub (Oct 10, 2025):

I have tested and found that this problem occurs starting from version 2025.7.2. I wonder if it is related to #4110.

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

<!-- gh-comment-id:3391096038 --> @Jiejd commented on GitHub (Oct 10, 2025): I have tested and found that this problem occurs starting from version 2025.7.2. I wonder if it is related to #4110. > 很好——这似乎正是其他帖子中用户所做的。同样的问题现在仍然存在吗?
GiteaMirror commented 2026-04-16 22:10:51 -05:00
Author
Owner
Copy Link

@Jiejd commented on GitHub (Oct 10, 2025):

https://github.com/user-attachments/assets/5fbcd0c0-69e6-4aa4-ac2f-4cdc75f73904

<!-- gh-comment-id:3391170814 --> @Jiejd commented on GitHub (Oct 10, 2025): https://github.com/user-attachments/assets/5fbcd0c0-69e6-4aa4-ac2f-4cdc75f73904
GiteaMirror commented 2026-04-16 22:10:51 -05:00
Author
Owner
Copy Link

@Jiejd commented on GitHub (Oct 15, 2025):

@samwathegreat
The video has been updated

<!-- gh-comment-id:3405961316 --> @Jiejd commented on GitHub (Oct 15, 2025): @samwathegreat The video has been updated
GiteaMirror commented 2026-04-16 22:10:51 -05:00
Author
Owner
Copy Link

@pamperer562580892423 commented on GitHub (Oct 22, 2025):

@Jiejd Works for me now with Android app version 2025.10.0 - though I only tested it with Brave browser. (and yeah, I can "Try again" / refresh, and it still "signs me in" on webauthn.io, without that error message that can be seen in your video)

(my favourite Browser Vivaldi on the other hand doesn't even show me Bitwarden as the passkey provider on my Android 15 device at the moment... I have the working hypothesis, that Chrome and Brave - due to the browser integrations - might work best at the moment with passkeys ?! -- however, it definitely seems to be very browser dependent at the moment on Android...)

Overall, I also would recommend this guide on the Community Forum, as it collects also some of the current tips and limitations regarding autofill on Android: https://community.bitwarden.com/t/short-guide-tips-autofill-on-android/88941

<!-- gh-comment-id:3434310331 --> @pamperer562580892423 commented on GitHub (Oct 22, 2025): @Jiejd Works for me now with Android app version 2025.10.0 - though I only tested it with Brave browser. (and yeah, I can "Try again" / refresh, and it still "signs me in" on webauthn.io, without that error message that can be seen in your video) (my favourite Browser Vivaldi on the other hand doesn't even show me Bitwarden as the passkey provider on my Android 15 device at the moment... I have the working hypothesis, that Chrome and Brave - due to the browser integrations - might work best at the moment with passkeys ?! -- however, it definitely seems to be very browser dependent at the moment on Android...) Overall, I also would recommend this guide on the Community Forum, as it collects also some of the current tips and limitations regarding autofill on Android: https://community.bitwarden.com/t/short-guide-tips-autofill-on-android/88941
GiteaMirror commented 2026-04-16 22:10:52 -05:00
Author
Owner
Copy Link

@Jiejd commented on GitHub (Oct 23, 2025):

@Jiejd Works for me now with Android app version 2025.10.0 - though I only tested it with Brave browser. (and yeah, I can "Try again" / refresh, and it still "signs me in" on webauthn.io, without that error message that can be seen in your video)

(my favourite Browser Vivaldi on the other hand doesn't even show me Bitwarden as the passkey provider on my Android 15 device at the moment... I have the working hypothesis, that Chrome and Brave - due to the browser integrations - might work best at the moment with passkeys ?! -- however, it definitely seems to be very browser dependent at the moment on Android...)

Overall, I also would recommend this guide on the Community Forum, as it collects also some of the current tips and limitations regarding autofill on Android: https://community.bitwarden.com/t/short-guide-tips-autofill-on-android/88941

I tried Brave, and it was still the same as shown in my video.

<!-- gh-comment-id:3434844764 --> @Jiejd commented on GitHub (Oct 23, 2025): > [@Jiejd](https://github.com/Jiejd) Works for me now with Android app version 2025.10.0 - though I only tested it with Brave browser. (and yeah, I can "Try again" / refresh, and it still "signs me in" on webauthn.io, without that error message that can be seen in your video) > > (my favourite Browser Vivaldi on the other hand doesn't even show me Bitwarden as the passkey provider on my Android 15 device at the moment... I have the working hypothesis, that Chrome and Brave - due to the browser integrations - might work best at the moment with passkeys ?! -- however, it definitely seems to be very browser dependent at the moment on Android...) > > Overall, I also would recommend this guide on the Community Forum, as it collects also some of the current tips and limitations regarding autofill on Android: https://community.bitwarden.com/t/short-guide-tips-autofill-on-android/88941 I tried Brave, and it was still the same as shown in my video.
GiteaMirror commented 2026-04-16 22:10:52 -05:00
Author
Owner
Copy Link

@pamperer562580892423 commented on GitHub (Oct 23, 2025):

@Jiejd Can you make sure you did the following:

  • activate the "browser integration" for Chrome and Brave (--> https://bitwarden.com/help/auto-fill-android/#browser-integrations)
  • enable this flag: #autofill-update-context-for-web-contents on Chrome and Brave (chrome://flags, brave://flags)
  • make sure that all previously recommended feature flags regarding passkeys (mainly recommendations/necessities from 2023/2024) are deactivated (as they are no longer necessary)
  • toggle the settings for making Bitwarden the passkey provider (in your Android settings) and toggle the autofill settings (in the Settings of the BW mobile app)
  • BW mobile app 2025.10.0 installed
<!-- gh-comment-id:3436117494 --> @pamperer562580892423 commented on GitHub (Oct 23, 2025): @Jiejd Can you make sure you did the following: - activate the "browser integration" for Chrome and Brave (--> https://bitwarden.com/help/auto-fill-android/#browser-integrations) - enable this flag: #autofill-update-context-for-web-contents on Chrome and Brave (chrome://flags, brave://flags) - make sure that all previously recommended feature flags regarding passkeys (mainly recommendations/necessities from 2023/2024) are deactivated (as they are no longer necessary) - toggle the settings for making Bitwarden the passkey provider (in your Android settings) and toggle the autofill settings (in the Settings of the BW mobile app) - BW mobile app 2025.10.0 installed
GiteaMirror commented 2026-04-16 22:10:53 -05:00
Author
Owner
Copy Link

@Jiejd commented on GitHub (Oct 23, 2025):

@Jiejd Can you make sure you did the following:

  • activate the "browser integration" for Chrome and Brave (--> https://bitwarden.com/help/auto-fill-android/#browser-integrations)
  • enable this flag: #autofill-update-context-for-web-contents on Chrome and Brave (chrome://flags, brave://flags)
  • make sure that all previously recommended feature flags regarding passkeys (mainly recommendations/necessities from 2023/2024) are deactivated (as they are no longer necessary)
  • toggle the settings for making Bitwarden the passkey provider (in your Android settings) and toggle the autofill settings (in the Settings of the BW mobile app)
  • BW mobile app 2025.10.0 installed

Forget it, I have tried all the methods. I have also tested 1password before, and there is the same problem. I described on it that the version after 2025.7.1 has this problem, and I can use it normally on 2025.7.1.

<!-- gh-comment-id:3436561204 --> @Jiejd commented on GitHub (Oct 23, 2025): > @Jiejd Can you make sure you did the following: > > - activate the "browser integration" for Chrome and Brave (--> https://bitwarden.com/help/auto-fill-android/#browser-integrations) > - enable this flag: #autofill-update-context-for-web-contents on Chrome and Brave (chrome://flags, brave://flags) > - make sure that all previously recommended feature flags regarding passkeys (mainly recommendations/necessities from 2023/2024) are deactivated (as they are no longer necessary) > - toggle the settings for making Bitwarden the passkey provider (in your Android settings) and toggle the autofill settings (in the Settings of the BW mobile app) > - BW mobile app 2025.10.0 installed Forget it, I have tried all the methods. I have also tested 1password before, and there is the same problem. I described on it that the version after 2025.7.1 has this problem, and I can use it normally on 2025.7.1.
GiteaMirror commented 2026-04-16 22:10:53 -05:00
Author
Owner
Copy Link

@pamperer562580892423 commented on GitHub (Oct 23, 2025):

Forget it, I have tried all the methods. I have also tested 1password before, and there is the same problem. I described on it that the version after 2025.7.1 has this problem, and I can use it normally on 2025.7.1.

Then it's your device and this issue should be closed, as it works with 2025.10.0 now.

<!-- gh-comment-id:3436610897 --> @pamperer562580892423 commented on GitHub (Oct 23, 2025): > Forget it, I have tried all the methods. I have also tested 1password before, and there is the same problem. I described on it that the version after 2025.7.1 has this problem, and I can use it normally on 2025.7.1. Then it's your device and this issue should be closed, as it works with 2025.10.0 now.
GiteaMirror commented 2026-04-16 22:10:54 -05:00
Author
Owner
Copy Link

@Gavin-Guiii commented on GitHub (Nov 19, 2025):

I have the same issue, and unfortunately it's because of our devices. Xiaomi has its own implementation of credential manager (autofill and passkey) and it's super buggy. I've reported to them multiple times and I was told that they have no plans to fix it.

I'm getting a different phone because honestly Xiaomi sucks at this point.

<!-- gh-comment-id:3550078251 --> @Gavin-Guiii commented on GitHub (Nov 19, 2025): I have the same issue, and unfortunately it's because of our devices. Xiaomi has its own implementation of credential manager (autofill and passkey) and it's super buggy. I've reported to them multiple times and I was told that they have no plans to fix it. I'm getting a different phone because honestly Xiaomi sucks at this point.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
app:authenticator
app:password-manager
bug
bug-passkey
customer-support
duplicate
enhancement
good first issue
help wanted
needs-reply
needs-response
pull-request
Mirrored from GitHub Pull Request
 question
No Label app:password-manager bug-passkey
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/android#21613
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?