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

Handling of failure during GattClient operations is missing #137

Open
pan- opened this issue Dec 7, 2015 · 2 comments
Open

Handling of failure during GattClient operations is missing #137

pan- opened this issue Dec 7, 2015 · 2 comments

Comments

@pan-
Copy link
Member

pan- commented Dec 7, 2015

The current GattClient API does not provide any way to catch a failure during a GattClient procedure. The following procedure miss this feature:

  • Primary service discovery
  • Characteristic discovery
  • read attribute value
  • write attribute value

With the current implementation, if something fail during one of this procedure, the client will never now that the procedure has ended and will not be able to react to such failures.

@rgrover
Copy link
Contributor

rgrover commented Dec 7, 2015

thanks for pointing out this gap in our APIs. We should allow registering callbacks to discover erorrs.

@ciarmcom
Copy link
Member

ciarmcom commented Dec 7, 2015

ARM Internal Ref: IOTSFW-1376

@pan- pan- added the bug label Apr 22, 2016
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

3 participants