Repository navigation
fix(web): serialize service discovery before pairing - #183
Conversation
|
Latest-head review: 862ad0f independently reviewed with no actionable findings after fixing a final-discovery cancellation race. Reviewer independently reran all 27 transport tests successfully. Prior full run passed lint, types and 647 tests, then failed only Expo Doctor on eight existing SDK patch mismatches. Full latest-head validation rerunning. Hardware testing remains blocked on user selection in the real Chrome Bluetooth picker; no successful pairing claimed. |
|
Latest head 862ad0f: version check, lint, TypeScript and all 648 tests across 73 suites pass. Independent latest-head review clear. Expo Doctor still reports the same eight pre-existing SDK patch mismatches. CI is pending, so green-CI acceptance is not met. No merge performed. |
|
Hardware retest correction: the Metro process on port 8091 was serving stale code even after browser reload. Verified the served bundle lacked both new diagnostic labels and sequential discovery. Restarted that exact Metro process with a cleared cache, then verified the served bundle contains both. Previous browser retry therefore did not exercise this PR. Real pairing remains unverified. |
|
Head 90c14c7 independently reviewed with no actionable findings. Reviewer reran all 61 focused transport/connection tests successfully. Hardware retry opened against a verified current served bundle, still awaiting user device selection. Full npm validation ongoing. No merge. |
|
Full validation on 90c14c7: version check, lint, TypeScript and 654 tests in 73 suites pass. Expo Doctor passes 20/21 checks and fails the existing eight SDK patch mismatches. Independent review clear. Real-PC pairing still pending; no merge. |
chore(deps): update Expo SDK 57 patches
fix(web): resolve web stack review findings
|
Summary
Closes #182
Stacked on #181. Discover characteristics sequentially, request read-response only for read-v1, and add fixed-vocabulary lookup diagnostics. Real testing then showed primary-service rediscovery fails after the discovery connection is closed. Explicitly retain the selected completed web discovery connection and reuse its live service for pairing preparation. Reread and validate desktop identity; keep normal disconnect and cancellation cleanup. Native transports keep their existing preparation path.
Validation
No protocol, permission, native configuration, dependency or version changes. Do not merge until hardware evidence and green CI are complete.