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
Upon connecting to a device, I have code that reads from its characteristics to determine the initial state of the UI. However, there exist two variants of the peripheral device and they differ by one characteristic, which is present in Variant A, but missing from Variant B.
At present, the app just goes ahead and reads them all. However, this approach results in all read operations on all of the characteristics failing when connected to a Variant B device. Is this how it is meant to work? I would expect only the read operation on the missing characteristic to fail.
The same error message is repeated for each of the read operations.
I do of course realize there are many ways to work around this issue, such as simply checking for the presence of the offending characteristic before reading from it. Nevertheless, I wanted to report this since the behavior I have observed doesn't make sense to me.
The text was updated successfully, but these errors were encountered:
dandan78
changed the title
Reading from non-existing characteristic causes all reads to fail
Reading from non-existent characteristic causes all reads to fail
Apr 26, 2019
Issue
Upon connecting to a device, I have code that reads from its characteristics to determine the initial state of the UI. However, there exist two variants of the peripheral device and they differ by one characteristic, which is present in Variant A, but missing from Variant B.
At present, the app just goes ahead and reads them all. However, this approach results in all read operations on all of the characteristics failing when connected to a Variant B device. Is this how it is meant to work? I would expect only the read operation on the missing characteristic to fail.
The error code is:
The same error message is repeated for each of the read operations.
I do of course realize there are many ways to work around this issue, such as simply checking for the presence of the offending characteristic before reading from it. Nevertheless, I wanted to report this since the behavior I have observed doesn't make sense to me.
The text was updated successfully, but these errors were encountered: