I am working in an IoT like setup where multiple devices are advertising over BLE.
An electron app is used to connect to the elements using noble-uwp. (No Pairing is done.)
Some app crashes are seen without any prompt.
The crashes become more frequent as the number of devices increases.
The logs of my application show that all crashes happened immediately after a call to startScanning() is made.
I could not find any specific steps to reproduce these crashes.
Is there any known issue around this?
Is there a limit to the number of BLE advertising devices that noble-uwp can handle?
OS: Windows 10 Pro
Version: 1809
OS Build: 17763.253
I get a crash after scanning for a number of hours (doing nothing with results, just scanning). There is some kind of bug in the nodert code I believe.
I am working in an IoT like setup where multiple devices are advertising over BLE. An electron app is used to connect to the elements using noble-uwp. (No Pairing is done.) Some app crashes are seen without any prompt. The crashes become more frequent as the number of devices increases.
The logs of my application show that all crashes happened immediately after a call to startScanning() is made.
I could not find any specific steps to reproduce these crashes.
Is there any known issue around this? Is there a limit to the number of BLE advertising devices that noble-uwp can handle?
OS: Windows 10 Pro Version: 1809 OS Build: 17763.253