On Android, interacting with a disconnected device (e.g., writeCharacteristic/readCharacteristic) will establish a connection. However, this connection is not reflected in the plugin, as there are no propagated connection states. Therefore, the consumer cannot manage this unmonitored connection.
This behavior differs from the iOS implementation, where writeCharacteristic on a disconnected device results in an error.
This PR aligns the behavior of the Android implementation. Calling writeCharacteristic, readCharacteristic, etc., now results in an error.
On Android, interacting with a disconnected device (e.g., writeCharacteristic/readCharacteristic) will establish a connection. However, this connection is not reflected in the plugin, as there are no propagated connection states. Therefore, the consumer cannot manage this unmonitored connection.
This behavior differs from the iOS implementation, where writeCharacteristic on a disconnected device results in an error.
This PR aligns the behavior of the Android implementation. Calling writeCharacteristic, readCharacteristic, etc., now results in an error.
Detailed description in issue #589
solves: #589