Schwifty
f082eeadad
SaveConfig (0x60) causes the beacon MCU to reboot and save to flash. It never sends an ACK, so writeToCharAndWaitACK would wait for the 5s timeout, during which the beacon disconnects. The disconnect handler fires while writesCompleted is still false, causing a false "Unexpected disconnect: beacon timed out" error. Fix: fire-and-forget the SaveConfig write and return immediately. The BLE-level write (.withResponse) confirms delivery. writeConfig() returns before the disconnect callback runs, so writesCompleted gets set to true in time. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com> |
||
|---|---|---|
| .. | ||
| App | ||
| Assets.xcassets | ||
| en.lproj | ||
| Models | ||
| Provisioners | ||
| Services | ||
| Utils | ||
| Views | ||
| BeaconProvisioner.swift | ||
| Info.plist | ||
| payfrit-favicon-light-outlines.svg | ||
