payfrit-beacon-ios/PayfritBeacon/Provisioners
Schwifty 640bc32f92 fix: use .withoutResponse for SaveConfig to prevent silent write drop
The beacon reboots instantly on SaveConfig (0x60). Using .withResponse
meant CoreBluetooth expected a GATT ACK that never arrived, potentially
causing the write to be silently dropped — leaving the config unsaved
and the beacon LED still flashing after provisioning.

Switching to .withoutResponse fires the bytes directly into the BLE
radio buffer without requiring a round-trip ACK. The beacon firmware
processes the save command from its buffer before rebooting.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
2026-03-23 03:57:56 +00:00
..
DXSmartProvisioner.swift fix: use .withoutResponse for SaveConfig to prevent silent write drop 2026-03-23 03:57:56 +00:00
ProvisionerProtocol.swift refactor: strip all non-CP-28 beacon code 2026-03-23 03:04:07 +00:00
ProvisionError.swift feat: complete rebuild of PayfritBeacon iOS from scratch 2026-03-22 17:13:36 +00:00