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
I may have misunderstood or overlooked that upstream the Channel is closed, and thus: this launched Coroutine should terminate when the upstream Channel closes (which is triggered via a disconnect event in the Android Callback).
tl;dr this may not be a bug (it might not leak) at all.
Confirmed that this is not a bug. In #193, the completion of the flow identified in this issue is relied on for observation handling. Testing of SNAPSHOTs produced from #193 confirmed that (as identified in #139 (comment)), the flow is terminated upon disconnected signal in Android's BluetoothGattCallback.
Characteristic changes are forwarded from the
Callback
to theObservers
vialaunchIn(scope)
but the Coroutine is never cancelled.kable/core/src/androidMain/kotlin/Peripheral.kt
Lines 175 to 178 in d9ff2ce
The text was updated successfully, but these errors were encountered: