Schwifty 4bf4435feb fix: resolve false disconnect error at end of provisioning ... 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>		2026-03-23 03:47:27 +00:00
..
BusinessListView.swift	fix: back button bounces user right back into selected business	2026-03-22 21:47:45 +00:00
DevBanner.swift	fix: resolve ambiguous color references by removing ShapeStyle extension	2026-03-22 19:40:51 +00:00
LoginView.swift	fix: resolve ambiguous color references by removing ShapeStyle extension	2026-03-22 19:40:51 +00:00
QRScannerView.swift	fix: QR scanner crash — missing NSCameraUsageDescription in Info.plist	2026-03-22 21:45:10 +00:00
RootView.swift	feat: complete rebuild of PayfritBeacon iOS from scratch	2026-03-22 17:13:36 +00:00
ScanView.swift	fix: resolve false disconnect error at end of provisioning	2026-03-23 03:47:27 +00:00