Schwifty f0fdb04e0e fix: restore FFF0 fallback and add 'payfrit' name detection in BLE scan ... The CP-28-only refactor accidentally over-filtered the BLE scan: 1. FFF0 service detection was gated on name patterns — CP-28 beacons advertising FFF0 with non-matching names (e.g. already provisioned as "Payfrit") were silently filtered out. Restored unconditional FFF0 → dxsmart mapping (matching old behavior). 2. Already-provisioned beacons broadcast with name "Payfrit" (set by old SDK cmd 0x43), but that name wasn't in the detection patterns. Added "payfrit" to the name check. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>		2026-03-23 03:11:46 +00:00
..
APIClient.swift	fix: three provisioning bugs causing beacon write failures	2026-03-23 02:29:16 +00:00
APIConfig.swift	feat: complete rebuild of PayfritBeacon iOS from scratch	2026-03-22 17:13:36 +00:00
BLEManager.swift	fix: restore FFF0 fallback and add 'payfrit' name detection in BLE scan	2026-03-23 03:11:46 +00:00
ProvisionLog.swift	fix: connection callback bug + add provisioning diagnostics	2026-03-22 23:12:06 +00:00
SecureStorage.swift	feat: complete rebuild of PayfritBeacon iOS from scratch	2026-03-22 17:13:36 +00:00