Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Attempt to automatically connect to first device #6

Open
dancojocaru2000 opened this issue Mar 13, 2020 · 2 comments
Open

Attempt to automatically connect to first device #6

dancojocaru2000 opened this issue Mar 13, 2020 · 2 comments
Assignees
Labels
question Further information is requested

Comments

@dancojocaru2000
Copy link

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
Copy link
Owner

fmeum commented Mar 13, 2020

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 fmeum added the question Further information is requested label Apr 9, 2020
@fmeum
Copy link
Owner

fmeum commented Apr 19, 2020

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

2 participants