ble_keeper 0.1.0-beta.1

ble_keeper: ^0.1.0-beta.1 copied to clipboard

First public pre-release.

Status: Android is verified on real hardware (Samsung Galaxy A53 5G, Android 16, debug and release builds; see "Verified on" in the README). iOS builds and passes its unit tests on the simulator but is not yet verified on a real iPhone; 0.1.0 follows after iOS hardware testing.

• Keeps BLE peripherals connected from native code that does not depend on the Flutter UI: an Android foreground service (connectedDevice) and an iOS CBCentralManager with Core Bluetooth state restoration.
• Automatic reconnect: Android autoConnect with status 133 backoff, iOS pending connect. Reconnects after Bluetooth is turned back on.
• Restarts after Android process death (sticky service), reboot and app update (BOOT_COMPLETED, MY_PACKAGE_REPLACED), and after iOS system termination via state restoration.
• Sealed KeeperEvent stream: Connected, Disconnected, Reconnecting, Data, RestoredAfterKill, Blocked.
• Blocked reasons for what the OS does not allow: Bluetooth off, missing permission, Android background foreground-service start, user force-quit (Android exact, iOS best effort), app misconfiguration.
• Background handler that runs in a headless engine when no UI is running.
• Notifications/indications, read, write with and without response.
• Rotating event log (2 x 1 MB) with export; pseudonymised device IDs and no payloads in release builds; Data events summarised per minute.

Fixed during hardware testing (Android 16):

• BOOT_COMPLETED delivered when a force-stopped app is opened again is no longer treated as a reboot (no misleading RestoredAfterKill).
• A force-stop shortly after an app update is reported as userForceQuit.
• The event log writes the open Data summary before each state event.