N3rdTek ok so I've got good news, bad news, and strange AF news.
Let's start with the strange; correct me if I'm wrong but passkeys requires Android 14, correct? I have a few devices on hand due to being a tech enthusiast, one of which is a Galaxy S10. It only supports Android 12 because "Reasons" yet feels faster than my Pixel 7.... at times, but rarely ever worse.
However, not only can I create & sign into passkeys.io with a passkey, after enabling the chrome flag , I can do it with my Google account also. It doesn't seem to even respect my Autofill choice of 1Passwors having disabled Google as my Autofill choice in settings. Yet still detects, authenticates, and signs me into my Google account using Google password manager.
And to top it off? When I initially tested passkeys.io I wasn't aware I was doing from my S10 initially. When I went to test on my pixel, it asked if I wanted to sign in using my saved passkey from the S10....Stange AF right?
Now the bad; my pixel 7 running GoS will not work for any of my Google accounts. I've tried just about everything;
- setting 1pw as autofill
- Setting Google as autofill
- Trying regular ol chrome browser
- Trying Chrome Canary
- Trying any other browser
- Trying a brand new never used before browser (Vivaldi)
- Completely removing the Google account from device then trying
Feel free to prove me wrong I spent upwards of last hour testing.
And the good?
It works for passkey.io, it works for GitHub, I'm getting ready to try a couple more but general consensus so far seems to concur our devices will support passkeys to almost everything but Google.
Provided that you;
- enable the chrome flag as mentioned earlier
chrome://flags/#web-authentication-android-credential-management
- set your password manager as autofill
- then attempt to register your passkey/device
This is useful to know but man, what a janky as hell future to get rid of passwords amirite?