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
At the moment, there is no way to know if a read or a write procedure have failed (see: ARMmbed/ble#181).
Nonetheless there is a way to know if those procedures succeed. If a read procedure succeed, then the client should call all callbacks previously registered by onDataRead and if the write procedure succeed, callbacks registered by onDataWritten should be called.
Unfortunately, those callbacks are always called, even if the procedure fail.
This behavior is reproducible:
read:
CharacteristicReadWrite_test_4
CharacteristicReadWrite_test_15
write:
CharacteristicReadWrite_test_8
CharacteristicReadWrite_test_16
DescriptorReadWrite_test_09
DescriptorReadWrite_test_05
The text was updated successfully, but these errors were encountered:
At the moment, there is no way to know if a
read
or awrite
procedure have failed (see: ARMmbed/ble#181).Nonetheless there is a way to know if those procedures succeed. If a read procedure succeed, then the client should call all callbacks previously registered by
onDataRead
and if the write procedure succeed, callbacks registered byonDataWritten
should be called.Unfortunately, those callbacks are always called, even if the procedure fail.
This behavior is reproducible:
The text was updated successfully, but these errors were encountered: