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
Currently when the user will unsubscribe from .setupNotification()/.setupIndication() the notification/indication is teardown but the (possibly) emitted Observable<byte[]> does not complete.
Similarly when the RxBleConnection terminates the emitted Observable<byte[]> does not throw an error.
Library version
1.3.1
Steps to reproduce actual result
1. Connect to a device
2. Setup notification (or indication)
3. Wait for it being setup
4. Get emitted Observable<byte[]>
5. Un-subscribe from the .setup*()
6. Observe that emitted Observable<byte[]> has not completed
dariuszseweryn
changed the title
Observable emitted from RxBleConnection.setupNotification()/RxBleConnection.setupIndication() does not comObservable emitted from RxBleConnection.setupNotification()/RxBleConnection.setupIndication() does not complete
Jun 23, 2017
dariuszseweryn
changed the title
Observable emitted from RxBleConnection.setupNotification()/RxBleConnection.setupIndication() does not completeObservable emitted from RxBleConnection.setupNotification()/RxBleConnection.setupIndication() does not terminate
Jun 23, 2017
dariuszseweryn
changed the title
Observable emitted from RxBleConnection.setupNotification()/RxBleConnection.setupIndication() does not terminateObservable emitted from RxBleConnection.setupNotification()/RxBleConnection.setupIndication() does not complete
Jun 26, 2017
Summary
Currently when the user will unsubscribe from
.setupNotification()
/.setupIndication()
the notification/indication is teardown but the (possibly) emittedObservable<byte[]>
does not complete.Similarly when the
RxBleConnection
terminates the emittedObservable<byte[]>
does not throw an error.Library version
1.3.1
Steps to reproduce actual result
1. Connect to a device
2. Setup notification (or indication)
3. Wait for it being setup
4. Get emitted
Observable<byte[]>
5. Un-subscribe from the
.setup*()
6. Observe that emitted
Observable<byte[]>
has not completedMinimum code snippet reproducing the issue
Actual result
SHOULD COMPLETE
is not logged after 15 seconds from the notification setup.Expected result
SHOULD COMPLETE
should be logged after 15 seconds from the notification setup.The text was updated successfully, but these errors were encountered: