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

write without response assumes we can process the write immediately #250

Open
markohara opened this issue Feb 13, 2021 · 0 comments · May be fixed by #251
Open

write without response assumes we can process the write immediately #250

markohara opened this issue Feb 13, 2021 · 0 comments · May be fixed by #251

Comments

@markohara
Copy link

Summary:
If we enqueue a large number of .withoutResponse writes, eventually we reach a point where the Core Bluetooth write buffer can no longer take any more writes, resulting in a crash. Apple has added the peripheralIsReady delegate method to allow you to ensure another write can happen successfully when writing without response.

in WriteCharacteristic instead of automatically processing requests of this type, we should use peripheralIsReady to inform us that we are able to process this write.

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

Successfully merging a pull request may close this issue.

1 participant