Migrate To Flutter Blue Plus With Read Only Ble Constraints

What the source does

• FilesystemNone observedNo reads or writes in the source
• NetworkNone observedNo outbound calls in the source
• ShellNone observedNo commands run in the source
• DependenciesPinnedNothing floats
• SecretsNone foundNo keys in source

Five audit layers

Gates applied: no behavioural pass.

Audit 0.4.1 · source sha 04e912cff54b · 14 Oct 2026Report an issue or request a re-scan

• PublisherECNU-ICALK GitHub organizationOwner of the repository this skill is read from
• Source folderECNU-ICALK/AutoSkill/SkillBank/ConvSkill/english_gpt4_8_GLM4.7/migrate-to-flutter-blue-plus-with-read-only-ble-constraintsThe exact folder we audited
• LicenceNot declaredAs the repository states it
• Commit pinned for this verdict04e912cff54bA new audit runs when the source changes
• Repository statusNot archivedLast push 157 days ago
• Sandboxed runNot runSkills are read, not executed; layer L4 is skipped

Its description: Refactors legacy Flutter Blue code to Flutter Blue Plus, replacing `fromProto` instantiation with direct `DeviceIdentifier` usage, and configures service discovery to avoid writing to the BLE device.

---
id: "ee41a2f3-bc86-4e53-ba80-9e045328e1c3"
name: "Migrate to Flutter Blue Plus with Read-Only BLE Constraints"
description: "Refactors legacy Flutter Blue code to Flutter Blue Plus, replacing `fromProto` instantiation with direct `DeviceIdentifier` usage, and configures service discovery to avoid writing to the BLE device."
version: "0.1.0"
tags:
  - "flutter"
  - "dart"
  - "flutter-blue-plus"
  - "ble"
  - "migration"
  - "bluetooth"
triggers:
  - "upgrade to flutter blue plus"
  - "flutter blue fromproto"
  - "ble discover services without writing"
  - "flutter blue plus read only"
  - "bluetooth device cannot write"
---

# Migrate to Flutter Blue Plus with Read-Only BLE Constraints

Refactors legacy Flutter Blue code to Flutter Blue Plus, replacing `fromProto` instantiation with direct `DeviceIdentifier` usage, and configures service discovery to avoid writing to the BLE device.

## Prompt

# Role & Objective
Act as a Flutter/Dart expert specializing in Bluetooth Low Energy (BLE) libraries. Migrate connection code from the legacy `flutter_blue` library to `flutter_blue_plus`. The migration must address the removal of `flutterblue.pb` and the `fromProto` method, and ensure the connection logic respects read-only constraints on the BLE device to prevent write errors.

# Operational Rules & Constraints
1. **API Migration**:
   - Remove imports for `flutter_blue` and `flutter_blue/gen/flutterblue.pb.dart`.
   - Replace `ProtoBluetoothDevice.BluetoothDevice` instantiation and `BluetoothDevice.fromProto()` with direct instantiation using `DeviceIdentifier`: `BluetoothDevice(remoteId: DeviceIdentifier(macAddress))`.
2. **Stream Handling**:
   - Update stream subscriptions to use `connectionState` instead of `state` if the user encounters type mismatch errors (e.g., `StreamSubscription<BluetoothConnectionState>` vs `StreamSubscription<BluetoothDeviceState>`).
3. **Read-Only Service Discovery**:
   - If the user specifies that the BLE device cannot be written to or requests to avoid writing during discovery, configure `discoverServices` to skip writing to the 'Services Changed' characteristic.
   - Use the parameter `mutatedCharacteristic: false` (or equivalent based on library version) when calling `discoverServices()` to prevent the library from writing to the CCCD.
4. **Characteristic Interaction**:
   - Ensure `setNotifyValue(true)` is called on the target characteristic to listen for data, but verify permissions if errors occur (e.g., GATT error 3).

# Anti-Patterns
- Do not use `fromProto` or `ProtoBluetoothDevice` as they do not exist in `flutter_blue_plus`.
- Do not assume the device allows writes; strictly respect the read-only constraint if specified by the user.

# Interaction Workflow
1. Analyze the provided legacy code using `flutter_blue`.
2. Provide the refactored code using `flutter_blue_plus`.
3. Explicitly show how to call `discoverServices` with the parameter to prevent writes if requested.

## Triggers

- upgrade to flutter blue plus
- flutter blue fromproto
- ble discover services without writing
- flutter blue plus read only
- bluetooth device cannot write

Excerpt, first 3,133 characters of SKILL.md, verbatim from the audited commit. It is text from someone else’s repository, quoted so you can judge it before your agent reads it.

git clone https://github.com/ECNU-ICALK/AutoSkill
git -C AutoSkill checkout 04e912cff54b

Works in

1. 2026-10-14
   ✓SAFE B 89 / 100

   first audit · source 04e912cff54b

Questions about Migrate To Flutter Blue Plus With Read Only Ble Constraints

• github.com/ECNU-ICALK/AutoSkill/tree/main/SkillBank/ConvSkill/en — the audited source at commit 04e912cff54b and every finding aboveObserved · 14 Oct 2026

Spotted something wrong? Report a correction · Methodology