search

fmeum / WearAuthn

Use your Wear OS watch as a FIDO2 security key via Bluetooth and NFC.
https://play.google.com/store/apps/details?id=me.henneke.wearauthn.authenticator
MIT License
183 stars 7 forks source link

Attempt to automatically connect to first device #6

Open dancojocaru2000 opened 4 years ago

dancojocaru2000 commented 4 years ago

What went wrong? When paired with more than one device, WearAuthn will automatically try to attach to the first device in the list when starting the app. If the device is not available, WearAuthn will be unusable, stuck in an "Attaching..." state. The only way to connect to other devices in the list is to have the first one available with Bluetooth on, and then go back and select any of the other ones.

Steps to reproduce

  1. Pair with multiple devices
  2. Close WearAuthn entirely
  3. Open WearAuthn app

Which model is your watch? Ticwatch E

Which Android version is running on your watch? 8.0:0

Which version of WearAuthn are you using? 0.9.9

fmeum commented 4 years ago

Thanks for the report!

I suspect that this is an issue with the underlying Bluetooth stack. On watches running Android 8, the required Bluetooth API is not officially available, but can be made to work reasonably well via a private API. It does have some limitations though and the observed behavior could very well be one of those.

Could you maybe try out WearMouse and report back whether you are encountering a similar issue with it? If yes, then this is most likely an unfixable annoyance with Android 8 and I will think about a workaround. If WearMouse doesn't have the same issue it would seem likely that this is actually a bug in WearAuthn.

fmeum commented 4 years ago

The most recent version 0.9.16 includes a change to the Bluetooth backend that may resolve this issue. It was also theoretically present in WearMouse, but much harder to trigger there.

Please give the new version a try when you have the time and let me know whether it resolves the issue for you.