succeed() was calling disconnectPeripheral() before completion(), so the disconnect delegate fired while writesCompleted was still false — causing the "Unexpected disconnect" error log even on successful provisions. Swapped order: signal completion first, then disconnect. Also removed the redundant provisioner.disconnect() in ScanView since succeed() already handles it. 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 | ||