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.

Sign up for GitHub

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

Jump to bottom

Document notification retrying #13

Open
Franzaine opened this issue Nov 21, 2018 · 1 comment
Open

Document notification retrying #13

Franzaine opened this issue Nov 21, 2018 · 1 comment
Labels
bug

Comments

@Franzaine
Copy link
Member

When a peripheral is notifying the client that the APDU responses are ready it needs to retry the notification until it is received. Certain phones seem to miss the notification and then the transaction fails. A sensible retry mechanism seems to be retry every second in total 5 times.
@Franzaine Franzaine added the bug label Nov 21, 2018
@martinpaljak
Copy link
Member

Things to consider:

  • use indications (with ACK) rather than notifications (no ACK) for increased reliability
  • define a recommended retry mechanism for a BLE server implementation, until the response is read (fully)

@martinpaljak martinpaljak mentioned this issue Dec 12, 2018
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@martinpaljak @Franzaine