github-starred/android
2
0
Fork 0
mirror of https://github.com/bitwarden/android.git synced 2026-03-22 12:32:53 -05:00
Code Issues 144 Packages Projects Releases 118 Wiki Activity

Bitwarden not popping up for passkey creation/sign-in #2277

New Issue
Open
opened 2025-11-26 23:14:17 -06:00 by GiteaMirror · 16 comments
GiteaMirror commented 2025-11-26 23:14:17 -06:00
Owner
Copy Link

Originally created by @ebejko on GitHub (Jul 9, 2025).

Origin

Native Application (non-browser app)

Web URL or App name

webauthn.io

Passkey Action

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

Build Information

© Bitwarden Inc. 2015-2025

Version: 2025.6.1 (20398)
📱 google Pixel 8 🤖 16@36 📦 prod
🧱 commit: bitwarden/android/release/hotfix-v2025.6.0-bwpm@e8878d321546a846909c70c00cdf8d7071f0ecf0
💻 build source: bitwarden/android/actions/runs/15984517798/attempts/1

Additional Information

Although Bitwarden is set as preferred service in "Passwords, passkeys and accounts" and the additional services are disabled, when trying to signup or login in webauthn.io or any other website that supports passkeys, the default Google manager popup is shown. This is happening on both Firefox 140.0.3 and Edge 138.0.3351.66. All the other functionalities, like password autofill, work as expected.

Setting the preferred service to None and then back to Bitwarden fixes the passkey issue temporarily, but the same issue reappears after some (undetermined) time.

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 @ebejko on GitHub (Jul 9, 2025). ### Origin Native Application (non-browser app) ### Web URL or App name webauthn.io ### Passkey Action - [x] Creating new passkey (Registration) - [x] Signing in (Authentication) ### Build Information © Bitwarden Inc. 2015-2025 Version: 2025.6.1 (20398) 📱 google Pixel 8 🤖 16@36 📦 prod 🧱 commit: bitwarden/android/release/hotfix-v2025.6.0-bwpm@e8878d321546a846909c70c00cdf8d7071f0ecf0 💻 build source: bitwarden/android/actions/runs/15984517798/attempts/1 ### Additional Information Although Bitwarden is set as preferred service in "Passwords, passkeys and accounts" and the additional services are disabled, when trying to signup or login in webauthn.io or any other website that supports passkeys, the default Google manager popup is shown. This is happening on both Firefox 140.0.3 and Edge 138.0.3351.66. All the other functionalities, like password autofill, work as expected. Setting the preferred service to None and then back to Bitwarden fixes the passkey issue temporarily, but the same issue reappears after some (undetermined) time. ### 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 2025-11-26 23:14:17 -06:00
GiteaMirror commented 2025-11-26 23:14:18 -06:00
Author
Owner
Copy Link

@bitwarden-bot commented on GitHub (Jul 9, 2025):

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

@bitwarden-bot commented on GitHub (Jul 9, 2025): Thank you for your report! We've added this to our internal board for review. ID: PM-23567
GiteaMirror commented 2025-11-26 23:14:18 -06:00
Author
Owner
Copy Link

@daniellbw commented on GitHub (Jul 10, 2025):

Hi there,

I am unable to reproduce this issue, it has been escalated for further investigation. If you have more information that can help us, please add it below.

Thanks!

@daniellbw commented on GitHub (Jul 10, 2025): Hi there, I am unable to reproduce this issue, it has been escalated for further investigation. If you have more information that can help us, please add it below. Thanks!
GiteaMirror commented 2025-11-26 23:14:18 -06:00
Author
Owner
Copy Link

@codecrafting-io commented on GitHub (Jul 19, 2025):

Also have this issue. Bitwarden is not prompting for passkeys, just don't work. Using Android 13. Tried to reinstall, reconfigure, chrome based browsers flags and nothing.

@codecrafting-io commented on GitHub (Jul 19, 2025): Also have this issue. Bitwarden is not prompting for passkeys, just don't work. Using Android 13. Tried to reinstall, reconfigure, chrome based browsers flags and nothing.
GiteaMirror commented 2025-11-26 23:14:18 -06:00
Author
Owner
Copy Link

@pamperer562580892423 commented on GitHub (Jul 20, 2025):

