Not registering input

[VNRARA]

The top connect button (with my bluetooth device name) doesn't work when already connected to a phone. It doesn't give an error msg or force connecting to a different device.

[fmeum]

Could you maybe take a screenshot or photo of the situation in which you can't connect? This will help me get to the bottom of this. WearAuthn unfortunately can't be used with phones via Bluetooth, so it shouldn't connect to one in the first place.

[VNRARA]

I mean when it's connected to my phone to accept phone calls it hangs up the Bluetooth connection so I can't use the app to connect to a laptop. I have to disable Bluetooth on the watch and re-enable for it to work;.

[fmeum]

I see, I think I understand the problem now. Could you tell me which watch model you are using (Settings ->System -> About) and which version of Android you have installed (Settings ->System -> About -> Versions)?

Ideally, you would try whether you can reproduce the same issue with the app WearMouse, which shares most of the underlying Bluetooth stack with WearAuthn. If you can reproduce the issue there, it is extremely likely that this is a problem with Wear OS itself and therefore can't be fixed.

[VNRARA]

TicWatch Pro (WF12096) on WearOS 2.14 H. Wearmouse isn't having this issue. But it seems to be using the system ui to prompt and dialog for connecting a device Bluetooth ? Haven't really payed much attention to the issue, tho.

[fmeum]

WearMouse only does a very good job at mimicking the system UI, but doesn't use it.

Does the problem always manifest itself with WearAuthn after you have taken a phone call on the watch? And it does not appear with WearMouse?

I will look into the difference between the two apps and let you know when I find anything.

[VNRARA]

It seems not to do it. But I haven't really used it that much anymore. Google's IP based SSO is only for business/suite owners and risking a password hack because of convenience isn't worth it. So as my second layer of auth I usually use the Google Prompt.

[VNRARA]

It stopped attaching altogether... It says attaching but it never does. I reset my bluetooth device on my pc and reset my watch and it works like before.

[fmeum]

Sorry for the late reply, but I have unfortunately been unable to make any progress on tracking down this bug.

It stopped attaching altogether... It says attaching but it never does. I reset my bluetooth device on my pc and reset my watch and it works like before.

This sometimes happens when switching between different apps emulating a HID device (such as WearMouse and WearAuthn) and can usually be resolved by repairing with the target device. Unfortunately, this also seems to be an inherent limitation of the Wear OS bluetooth stack.

[fmeum]

I have made some changes to the Bluetooth backend that may resolve this issue. If this should not resolve the issue for you, please reopen.

[VNRARA]

I found out that it may be related to some Wear devices being able to connect as headset and disabling the "Play phone audio on watch" and turning my Phone bluetooth off made it connect instantly today after a while of reconnecting and removing device from Windows Bluetooth devices.

[fmeum]

It's quite possible that Windows does not like to see HID devices that double as headsets, so this might very well have been the issue. Thanks for the info!

[VNRARA]

@fmeum

I found out with my new watch that the watches don't like being connected via BLE (to the phone) and at the same time do WearAuthn stuff.

Windows does not like to see HID devices that double as headsets

Is there any other OS/devices that uses bluetooth with wearAuthn besides Windows? Should this work with linux?

[VNRARA]

I think the problem might have been #22 all along