Weird. At no point am i asked about bluetooth permissions.
1 Like
I used the default.
1 Like
I can’t even get Passkeys to work on windows 11 with a USB NFC reader. I tried Bitwarden, Facebook and Google.
Can you tell us more? What are you trying? What’s happening? Have you tested with webauthn.io?
1 Like
Did you get it working with acar’s tips?
1 Like
I didn’t see a “allow bluetooth” anywhere.
I’m not super worried because I’ll have to uninstall the bridge soon because it breaks U2F 
Read this for the fix that makes the passkey bridge work and brings back other types of devices.
2 Likes
I mean, I blame graphine for this as well. When I need to use my u2f applet in my right Apex, I’m still given the chance to try “other devices” then use Google’s native NFC security key option and it works just fine.
So the “it” here is not the Bridge app
2 Likes
That said, I will see if it’s even possible to run ctap1 through this architecture. If it is, I’ll see about updating passkey bridge to support legacy security keys.
2 Likes
Sorry, you said usb reader. I assumed you were using a desktop so why is the bridge involved at all?
1 Like
I was responding to amal and your phone screenshots showing the bridge. I’ll have to get you photos of the windows / USB reader tomorrow. Probably need that in a new thread? Since its not bridge related
1 Like
Verifying that your passkey actually works is fundamental to troubleshooting 
I’ve never been able to make one. I’ll send more info tomorrow.
I just got it to work. Turn on google play services for auth. Passkey bridge will be under “more.” Apparently all the CTAP2 UI is piped through play services on Android, i guess.
1 Like
I also just got it to work.. in NFC Passkey Bridge.. CTAP1/U2F support. Well.. half way. I got authentication to work. I figure half-support is good enough, who’s registering U2F tokens with services these days? The only reason I even bothered was the logging feature.. not knowing where you’re using your U2F tokens is very nerve wracking, so I’m now using my one U2F token exclusively with Bridge just so I can get a running log of RPs I use it with.
Official release on Google Play soon™, after more testing.
2 Likes
i just noticed your version is v1.1.4 and we’re currently on v1.2.3.. the “linux fix” was very recent.. upgrade your version at google play .. it might just magically start working.
2 Likes
damn. well that graphine-ready phone should be arriving soon.
2 Likes
v1.3.0 submitted to google for review. this version adds U2F security key authentication support.
4 Likes
