Yes, it was set to direct and still no luck. I haven’t tested with the latest version of bridge yet. Which browser are you using?
1 Like
Update v1.3.8 to fix outlier U2F auth bug pushed to Google for review
2 Likes
I’ve tested Firefox and Chrome. I think also Brave.
1 Like
Yeah that link in my last response has chrome and firefox tested. This may be an issue with Samsung phones in general especially if Amal isn’t having the same issues as in that chart. I’d love to dig into this and get the bridge working as a viable drop-in to fill the gaps that android is lacking at the moment. Especially since Samsung is 30.8% of the android market share #ref.
The marketer in me also suspects that filling this gap could seriously boost the sales and visibility of Vivokey as a brand as the annoyed users of yubikeys are frequently complaining about this as well https://www.reddit.com/r/yubikey/comments/1lyf2z0/fido_2_passkey_nfc_prompt_not_working_on_android/ and they should in theory also be able to use this app. This momentum could be awesome growth for vivokey, at least until android implements the function in the core OS.
1 Like
No luck on 1.3.7 on Firefox on grapheneos 
2 Likes
Just to double check things we checked together at the event one more time: when you do the exact same thing with a reader on a PC, you do get a valid aaguid?
Edit: well not the EXACT same thing. I want ti confirm the app is still installed ans configured propety.
1 Like
-
i’m going to look at getting a Samsung s23 for testing
-
i’m going to take a harder look at that chart and respond to some of your observations
1 Like
samsung s23 ordered.
1 Like
my text pixel 7a arrived today. @tac0s put graphene on it. ironically i think we got the graphine buggies out before it even arrived.
3 Likes
Graphene 
1 Like
GraFINE…
6 Likes
Confession time: I only use Linux and I never got a USB reader configured correctly on it 
2 Likes
What reader do you have? I had the 122u working on linux but i had to break a bunch of shit and it wasn’t worth it.
1 Like
Correct: For the native “NFC Security Key”:
- Enrollment + Firefox: I see the option but enrollment doesn’t work
- Enrollment + Chrome: no option (USB only)
- Sign-In + Firefox: no option (USB only)
- Sign-In + Chrome: no option (USB only)
For the VK NFC Bridge:
- Enrollment + Firefox: I see the option and enrollment works
- Enrollment + Chrome: I see the option and enrollment works
- Sign-In + Firefox: I sign in without being prompted for a PIN. I do actually log in
- Sign-In + Chrome: NFC Bridge modal says success, but I never get logged in in the browser
1 Like
I’ve never had any issues with the ACR 1252U (or most other PC/SC readers) on Linux, but I pretty much only run stock Debian or its non-Ubuntu variants. I just install pcsc-lite and libpcsclite-dev and am able to read tags, install applets, etc. Now actually getting cards/applets to work with things like the browser is a whole different beast.
3 Likes
silly question.. do you have pin caching turned on?
are you prompted for a pin in this case?
1 Like
I’ll need to try again with my 1252u. I also have a 1552u on the way. I can test both to see if I can get something to work. But yeah, actually getting things integrated is the battle 
We really need an all-in-one NFC manager app for Linux that can handle getting things integrated for NFC signin + browser integration for passkeys + applet installation
No. Tripple-checked as that was my first thought to. Even turned it on then back off to be safe.
No – the sign-in flow with the NFC Bridge presents the same on Chrome and Firefox. But on Firefox, passkeys.io briefly flashes an error then logs me in. On Chrome, I just remain on the log in screen.
I’m sending you a screen recording of the enrollment and sign-in flows for both Firefox and Chrome.
2 Likes
does this happen on webauthn.io or webauthn.me as well or just passkeys.io?
1 Like