Also have this issue. Bitwarden is not prompting for passkeys, just don't work. Using Android 13. Tried to reinstall, reconfigure, chrome based browsers flags and nothing.

@codecrafting-io Only Android 14 and above can be used for third-party passkey management, so unfortunately it can't work for you on Android 13.

(--> the very first step described here: https://bitwarden.com/help/auto-fill-android/#using-passkeys can't be done on your phone, as you don't have "passkeys" mentioned in your Android settings... don't ask me though, why the Help Site doesn't mention Android 14 as a requirement... the Help Sites were changed recently - I think it was mentioned before that)

PS: Here you can read of the Android 14 requirement on "the" (developer) website about passkeys: https://passkeys.dev/docs/reference/android/ (right at the the top, "overview" section, second point which speaks of "third-party passkey provider")

@pamperer562580892423 commented on GitHub (Jul 20, 2025): > Also have this issue. Bitwarden is not prompting for passkeys, just don't work. Using Android 13. Tried to reinstall, reconfigure, chrome based browsers flags and nothing. @codecrafting-io Only Android 14 and above can be used for third-party passkey management, so unfortunately it can't work for you on Android 13. (--> the very first step described here: https://bitwarden.com/help/auto-fill-android/#using-passkeys can't be done on your phone, as you don't have "passkeys" mentioned in your Android settings... don't ask me though, why the Help Site doesn't mention Android 14 as a requirement... the Help Sites were changed recently - I think it was mentioned before that) PS: Here you can read of the Android 14 requirement on "the" (developer) website about passkeys: https://passkeys.dev/docs/reference/android/ (right at the the top, "overview" section, second point which speaks of "third-party passkey provider")
GiteaMirror commented 2025-11-26 23:14:18 -06:00
Author
Owner
Copy Link

@pamperer562580892423 commented on GitHub (Jul 20, 2025):

@SaintPatrck I really do think the Help Sites should mention the Android 14 requirement for BW passkey usage again - many people still have "older devices"... and the mobile app can be used with Android 10 and above currently...

@pamperer562580892423 commented on GitHub (Jul 20, 2025): @SaintPatrck I really do think the Help Sites should mention the Android 14 requirement for BW passkey usage again - many people still have "older devices"... and the mobile app can be used with Android 10 and above currently...
GiteaMirror commented 2025-11-26 23:14:18 -06:00
Author
Owner
Copy Link

@StevenJonSmith commented on GitHub (Jul 24, 2025):

Could this be linked to this issue: https://github.com/bitwarden/android/issues/5425

@StevenJonSmith commented on GitHub (Jul 24, 2025): Could this be linked to this issue: https://github.com/bitwarden/android/issues/5425
GiteaMirror commented 2025-11-26 23:14:19 -06:00
Author
Owner
Copy Link

@maz-saify commented on GitHub (Aug 14, 2025):

I am facing the same issue and can confirm it is still reproducible in latest Bitwarden version in Android 15 with Firefox Nightly. See Screenshot.

Image

instead of

Image

@maz-saify commented on GitHub (Aug 14, 2025): I am facing the same issue and can confirm it is still reproducible in latest Bitwarden version in Android 15 with Firefox Nightly. See Screenshot. ![Image](https://github.com/user-attachments/assets/9087165e-7706-4cff-aa51-6d9bba1c078a) instead of ![Image](https://github.com/user-attachments/assets/2f64cb69-3693-46b7-ba13-053f2bc37e44)
GiteaMirror commented 2025-11-26 23:14:19 -06:00
Author
Owner
Copy Link

@ebejko commented on GitHub (Aug 14, 2025):

I can also confirm that the problem reappeared today for the first time since opening the issue.

@ebejko commented on GitHub (Aug 14, 2025): I can also confirm that the problem reappeared today for the first time since opening the issue.
GiteaMirror commented 2025-11-26 23:14:19 -06:00
Author
Owner
Copy Link

@JSpurrier7 commented on GitHub (Aug 24, 2025):

I am facing the same issue and can confirm it is still reproducible in latest Bitwarden version in Android 15 with Firefox Nightly. See Screenshot.

Image

instead of

Image

Any fix for this yet?

Running into this exact same issue on my OnePlus 13 on Android 15. Extremely irritating when evaluating switching from Proton Pass, as this was working for that product.

Bitwarden version:
Version: 2025.8.0 (20577)
📱 OnePlus CPH2655 🤖 15@35 📦 prod
🧱 commit: bitwarden/android/release/2025.8-rc32@1c525b9dfc588105e1fd8f3ad2d4196803c19cd7
💻 build source: bitwarden/android/actions/runs/16834718954/attempts/1
🦀 SDK: 1.0.0-2450-9fe3aeda

@JSpurrier7 commented on GitHub (Aug 24, 2025): - [ ] > I am facing the same issue and can confirm it is still reproducible in latest Bitwarden version in Android 15 with Firefox Nightly. See Screenshot. > > ![Image](https://github.com/user-attachments/assets/9087165e-7706-4cff-aa51-6d9bba1c078a) > > instead of > > ![Image](https://github.com/user-attachments/assets/2f64cb69-3693-46b7-ba13-053f2bc37e44) Any fix for this yet? Running into this exact same issue on my OnePlus 13 on Android 15. Extremely irritating when evaluating switching from Proton Pass, as this was working for that product. Bitwarden version: Version: 2025.8.0 (20577) 📱 OnePlus CPH2655 🤖 15@35 📦 prod 🧱 commit: bitwarden/android/release/2025.8-rc32@1c525b9dfc588105e1fd8f3ad2d4196803c19cd7 💻 build source: bitwarden/android/actions/runs/16834718954/attempts/1 🦀 SDK: 1.0.0-2450-9fe3aeda
GiteaMirror commented 2025-11-26 23:14:19 -06:00
Author
Owner
Copy Link

@kizzywuzzit commented on GitHub (Sep 14, 2025):

I was also seeing this issue after upgrading to a new phone. I went into the preferred service setting and switched from bitwarden to another service, then back to bitwarden and it seems to be working. Not sure if others seeing this also did their initial service selection as bitwarden, or it carried over from phone transfer.

@kizzywuzzit commented on GitHub (Sep 14, 2025): I was also seeing this issue after upgrading to a new phone. I went into the preferred service setting and switched from bitwarden to another service, then back to bitwarden and it seems to be working. Not sure if others seeing this also did their initial service selection as bitwarden, or it carried over from phone transfer.
GiteaMirror commented 2025-11-26 23:14:20 -06:00
Author
Owner
Copy Link

@yujincheng08 commented on GitHub (Sep 15, 2025):

same issue here on Android 15

@yujincheng08 commented on GitHub (Sep 15, 2025): same issue here on Android 15
GiteaMirror commented 2025-11-26 23:14:20 -06:00
Author
Owner
Copy Link

@lukahn commented on GitHub (Sep 20, 2025):

Same on Android 16, using Bitwarden 2025.9.0 and Firefox Beta 144.04b. I'll note that this has never worked successfully for me, and I was hoping that it'd be fixed after https://github.com/bitwarden/mobile/issues/3193 / https://bugzilla.mozilla.org/show_bug.cgi?id=1870436 (both of which are closed).

Edit: Never mind. It appears to be working after selecting Bitwarden again in the "Passwords, passkeys and accounts" section. Before I just got the Google Passkey option, but now it has a button for choosing another option, and Bitwarden appears there.

@lukahn commented on GitHub (Sep 20, 2025): Same on Android 16, using Bitwarden 2025.9.0 and Firefox Beta 144.04b. I'll note that this has never worked successfully for me, and I was hoping that it'd be fixed after https://github.com/bitwarden/mobile/issues/3193 / https://bugzilla.mozilla.org/show_bug.cgi?id=1870436 (both of which are closed). Edit: Never mind. It appears to be working after selecting Bitwarden again in the "Passwords, passkeys and accounts" section. Before I just got the Google Passkey option, but now it has a button for choosing another option, and Bitwarden appears there.
GiteaMirror commented 2025-11-26 23:14:20 -06:00
Author
Owner
Copy Link

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

This is likely an android issue, not a Bitwarden issue.

I just experienced the same thing after getting a new phone. Bitwarden was selected as my passkey manager, and Google's was disabled. Regardless, Google's was the one showing up.

I followed @kizzywuzzit's advice, went back to the settings, selected Google instead, then clicked "Open" just out of curiosity, where it had me click through a pop-up about Google auto fill, then I switched it back to Bitwarden and it worked.

@kooshi commented on GitHub (Oct 10, 2025): This is likely an android issue, not a Bitwarden issue. I just experienced the same thing after getting a new phone. Bitwarden was selected as my passkey manager, and Google's was disabled. Regardless, Google's was the one showing up. I followed @kizzywuzzit's advice, went back to the settings, selected Google instead, then clicked "Open" just out of curiosity, where it had me click through a pop-up about Google auto fill, then I switched it back to Bitwarden and it worked.
GiteaMirror commented 2025-11-26 23:14:20 -06:00
Author
Owner
Copy Link

@Mattwmaster58 commented on GitHub (Oct 20, 2025):

This is quite frustrating, I have to agree it seems like an Android issue. Based on this logcat it seems to always be launching the google modal.

 Intent { act=com.google.android.gms.fido.fido2.regular.START pkg=com.google.android.gms }

file2.txt

I tried setting the provider to None and MSFT Authenticator, and none of these prevent the Google one from showing in the Kraken app. I also tried adb shell pm disable-user com.google.android.gms but this causes the continue button to simply hang in the Kraken app.

@Mattwmaster58 commented on GitHub (Oct 20, 2025): This is quite frustrating, I have to agree it seems like an Android issue. Based on this logcat it seems to always be launching the google modal. ``` Intent { act=com.google.android.gms.fido.fido2.regular.START pkg=com.google.android.gms } ``` [file2.txt](https://github.com/user-attachments/files/23004722/file2.txt) I tried setting the provider to None and MSFT Authenticator, and none of these prevent the Google one from showing in the Kraken app. I also tried `adb shell pm disable-user com.google.android.gms` but this causes the continue button to simply hang in the Kraken app.
GiteaMirror commented 2025-11-26 23:14:21 -06:00
Author
Owner
Copy Link

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

With Android app version 2025.10.0 I now can successfully create passkeys again - and also on webauthn.io and passkeys.io. (!)

Though

  • it doesn't work with Vivaldi at the moment (I don't get offered Bitwarden as passkey provider), but with Brave (--> maybe it would also work with Chrome, and I think due to the new browser integrations - but I didn't test other browsers)

  • and with passkeys.io I do shortly see an error message, but creation and login do work nonetheless (and I even see that error message shortly, when I successfully login with the browser extension 2025.10.0 to passkeys.io, so that might be a general issue...)

PS: 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

@pamperer562580892423 commented on GitHub (Oct 22, 2025): With Android app version 2025.10.0 I now can successfully create passkeys again - and also on webauthn.io and passkeys.io. (!) Though - it doesn't work with Vivaldi at the moment (I don't get offered Bitwarden as passkey provider), but with **Brave** (--> maybe it would also work with Chrome, and I think due to the new browser integrations - but I didn't test other browsers) - and with passkeys.io I do shortly see an error message, but creation and login do work nonetheless (and I even see that error message shortly, when I successfully login with the browser extension 2025.10.0 to passkeys.io, so that might be a general issue...) PS: 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
GiteaMirror commented 2025-11-26 23:14:21 -06:00
Author
Owner
Copy Link

@maave0 commented on GitHub (Oct 28, 2025):

I'm piling on: I also think it's an Android bug. I was getting the default google popup instead of BW. I simply re-set the preferred password manager and it worked. In Android Settings > "Password, passkeys, & accounts" I un-selected and re-selected Bitwarden for passkeys to work.

BitWarden version: 2025.10.0 (20794)
Android version 15, kernel version 5.15.170 (Sony Xperia build)
browser: both Chrome 141.0.7390.122 and Firefox 144.0.1

@maave0 commented on GitHub (Oct 28, 2025): I'm piling on: I also think it's an Android bug. I was getting the default google popup instead of BW. I simply re-set the preferred password manager and it worked. In Android Settings > "Password, passkeys, & accounts" I un-selected and re-selected Bitwarden for passkeys to work. BitWarden version: 2025.10.0 (20794) Android version 15, kernel version 5.15.170 (Sony Xperia build) browser: both Chrome 141.0.7390.122 and Firefox 144.0.1
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#2277
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?