Payfrit Beacon iOS
Schwifty
c62dace54d
The previous fix only caught the disconnect callback path. But CoreBluetooth can also fire didWriteValueFor with an error when the beacon reboots mid-ATT response. This was hitting fail() at the isNonFatalCommand check instead of being treated as success. Now handles both paths: 1. didDisconnectPeripheral with state=.writing at last command → succeed() 2. didWriteValueFor error for SaveConfig (last command) → succeed() Also added detailed state/index logging to disconnect handler for diagnostics. |
||
|---|---|---|
| _backup | ||
| PayfritBeacon | ||
| PayfritBeacon.xcodeproj | ||
| .gitignore | ||
| ExportOptions.plist | ||
| ExportOptionsLocal.plist | ||
| Podfile | ||
| Podfile.lock | ||
| QA_WALKTHROUGH.md | ||