Suppress connecting to device on all interactions on android.#842
Open
rolandmosimann wants to merge 2 commits into
Open
Conversation
|
Any updates on this? |
Author
|
Hey @Taym95, any chance to get this in? |
rolandmosimann
force-pushed
the
android_error_when_interacting_with_not_connected_device
branch
from
68b4e06 to
594d04d
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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