Apple: correlate concurrent BLE callbacks in FIFO order - #305
Merged
Merged
Conversation
rohitsangwan01
approved these changes
Sep 8, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Makes
QueueType.nonesafe for concurrent Apple operations that share the same CoreBluetooth callback identity. Each callback now completes only the oldest matching pending operation instead of every match.Covers characteristic reads, descriptor reads/writes, notification state changes, and RSSI reads. Write-with-response was already FIFO; write-without-response backpressure is handled separately by #300.
This unblocks the non-Android
QueueType.autobehavior in #304 without adding Dart-side serialization.Verification
flutter test(106 tests passed)flutter build macos --debug