So I was in Chrome on my Chromebook at https://myaccount.google.com/signinoptions/passkeys and clicked Create a passkey. Bitwarden asked where I wanted to save it and I pointed it to my Google.com login. It saved the passkey there. I verified that it did. Then I went to payments.google.com (which, since it is a “sensitive” action, engenders a passkey prompt). I got asked which passkey I wanted to use. I pointed it at the very same Google.com login in which I had just saved the passkey. When I clicked on it I ended up with an error window with the title Log in with passkey? that said “No passkeys found for this application.”. Like WTF? This makes no sense at all. What am I missing here?
Can you login on any other Google site with that newly created passkey?
(And I just tested it with a Google account – no issue to log in to payments.google.com with that regular Google passkey stored in a BW login item. // browser extension 2026.3.0, Vivaldi browser, Windows 11)
It seems to fail only when I try to verify my identity for some “sensitive” action that Google requires an extra verification step for. Perhaps it’s got something to do with the passkey having been created on a Chromebook.
Oh nevermind, it seems this is a side effect of me having had to powerwash my Chromebook due to some really bad advice I got from Gemini. Apparently Google is paranoid that my machine may have been stolen and so is refusing to allow my saved passkeys to work until it is sure I am really me, which I am told by the same stupid AI that screwed me in the first place is going to take 7 days. Pfft.
I do have a bit of a beef with Bitwarden telling me that there are no passkeys for Google when there is clearly a freshly minted one right there in my Google login vault entry. Maybe it could say something like “no TRUSTED passkeys” or some such. It might have saved me from pulling out so much of my hair.
All these passkey issues makes me just want to go back to passwords and forget it all. The whole rollout has been badly bungled in my opinion, and I have 40 years in IT. I can imagine how all this is going over with your average Joe.