-
-
Notifications
You must be signed in to change notification settings - Fork 144
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
prevent re-use of dropped peripheral #378
Labels
bug
Something isn't working
corebluetooth (macos/ios)
Issues related to the MacOS/iOS CoreBluetooth impl
Comments
Besides, I will give a look on how we can prevent this from happening and I will you about it. |
This is definitely a bug. is_connected() should return pretty much immediately, so there's something in our background executor that's having a problem. |
qdot
added
bug
Something isn't working
corebluetooth (macos/ios)
Issues related to the MacOS/iOS CoreBluetooth impl
labels
Mar 28, 2024
I agree on the bug thing.. here some feedback on the possible issue:
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
bug
Something isn't working
corebluetooth (macos/ios)
Issues related to the MacOS/iOS CoreBluetooth impl
Hello,
I hesitate filling a feature request or a bug. But since it happens with erroneous code I prefer to see it as a FR.
On macOS (not tested on other platforms), the following sequence goes in an infinite waiting loop:
I am fully aware that step 4 is wrong, still it should not await indefinitely (at least panic)
The feature request is:
"could we add a
timeout()
on theconnect(), disconnect() and is_connected()
functions or use reference counting at some point."I hope I make a clear statement.
jC
ps/ as code usually says more:
The text was updated successfully, but these errors were encountered: