[GH-ISSUE #6440] [PM-31444] Android says "No passkeys available" despite Bitwarden being unlocked + having a passkey #28333

Closed
opened 2026-04-18 12:25:10 -05:00 by GiteaMirror · 30 comments
Owner

Originally created by @colemickens on GitHub (Jan 30, 2026).
Original GitHub issue: https://github.com/bitwarden/android/issues/6440

Origin

Native Application (non-browser app)

Web URL or App name

https://peanut.me

Passkey Action

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

Build Information

2026.1.0 (21141)

Additional Information

This has been happening for weeks. I provisioned a passkey for https://peanut.me.

Most of the time, this works great! I can login, I can sign transactions, etc. But if the network is even a tiny bit spotty, something bad happens.

For this last occurrence, I specifically pre-opened and pre-unlocked Bitwarden, then tried to trigger a transaction in Peanut, that requires a Passkey.

This is what I got:

Image

I struggle to understand how this is not a SEVERE Android bug, or a problem with Bitwarden. Especially since I can trivially sit here and use the passkey for it, as seen in this video:

https://github.com/user-attachments/assets/5b1041f0-d505-40bf-9a22-93a8120d27cd

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 @colemickens on GitHub (Jan 30, 2026). Original GitHub issue: https://github.com/bitwarden/android/issues/6440 ### Origin Native Application (non-browser app) ### Web URL or App name https://peanut.me ### Passkey Action - [ ] Creating new passkey (Registration) - [x] Signing in (Authentication) ### Build Information 2026.1.0 (21141) ### Additional Information This has been happening for weeks. I provisioned a passkey for https://peanut.me. Most of the time, this works great! I can login, I can sign transactions, etc. But if the network is even a tiny bit spotty, something bad happens. For this last occurrence, I specifically pre-opened and pre-unlocked Bitwarden, then tried to trigger a transaction in Peanut, that requires a Passkey. This is what I got: ![Image](https://github.com/user-attachments/assets/4a8dda9c-c741-4fb9-a80c-a296fb18abf9) I struggle to understand how this is not a SEVERE Android bug, or a problem with Bitwarden. Especially since I can trivially sit here and use the passkey for it, as seen in this video: https://github.com/user-attachments/assets/5b1041f0-d505-40bf-9a22-93a8120d27cd ### 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-18 12:25:11 -05:00
Author
Owner

@bitwarden-bot commented on GitHub (Jan 30, 2026):

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

<!-- gh-comment-id:3821284711 --> @bitwarden-bot commented on GitHub (Jan 30, 2026): Thank you for your report! We've added this to our internal board for review. ID: [PM-31444](https://bitwarden.atlassian.net/browse/PM-31444) [PM-31444]: https://bitwarden.atlassian.net/browse/PM-31444?atlOrigin=eyJpIjoiNWRkNTljNzYxNjVmNDY3MDlhMDU5Y2ZhYzA5YTRkZjUiLCJwIjoiZ2l0aHViLWNvbS1KU1cifQ
Author
Owner

@colemickens commented on GitHub (Jan 30, 2026):

To further offer evidence:

Image
<!-- gh-comment-id:3821295453 --> @colemickens commented on GitHub (Jan 30, 2026): To further offer evidence: <img width="1184" height="1716" alt="Image" src="https://github.com/user-attachments/assets/35729445-396b-4f1d-b92b-7efc3cb0e421" />
Author
Owner

@sshadminBW commented on GitHub (Jan 30, 2026):

Hi there,

I attempted to reproduce your issue and was unable to do so. I think your error could have its origin in a misconfiguration as in your screenshot you are being presented with the Google Password Manager to autofill your passkey and not Bitwarden.

I would recommend you confirm that the browser integration has been enabled for Google Chrome and that you have configured Bitwarden to autofill passwords on your device. https://bitwarden.com/help/auto-fill-android/

We use GitHub issues as a place to track bugs and other development related issues. If your issue persists, please write us back using our “Contact support” form located on our Help Center (https://bitwarden.com/help/).
You can include a link to this issue in the message content.

Alternatively, you can also search for an answer in our help documentation or get help from other Bitwarden users on our community forums (https://community.bitwarden.com/c/support/).

The issue here will be closed.

Thanks!

<!-- gh-comment-id:3821318180 --> @sshadminBW commented on GitHub (Jan 30, 2026): Hi there, I attempted to reproduce your issue and was unable to do so. I think your error could have its origin in a misconfiguration as in your screenshot you are being presented with the Google Password Manager to autofill your passkey and not Bitwarden. I would recommend you confirm that the browser integration has been enabled for Google Chrome and that you have configured Bitwarden to autofill passwords on your device. https://bitwarden.com/help/auto-fill-android/ We use GitHub issues as a place to track bugs and other development related issues. If your issue persists, please write us back using our “Contact support” form located on our Help Center (https://bitwarden.com/help/). You can include a link to this issue in the message content. Alternatively, you can also search for an answer in our help documentation or get help from other Bitwarden users on our community forums (https://community.bitwarden.com/c/support/). The issue here will be closed. Thanks!
Author
Owner

@colemickens commented on GitHub (Jan 30, 2026):

You didn't even read what I wrote. I explained it was sporadic. That HOW THE PASSKEY UX WORKS ON ANDROID.

Also you blew right by where I SHOWED A VIDEO OF THE PASSKEY WORKING AND IT SAYS BITWARDEN AS THE PROVIDER.

And the part where I explained it only happens sporadically

Image
<!-- gh-comment-id:3821324906 --> @colemickens commented on GitHub (Jan 30, 2026): You didn't even read what I wrote. I explained it was sporadic. That HOW THE PASSKEY UX WORKS ON ANDROID. Also you blew right by where I SHOWED A VIDEO OF THE PASSKEY WORKING **AND IT SAYS BITWARDEN** AS THE PROVIDER. And the part where I explained it only happens sporadically <img alt="Image" src="https://github.com/user-attachments/assets/6d93e28e-0b38-45b7-9e78-f7aaba76dfa8" />
Author
Owner

@pamperer562580892423 commented on GitHub (Jan 30, 2026):

Another user here.

I watched your video. The passkey you use (around second 13) is not a passkey from your BW vault. That is a passkey, that is stored in Google Password Manager itself. (from my own test: it depends at the least on your device, if it is stored locally on your device as a hardware-bound passkey - or in your Google account as a synced passkey)

<!-- gh-comment-id:3821338895 --> @pamperer562580892423 commented on GitHub (Jan 30, 2026): Another user here. I watched your video. The passkey you use (around second 13) is **not** a passkey from your BW vault. That is a passkey, that is stored in Google Password Manager itself. (from my own test: it depends at the least on your device, if it is stored locally on your device as a hardware-bound passkey - or in your Google account as a synced passkey)
Author
Owner

@colemickens commented on GitHub (Jan 30, 2026):

Then there is a massive Android bug here. I have one singular passkey provision for Peanut.

I do NOT even have the Google Password manager enabled as an app, enabled in the OS, or enabled as a passkey provider.

More over, I just logged into it on my computer, with the Passkey saved in Bitwarden.

<!-- gh-comment-id:3821343893 --> @colemickens commented on GitHub (Jan 30, 2026): Then there is a massive Android bug here. I have one singular passkey provision for Peanut. I do NOT even have the Google Password manager enabled as an app, enabled in the OS, or enabled as a passkey provider. More over, I _just_ logged into it on my computer, with the Passkey saved in Bitwarden.
Author
Owner

@colemickens commented on GitHub (Jan 30, 2026):

Like, I'm not sure what to tell you all, the Android passkey UI is confusing. In the blacked out part of the video BITWARDEN OPENS and I authorize it to present the Passkey.

I can film this from my MBP if I really need to.

<!-- gh-comment-id:3821347480 --> @colemickens commented on GitHub (Jan 30, 2026): Like, I'm not sure what to tell you all, the Android passkey UI is confusing. In the blacked out part of the video **BITWARDEN OPENS** and I authorize it to present the Passkey. I can film this from my MBP if I really need to.
Author
Owner

@colemickens commented on GitHub (Jan 30, 2026):

  1. This shows a repro.
  2. This proves the passkey is in Bitwarden.

https://github.com/user-attachments/assets/43bf2e09-39a5-4b1c-b72e-67da51f01bb9

<!-- gh-comment-id:3821352408 --> @colemickens commented on GitHub (Jan 30, 2026): 1. This shows a repro. 2. This proves the passkey is in Bitwarden. https://github.com/user-attachments/assets/43bf2e09-39a5-4b1c-b72e-67da51f01bb9
Author
Owner

@pamperer562580892423 commented on GitHub (Jan 30, 2026):

Just for comparison: this is how it looks like when I choose a passkey that is stored in my BW vault (Android 15, BW mobile app 2026.1.0):

Image
<!-- gh-comment-id:3821353597 --> @pamperer562580892423 commented on GitHub (Jan 30, 2026): Just for comparison: this is how it looks like when I choose a passkey that is stored in my BW vault (Android 15, BW mobile app 2026.1.0): <img width="500" height="1062" alt="Image" src="https://github.com/user-attachments/assets/bc7e9a02-1adc-4c87-a3c0-94bdf0311e74" />
Author
Owner

@colemickens commented on GitHub (Jan 30, 2026):

As shown in the video above, my passkey is 100% coming from Bitwarden.

I am starting to wonder if Google is hijacking this in Chrome. A number of their documentation indicates that Chrome will just use Google Password Manager instead.

Which is really, really frustrating.

<!-- gh-comment-id:3821365219 --> @colemickens commented on GitHub (Jan 30, 2026): As shown in the video above, my passkey **is** 100% coming from Bitwarden. I am starting to wonder if Google is hijacking this in Chrome. A number of their documentation indicates that Chrome will just use Google Password Manager instead. Which is really, really frustrating.
Author
Owner

@colemickens commented on GitHub (Jan 30, 2026):

To further emphasize that I DO NOT use Google Password Manager, please see: which show NO provisioned accounts, and that it is disabled.

Image Image
<!-- gh-comment-id:3821369442 --> @colemickens commented on GitHub (Jan 30, 2026): To further emphasize that I DO NOT use Google Password Manager, please see: which show NO provisioned accounts, and that it is disabled. <img width="1080" height="2410" alt="Image" src="https://github.com/user-attachments/assets/fd767847-bbee-48f5-8f9a-7b02d6117b2c" /> <img width="1080" height="2410" alt="Image" src="https://github.com/user-attachments/assets/f60b752a-cd6c-4b94-8617-5c1aebc0b80d" />
Author
Owner

@pamperer562580892423 commented on GitHub (Jan 30, 2026):

Yeah, I saw your latest video. The unlock dialog is from Bitwarden - but the passkey you then choose is definitely not from Bitwarden.

Hm, GitHub is only for bug reports.

I think I can only say the following things now (as only another user):

  1. Follow what @sshadminBW wrote.
  2. ... and that would be also: you can seek assistance from the BW Community: https://community.bitwarden.com
  3. ... and/or contact BW support: https://bitwarden.com/contact/
  4. Personally, I would also generally recommend this Community Guide for the Android app (where you could at least check your settings / set up / configuration): https://community.bitwarden.com/t/short-guide-tips-autofill-on-android/88941
<!-- gh-comment-id:3821370966 --> @pamperer562580892423 commented on GitHub (Jan 30, 2026): Yeah, I saw your latest video. The unlock dialog is from Bitwarden - but the passkey you then choose is definitely not from Bitwarden. Hm, GitHub is only for bug reports. I think I can only say the following things now (as only another user): 1. Follow what @sshadminBW wrote. 2. ... and that would be also: you can seek assistance from the BW Community: https://community.bitwarden.com 3. ... and/or contact BW support: https://bitwarden.com/contact/ 4. Personally, I would also generally recommend this Community Guide for the Android app (where you could at least check your settings / set up / configuration): https://community.bitwarden.com/t/short-guide-tips-autofill-on-android/88941
Author
Owner

@colemickens commented on GitHub (Jan 30, 2026):

As I've again shown with screenshots, I do not use Google Password Manger. I do not have a passkey provisioned with Google Password Manager. I do not think you are correct.

<!-- gh-comment-id:3821373650 --> @colemickens commented on GitHub (Jan 30, 2026): As I've *again* shown with screenshots, I do not use Google Password Manger. I do not have a passkey provisioned with Google Password Manager. I do not think you are correct.
Author
Owner

@colemickens commented on GitHub (Jan 30, 2026):

If the passkey were in Google Password Manager, I would not be able to login with the passkey provisioned in Bitwarden. As I just did, repeatedly, on my laptop, from Firefox.

Peanut does NOT allow more than one passkey, it's literally impossible. Like, the passkey is the private key to my wallet. It is strictly impossible for there to be two provisioned passkeys for it.

<!-- gh-comment-id:3821376104 --> @colemickens commented on GitHub (Jan 30, 2026): If the passkey were in Google Password Manager, I would not be able to login with *the passkey provisioned in Bitwarden*. As I just did, repeatedly, on my laptop, from Firefox. Peanut does NOT allow more than one passkey, **it's literally impossible**. Like, the passkey is the private key to my wallet. It is strictly impossible for there to be two provisioned passkeys for it.
Author
Owner

@pamperer562580892423 commented on GitHub (Jan 30, 2026):

  1. I don't think that you can deactivate Google Password Manager on Android completely, as it is the "platform credential manager", which also mediates the use of third-party passkey providers like the Bitwarden app.
  2. Could you please check your Google account for any stored passkeys?
<!-- gh-comment-id:3821425083 --> @pamperer562580892423 commented on GitHub (Jan 30, 2026): 1. I don't think that you can deactivate Google Password Manager on Android completely, as it is the "platform credential manager", which also _mediates_ the use of third-party passkey providers like the Bitwarden app. 2. Could you please check your Google account for any stored passkeys?
Author
Owner

@colemickens commented on GitHub (Jan 30, 2026):

As I just showed in the screenshots above, Google Password Manager has NO accounts nor passkeys.

I also know to check Google Password Manager (my account), and (my device). BOTH report zero accounts or passkeys. I'm happy to provide screenshots if it would help.

Furthermore, the UX changes if I lock Bitwarden, and /any/ movement through the GPM screen that we are worried about opens Bitwarden, prompts me to unlock it specifically, then when I return to GPM and click "More options", it indicates it's going to use the Passkey it discovered from Bitwarden.

<!-- gh-comment-id:3821431653 --> @colemickens commented on GitHub (Jan 30, 2026): As I just showed in the screenshots above, Google Password Manager has NO accounts nor passkeys. I also know to check Google Password Manager (my account), and (my device). BOTH report zero accounts or passkeys. I'm happy to provide screenshots if it would help. Furthermore, the UX changes if I lock Bitwarden, and /any/ movement through the GPM screen that we are worried about opens Bitwarden, prompts me to unlock it specifically, then when I return to GPM and click "More options", it indicates it's going to use the Passkey it discovered from Bitwarden.
Author
Owner

@pamperer562580892423 commented on GitHub (Jan 30, 2026):

I also know to check Google Password Manager (my account)

Yeah, that screen here - from your phone - would be interesting (BTW, redact your personal info if you post it - we don't need to see everything):

Image

 

What would also be helpful: more infos to your device. Best thing (in general for this GitHub repository): in the Android app, go to Settings --> About --> Version --> and from there, you can copy (& paste here) all relevant device and app info.

<!-- gh-comment-id:3821471640 --> @pamperer562580892423 commented on GitHub (Jan 30, 2026): > I also know to check Google Password Manager (my account) Yeah, that screen here - from your phone - would be interesting (BTW, redact your personal info if you post it - we don't need to see everything): <img width="400" height="882" alt="Image" src="https://github.com/user-attachments/assets/53e56fda-5c86-43ef-9423-8a8f031fdbd4" /> &nbsp; What would also be helpful: more infos to your device. Best thing (in general for this GitHub repository): in the Android app, go to Settings --> About --> Version --> and from there, you can copy (& paste here) all relevant device and app info.
Author
Owner

@colemickens commented on GitHub (Jan 30, 2026):

Heh... That IS the page I showed above 😉 . It's literally empty, with the text "You'll find your Accounts and Passkeys here". haha.

But I can upload 2 new screenshots, one will have my account icon, the other will be from "the device" so you can be very, very, very sure that I have never once let a Passkey touch a Google Password Manager.

As for the version info, what app? I doubt I can screenshot the Bitwarden app. I'll try to screenshot them both, or at least provide you the version information.

EDIT: Cool, I see what you mean now - when I tap "Version" it gives me a chunk of text. Incoming...

<!-- gh-comment-id:3821484562 --> @colemickens commented on GitHub (Jan 30, 2026): Heh... That _IS_ the page I showed above 😉 . It's literally empty, with the text "You'll find your Accounts and Passkeys here". haha. But I can upload 2 new screenshots, one will have my account icon, the other will be from "the device" so you can be very, very, very sure that I have never once let a Passkey touch a Google Password Manager. As for the version info, what app? I doubt I can screenshot the Bitwarden app. I'll try to screenshot them both, or at least provide you the version information. EDIT: Cool, I see what you mean now - when I tap "Version" it gives me a chunk of text. Incoming...
Author
Owner

@colemickens commented on GitHub (Jan 30, 2026):

© Bitwarden Inc. 2015-2026

Version: 2026.1.0 (21141)
📱 google Pixel 10 Pro 🤖 16@36 📦 prod
🧱 commit: bitwarden/android/release/2026.1-rc42@67f83e3020b53f8d41e63a7d8f6bdb759ccb9ddc
💻 build source: bitwarden/android/actions/runs/21299199924/attempts/1
🦀 SDK: 2.0.0-4441-c5a3b833
🌩 Server: Vaultwarden 2025.12.0

And screenshot 1 is Google Password Manager (Cole.mickens@gmail.com). screenshot 2 is Google Password Manager (device).

Note they both show zero accounts passwords or passkeys.

Image Image
<!-- gh-comment-id:3821501019 --> @colemickens commented on GitHub (Jan 30, 2026): ``` © Bitwarden Inc. 2015-2026 Version: 2026.1.0 (21141) 📱 google Pixel 10 Pro 🤖 16@36 📦 prod 🧱 commit: bitwarden/android/release/2026.1-rc42@67f83e3020b53f8d41e63a7d8f6bdb759ccb9ddc 💻 build source: bitwarden/android/actions/runs/21299199924/attempts/1 🦀 SDK: 2.0.0-4441-c5a3b833 🌩 Server: Vaultwarden 2025.12.0 ``` And screenshot 1 is Google Password Manager (Cole.mickens@gmail.com). screenshot 2 is Google Password Manager (device). Note they both show zero ~~accounts~~ passwords or passkeys. <img width="1080" height="2410" alt="Image" src="https://github.com/user-attachments/assets/811b096f-bae0-4b31-ae7e-57dc9fdfde3a" /> <img width="1080" height="2410" alt="Image" src="https://github.com/user-attachments/assets/5ccf9a6c-e35b-4ba9-92a7-b29b2b97ac34" />
Author
Owner

@pamperer562580892423 commented on GitHub (Jan 30, 2026):

Heh... That IS the page I showed above 😉 . It's literally empty, with the text "You'll find your Accounts and Passkeys here". haha.

I think your screenshots only showed the "on the device" part. If you tap on the icon (top right) you can choose your Google account - and yeah, that's what I specifically meant:

Image

 

What do you see, when you choose your Google account there?

<!-- gh-comment-id:3821512903 --> @pamperer562580892423 commented on GitHub (Jan 30, 2026): > Heh... That _IS_ the page I showed above 😉 . It's literally empty, with the text "You'll find your Accounts and Passkeys here". haha. I think your screenshots only showed the "on the device" part. If you tap on the icon (top right) you can choose your Google account - and yeah, that's what I specifically meant: <img width="400" height="536" alt="Image" src="https://github.com/user-attachments/assets/2075acb9-fa15-4de4-9bb5-caac45388e91" /> &nbsp; What do you see, when you choose your Google account there?
Author
Owner

@colemickens commented on GitHub (Jan 30, 2026):

No, the first screenshots up above have my Google avatar in the corner.

But regardless, the second set of screenshots show both of them completely empty of passwords+passkeys as described.

And sure I can show you this too, to show you I only have one Google account:

Image
<!-- gh-comment-id:3821522596 --> @colemickens commented on GitHub (Jan 30, 2026): No, the first screenshots up above have my Google avatar in the corner. But regardless, the second set of screenshots show both of them completely empty of passwords+passkeys as described. And sure I can show you this too, to show you I only have one Google account: <img width="1080" height="2410" alt="Image" src="https://github.com/user-attachments/assets/5edef1a4-97dc-4bfb-ade6-6f989149ffb8" />
Author
Owner

@pamperer562580892423 commented on GitHub (Jan 30, 2026):

Ah. Thanks!

Hmm. That really is strange then.

<!-- gh-comment-id:3821535761 --> @pamperer562580892423 commented on GitHub (Jan 30, 2026): Ah. Thanks! Hmm. That really is strange then.
Author
Owner

@pamperer562580892423 commented on GitHub (Jan 30, 2026):

And that you use Vaultwarden also makes it more complicated. Because now we also don't know, if the server-client interaction also comes into play here - and neither Bitwarden nor Vaultwarden could be sure, if either one would be involved or not.

The cleanest thing would be, to try to reproduce this with an official BW server first (self-hosted or cloud). Vaultwarden recommend this themselves here: https://github.com/dani-garcia/vaultwarden/wiki/Bitwarden-clients-troubleshooting

<!-- gh-comment-id:3821546757 --> @pamperer562580892423 commented on GitHub (Jan 30, 2026): And that you use Vaultwarden also makes it more complicated. Because now we also don't know, if the server-client interaction also comes into play here - and neither Bitwarden nor Vaultwarden could be sure, if either one would be involved or not. The cleanest thing would be, to try to reproduce this with an official BW server first (self-hosted or cloud). Vaultwarden recommend this themselves here: https://github.com/dani-garcia/vaultwarden/wiki/Bitwarden-clients-troubleshooting
Author
Owner

@colemickens commented on GitHub (Jan 30, 2026):

  1. @pamperer562580892423 thanks for sticking it out with me, even if it ends on "strange" and "try the official server". I appreciate us exhausting other ideas.
  2. I have now setup a Bitwarden.com account and will try to see if it repros, and under what conditions.

I will note, the UX with the Bitwarden.com account is basically identical. (That is to say, really confusing).

At this point, I am actually more suspicious of the Google Password Manager and it's role as mediator... :/

Thanks again, I'll update if I find out anything interesting. I'll probably ask the Vaultwarden people what they think too. I'd assume Passkeys are cached locally like anything else - they're not exactly stateful as far as I know?

<!-- gh-comment-id:3821573394 --> @colemickens commented on GitHub (Jan 30, 2026): 1. @pamperer562580892423 thanks for sticking it out with me, even if it ends on "strange" and "try the official server". I appreciate us exhausting other ideas. 2. I have now setup a Bitwarden.com account and will try to see if it repros, and under what conditions. I will note, the UX with the Bitwarden.com account is basically identical. (That is to say, really confusing). At this point, I am actually more suspicious of the Google Password Manager and it's role as mediator... :/ Thanks again, I'll update if I find out anything interesting. I'll probably ask the Vaultwarden people what they think too. I'd assume Passkeys are cached locally like anything else - they're not exactly stateful as far as I know?
Author
Owner

@SaintPatrck commented on GitHub (Jan 30, 2026):

Hi @colemickens,

Could you enable Flight Recorder to capture logs when this issue manifests? I'd like to first confirm that Bitwarden is actually receiving the Passkey request in those instances where GPM shows up.

If you see "Get credential request received" in the logs you'll know that Bitwarden is receiving the request. Subsequent logs should indicate where it is failing, if it is within Bitwarden's process. If you do not see that log, it indicates GPM is somehow intercepting the request. In that case there is unfortunately little we can do since we never receive the request.

<!-- gh-comment-id:3824812869 --> @SaintPatrck commented on GitHub (Jan 30, 2026): Hi @colemickens, Could you enable Flight Recorder to capture logs when this issue manifests? I'd like to first confirm that Bitwarden is actually receiving the Passkey request in those instances where GPM shows up. If you see "Get credential request received" in the logs you'll know that Bitwarden is receiving the request. Subsequent logs should indicate where it is failing, if it is within Bitwarden's process. If you do not see that log, it indicates GPM is somehow intercepting the request. In that case there is unfortunately little we can do since we never receive the request.
Author
Owner

@colemickens commented on GitHub (Jan 30, 2026):

Hi @SaintPatrck,

To reiterate this, as I did on the forum:

  1. Peanut.me only allows a single Passkey. It is literally the private key to the wallet. It's categorically impossible for their to be multiple keys. I use the passkey, in Bitwarden, in Firefox, on my laptop, every day.
  2. Every single GPM view, on desktop, in Chrome, in the Android app, says there are no passkeys or passwords.
  3. I have repeated this passkey login with Coinbase.com (one account with one passkey registered) in Chrome Android, and Google.com (one account with one passkey registered) in Chrome Android. That simply is what the UX looks like, when GPM is mediating access to passkeys.
    The passkey is coming from Bitwarden.

But sure:

  • turn on Flight Recorder
  • I logged out of Peanut
  • I logged into Peanut

In the midst of the logs:

2026-01-30 15:16:45:992 – DEBUG – c – App is backgrounded⏎
2026-01-30 15:16:59:096 – DEBUG – BitwardenCredentialProviderService – Get credential request received.⏎
2026-01-30 15:16:59:221 – DEBUG – n0 – Credentials retrieved.⏎
<!-- gh-comment-id:3825046890 --> @colemickens commented on GitHub (Jan 30, 2026): Hi @SaintPatrck, To reiterate this, as I did on the forum: 1. Peanut.me only allows a single Passkey. It is literally the private key to the wallet. It's categorically impossible for their to be multiple keys. I use the passkey, in Bitwarden, in Firefox, on my laptop, every day. 2. Every single GPM view, on desktop, in Chrome, in the Android app, says there are no passkeys or passwords. 3. I have repeated this passkey login with Coinbase.com (one account with one passkey registered) in Chrome Android, and Google.com (one account with one passkey registered) in Chrome Android. That simply **is** what the UX looks like, when GPM is mediating access to passkeys. The passkey is coming from Bitwarden. But sure: - turn on Flight Recorder - I logged out of Peanut - I logged into Peanut In the midst of the logs: ``` 2026-01-30 15:16:45:992 – DEBUG – c – App is backgrounded⏎ 2026-01-30 15:16:59:096 – DEBUG – BitwardenCredentialProviderService – Get credential request received.⏎ 2026-01-30 15:16:59:221 – DEBUG – n0 – Credentials retrieved.⏎ ```
Author
Owner

@colemickens commented on GitHub (Jan 30, 2026):

Full log here, just for good measure.

flight_recorder_2026-01-30_15-16-42.txt

<!-- gh-comment-id:3825050568 --> @colemickens commented on GitHub (Jan 30, 2026): Full log here, just for good measure. [flight_recorder_2026-01-30_15-16-42.txt](https://github.com/user-attachments/files/24971808/flight_recorder_2026-01-30_15-16-42.txt)
Author
Owner

@pamperer562580892423 commented on GitHub (Jan 30, 2026):

To reiterate this, as I did on the forum:

@SaintPatrck This forum thread is meant: https://community.bitwarden.com/t/android-says-no-passkeys-available-invalidly/93346

<!-- gh-comment-id:3825237481 --> @pamperer562580892423 commented on GitHub (Jan 30, 2026): > To reiterate this, as I did on the forum: @SaintPatrck This forum thread is meant: https://community.bitwarden.com/t/android-says-no-passkeys-available-invalidly/93346
Author
Owner

@trebory6 commented on GitHub (Mar 31, 2026):

Jumping in here to mention I'm having the same exact issue with gmail. I have a gmail email with a passkey stored in Bitwarden and I can't sign in with it because I get the same message. I figured it had more to do with gmail defaulting to the Google password manager but seeing this topic I'm not so sure.

Also, @colemickens, reading through this thread was painful watching you painstakingly show how you don't have any passkeys stored with Google, and still repeatedly not being understood or believed. You truly have way more patience than I do, I'd probably have gotten kicked off the topic within the first few messages. 😅 Know I commiserate with your frustration!

<!-- gh-comment-id:4162925589 --> @trebory6 commented on GitHub (Mar 31, 2026): Jumping in here to mention I'm having the same exact issue with gmail. I have a gmail email with a passkey stored in Bitwarden and I can't sign in with it because I get the same message. I figured it had more to do with gmail defaulting to the Google password manager but seeing this topic I'm not so sure. Also, @colemickens, reading through this thread was painful watching you painstakingly show how you don't have any passkeys stored with Google, and still repeatedly not being understood or believed. You truly have way more patience than I do, I'd probably have gotten kicked off the topic within the first few messages. 😅 Know I commiserate with your frustration!
Author
Owner

@pamperer562580892423 commented on GitHub (Mar 31, 2026):

@trebory6 It might have been shorter, if we would have known from the start, that Google Password Manager was deactivated, causing this "anomaly". (if I remember correctly) 😉

And about your issue: as Gmail is Google, it might be connected to this issue: https://github.com/bitwarden/android/issues/5506

<!-- gh-comment-id:4162999723 --> @pamperer562580892423 commented on GitHub (Mar 31, 2026): @trebory6 It might have been shorter, if we would have known from the start, that Google Password Manager was deactivated, causing this "anomaly". (if I remember correctly) 😉 And about your issue: as Gmail is Google, it might be connected to this issue: https://github.com/bitwarden/android/issues/5506
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/android#28333