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

Adjust default timeout for read_gatt_char() with CoreBluetooth to 20s #928

Merged

Conversation

bdraco
Copy link
Contributor

@bdraco bdraco commented Aug 8, 2022

fixes #926

@dlech
Copy link
Collaborator

dlech commented Aug 12, 2022

I wonder if we should just remove this timeout altogether. The other backends don't have a timeout on this method.

@bdraco
Copy link
Contributor Author

bdraco commented Aug 12, 2022

That's a good thought. I'll do some testing to make sure I can't get it to hang

@bdraco
Copy link
Contributor Author

bdraco commented Aug 13, 2022

I took out the timeout , and attempted to do a homekit pairing. After a few times I got it to fail, and it is hanging forever without the timeout. I think we do need one, it is just a question of how low is too low.

@dlech dlech merged commit 8f7e43e into hbldh:develop Aug 26, 2022
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 this pull request may close these issues.

corebluetooth read_characteristic timeout is too low
2 participants