You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
When I have a peripheral that disconnects and I later call connect on it successfully the stream returned by notifications() never produces an event.
Expected behavior
I can re-use a peripheral after it has reconnected
Actual behavior
The peripheral stops producing notifications after the first diconnect
Additional context
The log message Event receiver died, breaking out of corebluetooth device loop appears which seems to show the event handler for my peripheral dying. I am currently working around this be rescanning and getting a fresh version of the peripheral from Central.
The text was updated successfully, but these errors were encountered:
Yes, the TX/RX channel is initialized in Peripheral::new() and cleaned up in Drop.
When disconnected, the peripheral is removed from the manager's HashMap, triggering its Drop implementation.
Describe the bug
When I have a peripheral that disconnects and I later call connect on it successfully the stream returned by notifications() never produces an event.
Expected behavior
I can re-use a peripheral after it has reconnected
Actual behavior
The peripheral stops producing notifications after the first diconnect
Additional context
The log message
Event receiver died, breaking out of corebluetooth device loop
appears which seems to show the event handler for my peripheral dying. I am currently working around this be rescanning and getting a fresh version of the peripheral from Central.The text was updated successfully, but these errors were encountered: