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
A platform exception happens due to too many receivers because of which our app starts to have audio issues (audio stops playing) We connect to a ble device and play audio. We aren't sure how these may be connected.
To Reproduce
Steps to reproduce the behavior:
Connect to a single device using using connectTo()
Read and write to a single non-protected characteristic
Disconnect and reconnect with the bluetooth device a few times
Exception: PlatformException(ObserveBleStatusFailure, Too many receivers, total of 1000, registered for pid: 6144, callerPackage: tech.netrin.enhance, null, null)
Expected behavior
We do call disconnect correctly and retry only after the connection timeout, so we aren't sure why this particular issue happens
Smartphone / tablet
This happens on Android devices (Android 11, Android 12, Android 13)
Additional context
We aren't able to re-produce this issue consistently. We observe that this happens when the app remains open for a few days without getting force closed. It seems like there is some kind of a leak
The text was updated successfully, but these errors were encountered:
Describe the bug
A platform exception happens due to too many receivers because of which our app starts to have audio issues (audio stops playing) We connect to a ble device and play audio. We aren't sure how these may be connected.
To Reproduce
Steps to reproduce the behavior:
connectTo()
Exception: PlatformException(ObserveBleStatusFailure, Too many receivers, total of 1000, registered for pid: 6144, callerPackage: tech.netrin.enhance, null, null)
Expected behavior
We do call disconnect correctly and retry only after the connection timeout, so we aren't sure why this particular issue happens
Smartphone / tablet
Peripheral device
Additional context
We aren't able to re-produce this issue consistently. We observe that this happens when the app remains open for a few days without getting force closed. It seems like there is some kind of a leak
The text was updated successfully, but these errors were encountered: