github-starred/android
2
0
Fork 0
mirror of https://github.com/bitwarden/android.git synced 2026-03-09 03:33:36 -05:00
Code Issues 144 Packages Projects Releases 116 Wiki Activity

Bitwarden not offered as a passkey option when adding a Google Account to an Android device #1982

New Issue
Open
opened 2025-11-26 23:03:45 -06:00 by GiteaMirror · 5 comments
GiteaMirror commented 2025-11-26 23:03:45 -06:00
Owner
Copy Link

Originally created by @nanomad on GitHub (Aug 21, 2024).

Bitwarden Beta

  • I'm using the new native Bitwarden Beta app and I'm aware that legacy .NET app bugs should be reported in bitwarden/mobile

Steps To Reproduce

  1. Set up a passkey for a Google account (e.g. via browser)
  2. In Android, setup bitwarden as the default and only passkey provider
  3. In Android, add the same Google account from the settings panel

Note: this happens on the non beta version as well and it

Expected Result

  1. The system UI will prompt to use a passkey, offering BW as an option

Actual Result

  1. The system UI will prompt to use a passkey, but there's no way of using bitwarden as the passkey provider
  2. Open a browser on the same android device
  3. Go to accounts.google.com
  4. Try to login with the same google account as step 1, notice that now Bitwarden is offered as a passkey manager

Screenshots or Videos

image
image
image

Additional Context

Note that that prompt seems to be handled by Google Play Services

This is quite tricky, as I almost couldn't add my google account on a new phone since it was not accepting Bitwarden as a passkey manager. Fortunately after a few failed attempts google has a fallback on the less secure password authentication

Build Version

2024.8.0

Environment Details

  • Device: multiple, android 13 and 14

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 @nanomad on GitHub (Aug 21, 2024). ### Bitwarden Beta - [X] I'm using the new native Bitwarden Beta app and I'm aware that legacy .NET app bugs should be reported in [bitwarden/mobile](https://github.com/bitwarden/mobile) ### Steps To Reproduce 1. Set up a passkey for a Google account (e.g. via browser) 2. In Android, setup bitwarden as the default and only passkey provider 3. In Android, add the same Google account from the settings panel Note: this happens on the non beta version as well and it ### Expected Result 4. The system UI will prompt to use a passkey, offering BW as an option ### Actual Result 4. The system UI will prompt to use a passkey, but there's no way of using bitwarden as the passkey provider 5. Open a browser on the same android device 6. Go to accounts.google.com 7. Try to login with the same google account as step 1, notice that now Bitwarden is offered as a passkey manager ### Screenshots or Videos ![image](https://github.com/user-attachments/assets/da1f7a09-e17f-4acc-ba78-fa7da02a6daa) ![image](https://github.com/user-attachments/assets/cd12f9ce-01eb-4af0-9b49-a97662228091) ![image](https://github.com/user-attachments/assets/d046f034-ad5e-4be8-a49f-29e27a8ad24e) ### Additional Context _Note that that prompt seems to be handled by Google Play Services_ This is quite tricky, as I almost couldn't add my google account on a new phone since it was not accepting Bitwarden as a passkey manager. Fortunately after a few failed attempts google has a fallback on the less secure password authentication ### Build Version 2024.8.0 ### Environment Details - Device: multiple, android 13 and 14 ### 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 app:password-managerbug labels 2025-11-26 23:03:45 -06:00
GiteaMirror commented 2025-11-26 23:03:45 -06:00
Author
Owner
Copy Link

@bitwarden-bot commented on GitHub (Aug 21, 2024):

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

@bitwarden-bot commented on GitHub (Aug 21, 2024): Thank you for your report! We've added this to our internal board for review. ID: PM-11251
GiteaMirror commented 2025-11-26 23:03:45 -06:00
Author
Owner
Copy Link

@cbbit commented on GitHub (Aug 22, 2024):

Hi,

Thank you again for your report! It has been escalated for further investigation. If you have more information that can help us, please add it below.

Thanks!

@cbbit commented on GitHub (Aug 22, 2024): Hi, Thank you again for your report! 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:03:45 -06:00
Author
Owner
Copy Link

@closebot-bw commented on GitHub (Aug 12, 2025):

⚠️ Stale Issue Notice

This issue has been automatically marked as stale due to inactivity. It will be closed in 2 weeks (August 26, 2025) if no further activity occurs.

If this issue is still relevant and you would like to keep it open, please:

  • Comment on this issue to show continued interest
  • Provide any additional information or updates
  • Confirm that the issue still exists in the latest version

Thank you for your contribution to this project! 🙏

@closebot-bw commented on GitHub (Aug 12, 2025): ⚠️ **Stale Issue Notice** This issue has been automatically marked as stale due to inactivity. It will be closed in **2 weeks** (August 26, 2025) if no further activity occurs. If this issue is still relevant and you would like to keep it open, please: - Comment on this issue to show continued interest - Provide any additional information or updates - Confirm that the issue still exists in the latest version Thank you for your contribution to this project! 🙏
GiteaMirror commented 2025-11-26 23:03:46 -06:00
Author
Owner
Copy Link

@divinebovine commented on GitHub (Aug 18, 2025):

Commenting to keep the story alive as this is still a problem on android.

@divinebovine commented on GitHub (Aug 18, 2025): Commenting to keep the story alive as this is still a problem on android.
GiteaMirror commented 2025-11-26 23:03:46 -06:00
Author
Owner
Copy Link

@SaintPatrck commented on GitHub (Aug 18, 2025):

Hi all

Bitwarden is not invoked to fulfill passkey requests during this process. It may be intentional by design that Google only allows passkeys from their own provider. We have opened a ticket with Google inquiring why 3rd party providers are not being invoked and are awaiting a response.

You can view and +1 the issue here: https://issuetracker.google.com/issues/431032359

@SaintPatrck commented on GitHub (Aug 18, 2025): Hi all Bitwarden is not invoked to fulfill passkey requests during this process. It may be intentional by design that Google only allows passkeys from their own provider. We have opened a ticket with Google inquiring why 3rd party providers are not being invoked and are awaiting a response. You can view and +1 the issue here: https://issuetracker.google.com/issues/431032359
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
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#1982
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?