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
{{ message }}
This repository has been archived by the owner on Jun 19, 2024. It is now read-only.
For each instance of the IDevice on Android side there is an event subscription. This is done using a Lambda. It is preferred to hook this up to an actual delegate for the purpose of event unsubscription. In the constructor of the Device the DeviceConnected event is being subscribed to. In case of disconnect, this event is not cleared. So the next time the same device is discovered and connected to, previous event gets the first notification. The GATT instance in the initial IDevice is null so it throws an exception.
The text was updated successfully, but these errors were encountered:
Thanks Steven. Just one more issue I forgot to mention on the issue I created. Upon triggering the connection made event, the returned device is added to the list of connect devices. However it is never removed from the list once disconnected. I don't use that list since my app will only talk to one designated BLE device at a time. It would be nice to fix in case someone is planning on a multi-connection session.
For each instance of the IDevice on Android side there is an event subscription. This is done using a Lambda. It is preferred to hook this up to an actual delegate for the purpose of event unsubscription. In the constructor of the Device the DeviceConnected event is being subscribed to. In case of disconnect, this event is not cleared. So the next time the same device is discovered and connected to, previous event gets the first notification. The GATT instance in the initial IDevice is null so it throws an exception.
The text was updated successfully, but these errors were encountered: