fix: per-write timeouts + reduced inter-write delay #10

Merged

schwifty merged 1 commit from schwifty/per-write-timeout-and-mtu into main

2026-03-22 02:17:19 +00:00

Author	SHA1	Message	Date
Schwifty	91669515bd	fix: add per-write timeouts and reduce inter-write delay to match Android The iOS provisioner had no per-write timeout — if a BLE write callback never came back, the operation hung until the 30s global timeout, by which point the connection was likely dead. Android uses a 5-second per-write timeout with withTimeoutOrNull(5000L). Changes: - Add 5-second per-write timeout with retry (1 retry per command) - On timeout: retry once, skip if non-fatal (steps 1-6), or fail - SaveConfig timeout treated as success (beacon reboots = no callback) - Reduce inter-write delay from 200ms to 150ms (Android uses 100ms) - Log negotiated MTU on connect to diagnose packet size issues - Cancel write timeout on cleanup/succeed/fail to prevent stale timers Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>	2026-03-22 02:14:32 +00:00

Author

SHA1

Message

Date

Schwifty

91669515bd

fix: add per-write timeouts and reduce inter-write delay to match Android

The iOS provisioner had no per-write timeout — if a BLE write callback
never came back, the operation hung until the 30s global timeout, by
which point the connection was likely dead. Android uses a 5-second
per-write timeout with withTimeoutOrNull(5000L).

Changes:
- Add 5-second per-write timeout with retry (1 retry per command)
- On timeout: retry once, skip if non-fatal (steps 1-6), or fail
- SaveConfig timeout treated as success (beacon reboots = no callback)
- Reduce inter-write delay from 200ms to 150ms (Android uses 100ms)
- Log negotiated MTU on connect to diagnose packet size issues
- Cancel write timeout on cleanup/succeed/fail to prevent stale timers

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

2026-03-22 02:14:32 +00:00