Characteristic value updates faster than asyncio schedule #240
Labels
Backend: Core Bluetooth
Issues and PRs relating to the Core Bluetooth backend
bug
Something isn't working
Milestone
Description
did_update_value_for_characteristic
will potentially be called after the characteristic value has changed again due to asyncio scheduling, causing the callback not be able to receive the old data.What I Did
This can be fixed by the pull request #241.
The text was updated successfully, but these errors were encountered: