trussed-dev/fido-authenticator

Setup configured on Windows for Github fails to work on Android

Opened this issue · 8 comments

See title. Add a key on Github on Windows, go to use it on Android + ChromeOS and it can't ready the key.

Any logs, etc, I can provide just let me know.

Have similar issue (I think). Used all 3 keys on Windows and none of them work now on Android

Android USB or Android NFC?

Android NFC for me

I don't have the means to debug NFC myself, will ask Conor to dig in once USB (on desktops) works better.

I have what seems to be the same issue. I recently got a new Solo V2 and added it to my Google account on Chrome on my (Linux) laptop - worked fine. I then tried logging into Google in an incognito window in Chrome on my Pixel 6 Pro phone (up-to-date Android 12 etc), and was not able to get the new Solo V2 to work either via USB or NFC. If I try USB, the green LED on the key lights up and I get a pop up asking if I want to let Google Play Services access my security key, but if I click OK and touch the gold contacts, nothing happens on the phone and I can't get past the 2FA challenge. If I try NFC, the failure is slightly different: when the key gets in NFC range of the phone, the browser screen advances to "There was a problem Try using your security key again or try another way..." and I never got it to work even with about 10x retries.

I also have an older Solo V1, and that did work on my phone (with a USB A->C adapter). I get the same Google Play Services pop up when I plug in the key, click OK, press the button on my key, and the login completes.

As above - happy to provide any logs or other debugging help.

@nickray Actually, the very same solo key used via USB on windows and via USB on android on Facebook is recognized as 2 different keys... 🤔

@nickray any progress on this? It's been months...

FYI new release 2.964.0 still has the issue