-
Notifications
You must be signed in to change notification settings - Fork 609
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
Android stopNotification causes errors if done too quickly #937
Comments
Hi @sam-higgs Are you able to provide any logs with what the reported errors are? Generally speaking, you should wait for the callbacks to complete (or await the Out of interest, what's the use-case here that's requiring you to stop and then start the notifications in quick succession? |
Hey @peitschie,
If the user restarts the app, then the app can connect to the given UUID and Notification ID. I've also tried to add a timeout with 150ms before calling Do you have any ideas why this behaves that strange? Thanks for your great work and your awesome support! |
Hi @graphefruit That error message is from iOS:
Are you able to split this out into a separate issue for discussion? |
Upon calling
.stopNotification()
an error occurs when trying to do any other ble action too quickly afterwards e.g..startNotification()
or.read()
Has anyone else experienced this? Adding a delay of over 100ms seems to be a workaround.
The text was updated successfully, but these errors were encountered: