-
Notifications
You must be signed in to change notification settings - Fork 45
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
discoverAllServicesAndCharacteristics() doesn't always call callback. #50
Comments
This seems to just be an issue when building with an electron app. I can't reproduce this on my desktop using Node 6.11.5 |
Turns out, if the device is paired then the callback is never called. If the device is not paired then the callback is called. |
It looks like it might be because initially
|
@NAllred91 : does noble itself handle disconnects in the middle of discovering services? |
When I make calls to
peripheral.discoverAllServicesAndCharacteristics([callback])
the callback is not always called. It seems that if I put the call todiscoverAllServicesAndCharacteristics
in a setTimeout I can get the callback to be called more frequently, but the callback is still mostly never called.The text was updated successfully, but these errors were encountered: