Hello,
I recently started using noble-uwp in place of noble in my electron app. My Windows 10 machine is at update 1709 - Fall creators update. I am seeing two problems.
First of all I do not see the scan UUID being used as a filter. Currently, I removed all the filters and started looking for all the devices.
Second problem is more critical. When I trigger "connect" to my device, no callback is triggered. In the bindings.js file, I could trace the flow up to the call to fromBluetoothAddressAsync. Neither did the promise resolve, nor was it rejected.
I normally do keep the scan running periodically. I also tried to stop scan forever before triggering the connection request. This did not result in any change in behavior.
Is this a known issue with Windows/ noble-uwp or can this issue be seen due to any mistakes in the setup?
Hello, I recently started using noble-uwp in place of noble in my electron app. My Windows 10 machine is at update 1709 - Fall creators update. I am seeing two problems.
First of all I do not see the scan UUID being used as a filter. Currently, I removed all the filters and started looking for all the devices.
Second problem is more critical. When I trigger "connect" to my device, no callback is triggered. In the bindings.js file, I could trace the flow up to the call to fromBluetoothAddressAsync. Neither did the promise resolve, nor was it rejected.
I normally do keep the scan running periodically. I also tried to stop scan forever before triggering the connection request. This did not result in any change in behavior.
Is this a known issue with Windows/ noble-uwp or can this issue be seen due to any mistakes in the setup?
Thanks