Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

GattClient write and read procedures always seems to succeed even if they fail. #123

Open
pan- opened this issue Mar 18, 2016 · 1 comment

Comments

@pan-
Copy link
Member

pan- commented Mar 18, 2016

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
@pan- pan- added the bug label Mar 18, 2016
@ciarmcom
Copy link
Member

ARM Internal Ref: IOTSFW-2379

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants