airoc_connect_flutter

Releases

1. ▸▾0.0.821 Aug 2026

   Lowered Minimum SDK Requirements

   Lowered Minimum SDK Requirements

   • Minimum Dart SDK lowered from 3.8.1 to 3.2.0
   • Minimum Flutter lowered from 3.32.7 to 3.16.0
   • Downgraded crypto to ^3.0.3 and flutter_lints to ^4.0.0, the last versions compatible with Dart SDK 3.2

   ---

   Open source →
2. ▸▾0.0.74 Aug 2026

   OTA Workflow Redesign & Connection Stability

   OTA Workflow Redesign & Connection Stability

   Platform Support: Android, iOS, macOS

   New Features

   • Auto-Unpair After OTA - Once the upgrade completes, the device is automatically unpaired to clean up the pairing state: Android calls removeBond(), while iOS/macOS disconnect (CoreBluetooth exposes no programmatic unpair API).
   • Explicit Manual Pairing — Added "Pair Device" as Step 1 in the OTA workflow. Users must manually pair before proceeding to service discovery and upgrade. Paired state is visually indicated (Not Paired / Pairing… / Paired ✓).
   • 4-Step OTA Workflow — Expanded from 3 steps to 4 steps for clearer operation flow:
     • Step 1: Pair Device — Manually pair with the device
     • Step 2: Discover Services — Read device service UUIDs
     • Step 3: Select Firmware — Choose a firmware file
     • Step 4: Start OTA Upgrade — Begin the firmware update
   • Colorized Debug Logging — Terminal output now uses ANSI color coding: level-specific badges (blue=info, yellow=warning, red=error), green tags, gray timestamps, magenta TX / cyan RX hex dumps.
   • Characteristic Property Filtering — Service discovery dropdowns now only show characteristics that support both WRITE and NOTIFY capabilities.

   Bug Fixes

   • Fixed macOS Pairing "android-only" Error — Pairing and OTA no longer throw android-only on macOS/iOS. The example app previously called flutter_blue_plus Android-only APIs (createBond(), bondState) unconditionally on all platforms; these are now guarded behind Platform.isAndroid. On iOS/macOS (CoreBluetooth), which expose no programmatic pairing API, pairDevice() just connects and pairing is triggered implicitly by the OS when an encrypted characteristic is accessed; isDeviceBonded() / isBonded fall back to connection state. Android retains its explicit createBond() flow unchanged.
   • Fixed Repeated Pairing Prompts — Eliminated unnecessary disconnect/reconnect cycles throughout the OTA flow. A single continuous BLE connection is now maintained from pairing through OTA completion, matching iOS CoreBluetooth behavior.
   • Fixed "WRITE property not supported" Error — Transport layer now auto-detects whether the characteristic supports write or writeWithoutResponse and uses the correct write mode.
   • Fixed Multiple createBond() Calls — Removed auto-pairing logic from the transport layer. Pairing is now exclusively handled by the user-facing "Pair Device" step.

   Technical Improvements

   • Single Continuous Connection — FlutterBluePlusOtaTransport.connect() no longer forces disconnect/reconnect when the device is already connected. It reuses the existing connection to avoid bond re-negotiation.
   • Transport Write Detection — write() auto-falls back to writeWithoutResponse when the characteristic lacks WRITE property.
   • Characteristic Discovery — discover() logs all characteristic properties and selects the best match with both WRITE and NOTIFY capabilities.
   • Pairing State Management — Bond state is checked on OTA screen init to detect previously-paired devices.

   Notes

   • One Connection, One Pairing — Following the iOS CoreBluetooth model, the app now uses a single Bluetooth connection throughout the entire OTA session. Users should only see the pairing dialog once.

   ---