# Android says "No passkeys available" invalidly

**URL:** <https://community.bitwarden.com/t/android-says-no-passkeys-available-invalidly/93346>\
**Category:** Password Manager\
**Tags:** app:mobile, server:selfhost, os:android\
**Created:** [January 30, 2026, 2:15am UTC](https://community.bitwarden.com/t/android-says-no-passkeys-available-invalidly/93346 "2026-01-30T02:15:59Z")\
**Posts on this page:** 10\
**Page:** 1

<div class="post-metadata">

**Author:** ![colemickens](https://sea1.discourse-cdn.com/flex001/user_avatar/community.bitwarden.com/colemickens/32/44054_2.png) [@colemickens](https://community.bitwarden.com/u/colemickens)\
**Post date:** [January 30, 2026, 2:15am UTC](https://community.bitwarden.com/t/android-says-no-passkeys-available-invalidly/93346/1 "2026-01-30T02:15:59Z")

</div>

I filed this bug, but it feels like I’m not going to get any more answers.

> <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.

1. Bitwarden is the only passkey provider enabled.
2. I have a video of the Passkey working.
3. I have screenshots of the enroll passkeys.
4. I have a screenshot showing Bitwarden is the only passkey provider.
5. I have screenshots of Google Password Manager having NO accounts/passkeys.
6. I have a video of the Passkey working, via Bitwarden.

As the bug says **SPORADICALLY** Android will incorrectly report that there are no passkeys available.

I am concerned this is actually an Android bug, rather than Bitwarden.

What do I do now?

---

<div class="post-metadata">

**Author:** ![colemickens](https://sea1.discourse-cdn.com/flex001/user_avatar/community.bitwarden.com/colemickens/32/44054_2.png) [@colemickens](https://community.bitwarden.com/u/colemickens)\
**Post date:** [January 30, 2026, 3:20am UTC](https://community.bitwarden.com/t/android-says-no-passkeys-available-invalidly/93346/3 "2026-01-30T03:20:03Z")

</div>

Shout-out to the user that saw it through to … a conclusion with me 🙂 .

I’m not sure what to take away. I guess it’s either:

1. Google Password Manager being weird, while doing its mediation
2. somehow a vaultwarden thing (I assumed passkeys would be cached locally)
3. some really odd bitwarden bug

Appreciate the help; sad at the conclusion(s).

Would be curious if anyone else has thoughts, or has seen this.

---

<div class="post-metadata">

**Author:** ![grb](https://sea1.discourse-cdn.com/flex001/user_avatar/community.bitwarden.com/grb/32/22038_2.png) [@grb](https://community.bitwarden.com/u/grb)\
**Post date:** [January 30, 2026, 3:51am UTC](https://community.bitwarden.com/t/android-says-no-passkeys-available-invalidly/93346/4 "2026-01-30T03:51:17Z")

</div>

Were you able to reproduce the issue using your test account on `bitwarden.com`?

---

<div class="post-metadata">

**Author:** ![colemickens](https://sea1.discourse-cdn.com/flex001/user_avatar/community.bitwarden.com/colemickens/32/44054_2.png) [@colemickens](https://community.bitwarden.com/u/colemickens)\
**Post date:** [January 30, 2026, 4:04am UTC](https://community.bitwarden.com/t/android-says-no-passkeys-available-invalidly/93346/5 "2026-01-30T04:04:44Z")

</div>

Hi @grb,

I have not been able to reproduce on either account ([bitwarden.com](http://bitwarden.com), or self-hosted Vaultwarden) in the last hour or so. I have inquired in the Vaultwarden Matrix room - if they have any ideas, if they know if server interaction is utilized when using a passkey, any hints really.

Like I said though, this whole thing has left a bad taste in my mouth regarding Google Password Manager. As shown in that GitHub thread, the UX is /very/ confusing, and I’m starting to wonder if it’s more of a bug in the GPM mediation logic, rather than in the Bitwarden Android client…

Or maybe it’s Vaultwarden, I don’t know. Hopefully the next repro will give some more clues … 🙃 .

---

<div class="post-metadata">

**Author:** ![Nail1684](https://sea1.discourse-cdn.com/flex001/user_avatar/community.bitwarden.com/nail1684/32/47626_2.png) [@Nail1684](https://community.bitwarden.com/u/Nail1684)\
**Post date:** [January 30, 2026, 10:47am UTC](https://community.bitwarden.com/t/android-says-no-passkeys-available-invalidly/93346/6 "2026-01-30T10:47:56Z")

</div>

> [@colemickens](#):
>
> I’m not sure what to take away. I guess it’s either:

Especially if that is the only passkey in your vault that shows such a behaviour, I maybe would add to that list: “Peanut may have a quirk in their passkey implementation” (wouldn’t be the first service ever…)

PS: Your phone is on the official ROM?

---

<div class="post-metadata">

**Author:** ![colemickens](https://sea1.discourse-cdn.com/flex001/user_avatar/community.bitwarden.com/colemickens/32/44054_2.png) [@colemickens](https://community.bitwarden.com/u/colemickens)\
**Post date:** [January 30, 2026, 3:23pm UTC](https://community.bitwarden.com/t/android-says-no-passkeys-available-invalidly/93346/7 "2026-01-30T15:23:49Z")

</div>

Yes. Folks, I use a very standard Google Pixel 10 Pro, it is updated daily. I do not do ANYTHING remotely weird with it. I write Rust and Nix and build a Linux distribution for my day job, I’ve been using Android since the G1, I promise I have some basic competency.

And again, I’m not sure what to say about the confusion around the UX:

Coinbase also has ONE Passkey registered to my account, it is in Bitwarden, and the Passkey login UX for [Coinbase.com](http://Coinbase.com) in Chrome is **IDENTICAL** to the login flow as presented by [Peanut.me](http://Peanut.me).

Just did [Google.com](http://Google.com), same UX.

([Peanut.me](http://Peanut.me) is a PWA).

---

<div class="post-metadata">

**Author:** ![colemickens](https://sea1.discourse-cdn.com/flex001/user_avatar/community.bitwarden.com/colemickens/32/44054_2.png) [@colemickens](https://community.bitwarden.com/u/colemickens)\
**Post date:** [January 30, 2026, 3:25pm UTC](https://community.bitwarden.com/t/android-says-no-passkeys-available-invalidly/93346/8 "2026-01-30T15:25:47Z")

</div>

I really, really, really think this is because I had the Google Password Manager app disabled and it wasn’t updating. I assumed the core functionality was provided by Google Play Services / Google app, but maybe not. After the update, the UX changed _slightly_, and I have not been able to repro this after trying dozens and dozens of times.

tl;dr: pretty sure Google Password Manager **was** buggy, and **has** terrible confusing UX when acting as the passkey mediator.

---

<div class="post-metadata">

**Author:** ![Nail1684](https://sea1.discourse-cdn.com/flex001/user_avatar/community.bitwarden.com/nail1684/32/47626_2.png) [@Nail1684](https://community.bitwarden.com/u/Nail1684)\
**Post date:** [January 30, 2026, 3:39pm UTC](https://community.bitwarden.com/t/android-says-no-passkeys-available-invalidly/93346/9 "2026-01-30T15:39:37Z")

</div>

> [@colemickens](#):
>
> Yes. Folks, I use a very standard Google Pixel 10 Pro, it is updated daily. I do not do ANYTHING remotely weird with it. I write Rust and Nix and build a Linux distribution for my day job, I’ve been using Android since the G1, I promise I have some basic competency.

Sorry, I didn’t question your competency – I thought more about a possible custom ROM that could contribute to your issue (or not).

As in the comments in your GitHub issue already implied: you can see on the popups that say “Google Password Manager”, that Google Password Manager can’t be disabled entirely on an Android phone… Keep us posted if the updates of Google Password Manager finally resolve it.

PS:

> [@colemickens](#):
>
> Shout-out to the user that saw it through to … a conclusion with me 🙂 .

I know who that was. Will forward it to him. 😉

---

<div class="post-metadata">

**Author:** ![colemickens](https://sea1.discourse-cdn.com/flex001/user_avatar/community.bitwarden.com/colemickens/32/44054_2.png) [@colemickens](https://community.bitwarden.com/u/colemickens)\
**Post date:** [January 30, 2026, 3:40pm UTC](https://community.bitwarden.com/t/android-says-no-passkeys-available-invalidly/93346/10 "2026-01-30T15:40:46Z")

</div>

Thanks Nail, you definitely didn’t but I figured I’d try to set the stage.

Really appreciate all of the thoughts and help from folks. Going to mark this as solved. I’ll update if I get any more data points.

❤

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex001/uploads/bitwarden1/original/1X/681d35175c3ce2ae5f010fa0bb448862f79a2399.png) [@system](https://community.bitwarden.com/u/system)\
**Post date:** [March 1, 2026, 3:41pm UTC](https://community.bitwarden.com/t/android-says-no-passkeys-available-invalidly/93346/11 "2026-03-01T15:41:16Z")

</div>

Closed on March 1, 2026, 3:41pm UTC

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.
