Bluetooth tests latest version

[arenddeboer]

In light of the request to test Bluetooth on the latest version, these are my findings.
OS: Ubuntu 24.04
Chrome: 131 64bit
Watch: Galaxy Watch 7 Ultra / Wear OS 5.0

Working great with Amazon AWS console, registering and logging tested. (https://aws.amazon.com/console/)

Trying to register on the below demo site doesn't work:
https://webauthn.io/

The dev console shows the following:

p Conditional UI
(index):693 AUTHENTICATION OPTIONS
(index):694 {
"challenge": "9tXER9Rb-Qpx9zVbxmMU0mgayo46NLF--oj4RQmx_Nxww_44qeTZ-cooDRP3JLR1XhQO-vJ9POniubOuDVXOAw",
"timeout": 60000,
"rpId": "webauthn.io",
"allowCredentials": [],
"userVerification": "preferred"
}
(index):644 REGISTRATION OPTIONS
(index):645 {
"rp": {
"name": "webauthn.io",
"id": "webauthn.io"
},
"user": {
"id": "Km093UrRAkbEhA_w9zvgQTBegce9fChZZlGqHFFhVeo",
"name": "watchbt",
"displayName": "watchbt"
},
"challenge": "Txhwhg-ggypxVGKJOLFwLyuar2WoAs2IPolQijEaHpZpbGiidEqDcjyneuS_BeReGSksVRhSbLFFSGH2SsptEA",
"pubKeyCredParams": [
{
"type": "public-key",
"alg": -8
},
{
"type": "public-key",
"alg": -7
},
{
"type": "public-key",
"alg": -257
}
],
"timeout": 60000,
"excludeCredentials": [],
"authenticatorSelection": {
"residentKey": "preferred",
"requireResidentKey": false,
"userVerification": "preferred"
},
"attestation": "none",
"hints": [],
"extensions": {
"credProps": true
}
}
(index):737 Conditional UI request was aborted

[arenddeboer]

The same error is shown when trying to register over Bluetooth on the following sites:
https://www.passkeys.io/
https://passkeys.guru/
https://www.token2.com/tools/fido2-demo
https://myaccount.google.com/

[arenddeboer]

On Windows 11 with either Chrome or Edge, when I select a security key to login with, it doesn't show a popup on the Watch while having the watch paired to Windows. Not sure exactly how this auth flow should work though. What I did:

• Pair watch with Windows 11 (it's showing connected on Watch and in Windows 11)
• Go to test website eg: https://www.token2.com/tools/fido2-demo
• Click register + various popups (see screenshots), but the Watch does not show a continue with this security key dialog.

[fmeum]

Thanks for the detailed test run, this is really helpful!

The Linux issue with only certain sites sounds like a logic issue that shouldn't be too difficult to fix. I hope that I can take a look soon.

Windows 10 supported WearAuthn pretty well, but I haven't personally tested it with Windows 11 yet. Since Windows Hello is closed source and changes pretty rapidly, I'm not sure whether we can realistically fix this issue.