-
Notifications
You must be signed in to change notification settings - Fork 372
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
discoverServices doesn't emit any result #309
Comments
Probably related to #287 |
@vladiulianbogdan can you confirm that this issue is fixed in version 5.2.0? |
Yes. I can't reproduce the problem anymore. |
Can we close this now? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
The problem is that in our code we have multiple places where we discover services. The peripheral that the app connects to is also sometimes emitting a service change indication (I don't know if it is relevant).
What I've seen is that sometimes the
discoverServices
does not emit anything. I've deep dived into the code and the problem is aroundremainingServicesDiscoveryRequest
. Sometimes the value inremainingServicesDiscoveryRequest
remains unbalanced (it has value 1).I will keep you posted if I discover what is causing the variable to be unbalanced.
Expected behavior
discoverServices
should always emit the discovered services.Environment:
The text was updated successfully, but these errors were encountered: