flutter_midi_command_linux

• FIX: addVirtualDevice, removeVirtualDevice and setNetworkSessionEnabled return Future<void> instead of void. The platform call was previously discarded, so a failure such as PlatformException(AUDIOERROR, Error -2 while create MIDI virtual source) escaped as an unhandled asynchronous error that no try/catch around the call could see. Await them to handle failures. Existing calls that ignore the result keep compiling; custom MidiCommandPlatform implementations must widen these three overrides from void.
• FIX(ios): the system "Allow [app] to find devices on local networks" prompt no longer appears at app startup. The MIDI network session is created on the first setNetworkSessionEnabled(true) rather than at plugin init, so apps using only Bluetooth, USB or virtual MIDI never trigger it. Thanks to @aleksei-svezhevskii for the fix.
• Update federated package constraints to ^1.2.0.

• FIX(ble): retry a connection sequence whose link was torn down mid-handshake. universal_ble reports that as deviceDisconnected rather than a GATT status, so the retry shipped in 1.1.1 did not apply. Unlike a GATT status the code cannot arise from a peripheral that was never reachable, so it is honoured on every platform.
• Update federated package constraints to ^1.1.2.

• FIX(ble): retry the whole connection sequence through transient Android GATT_ERROR 133 failures, including failures during service discovery and notification subscription.
• FIX(ble): recognise operation-specific GATT failures from their details and preserve typed pairing-removal errors through connection-stage wrappers.
• FIX(ble): avoid resetting connection priority when it was never raised during a failed connection attempt.
• FIX(ble): handle stopScan failures when Bluetooth is switched off during a scan instead of surfacing an unhandled asynchronous error.
• Update federated package constraints to ^1.1.1.

• FIX(darwin): read every packet of a coalesced MIDIPacketList from the original list memory. Packets after the first were read from unrelated memory and anything over 256 bytes was truncated, affecting virtual devices; native devices already had a correct implementation. Virtual device timestamps now report nanoseconds, matching native devices.
• FIX(ble): serialize writes per device so two SysEx messages sent in quick succession cannot interleave their BLE packets. The peripheral reassembles a multi-packet SysEx statefully, so interleaving silently merged two messages into corruption — the failure mode behind bulk transfers that break partway through with no BLE-level error.
• FEAT: add MidiCommand.sendDataAwaitingDelivery, completing once the transport has written the data rather than queued it, so a bulk transfer can pace against the link rather than a fixed delay. Only the BLE transport observes delivery; platform-routed devices complete immediately, as with sendData.
• FEAT(ble): size BLE MIDI packets from the negotiated ATT MTU and request a low-latency connection interval, both on by default. Together these cut the number of BLE writes per SysEx and lower MIDI latency. Note that they do not speed up a request/response protocol whose cost is the peripheral's turnaround: measured against a GEWA piano, the write path was ~1.4 ms of a ~495 ms per-packet round trip. New UniversalBleMidiTransport flags useNegotiatedMtu and requestHighPerformanceConnection opt out. These apply on Android, Windows and Linux; on iOS and macOS a connected device is handed over to CoreMIDI, which then owns the write path.
• FEAT: add MidiCommand.onBleWriteFailure, reporting BLE writes the platform rejected. sendData is fire-and-forget, so this is the only signal that a packet was dropped. Bulk transfers that split a payload across many SysEx messages should treat any event as a corrupted transfer. Silent on Apple platforms for devices handed off to CoreMIDI, which has no equivalent per-write signal, so it complements rather than replaces device-level acknowledgements.
• FIX(ble): emit the BLE MIDI timestamp byte before the closing 0xF7 in every SysEx packet. It was omitted whenever the remaining body was exactly one byte short of the packet size.
• BREAKING (implementers only): MidiBleTransport gained onWriteFailure. Classes using implements MidiBleTransport must declare it; extends and all API consumers are unaffected. See the platform interface changelog.
• Update federated package constraints to ^1.1.0.

• FIX(ble): stop the opportunistic MTU request from stalling Android connections. It was issued from the connection callback and, because universal_ble runs every GATT command through one queue, it sat in front of service discovery long enough for Android to drop the link with GATT_ERROR 133 (surfaced as Unknown Error 133).
• FIX(ble): retry the BLE link once through a transient Android GATT_ERROR 133, and keep the device in the transport cache across that retry so received data still resolves to it.
• Update federated package constraints to ^1.0.9.

• FIX(darwin): report CoreMIDI destinations as inputPorts and sources as outputPorts so port direction matches Android and the public device-owned API contract (#164).
• FIX(android): disable Kotlin incremental compilation for the Android implementation so Windows builds do not fail when the app project and Pub cache are on different drives (#163).
• Update federated package constraints to ^1.0.8.

• FIX: export MidiPairingInfoRemovedException from package:flutter_midi_command/flutter_midi_command.dart.
• Update federated package constraints to ^1.0.7.

• FIX: a disconnect that races an in-flight connect no longer surfaces as an unhandled async error on PlatformDispatcher.onError (#160).
• FIX(ble): surface a typed MidiPairingInfoRemovedException when a peripheral has removed its pairing information (iOS CBErrorPeerRemovedPairingInformation), best-effort clearing the stale bond, instead of leaking a raw UniversalBleException.
• FIX(android): don't crash when a connected USB MIDI device is unplugged; ConnectedDevice teardown now survives the IOException: EPIPE from a removed device (#158).
• FIX(platform): don't clobber a device's transitional connecting/disconnecting state when listing devices (#159).

• FIX(ios): keep usable non-bonding BLE MIDI connections alive when no CoreMIDI counterpart appears, and perform bonded-device handoff as an optional atomic background upgrade (#157).
• FIX(ble): strip the BLE timestamp byte from received SysEx so SysEx round-trips on Android/Linux/Windows/Web (was corrupting the payload before 0xF7).
• FIX(ble): make scan start/stop idempotent to avoid redundant OS scan calls that can desync the Android LE scanner.

• FIX(ci): track pubspec_overrides.yaml so melos bootstrap works on clean checkouts.
• FIX(ble): hide registered devices until rediscovered.
• FIX(ble): remove stale BLE devices on disconnect.
• FIX: await BLE MIDI readiness in connectToDevice.
• FIX: bluetooth discovery with latest Universal_ble.
• FIX: suppress duplicate BLE packets after the CoreMIDI handoff.
• FIX: subscribe to BLE MIDI notifications on platforms without a pairing.
• FIX: update example app to iOS v14 minimum.
• FIX: port to win32 6, csv 8 and file_picker 12 APIs.
• FIX: example app dependency update.
• FEAT(ble): bundle Android permissions and document platform setup.

• FIX(ble): hide registered devices until rediscovered.
• FIX(ble): remove stale BLE devices on disconnect.
• FIX: await BLE MIDI readiness in connectToDevice.
• FIX: bluetooth discovery with latest Universal_ble.
• FIX: suppress duplicate BLE packets after the CoreMIDI handoff.
• FIX: subscribe to BLE MIDI notifications on platforms without a pairing.

• FIX: update example app to iOS v14 minimum.
• FIX: port to win32 6, csv 8 and file_picker 12 APIs.
• FIX: example app dependency update.

• fix(darwin) fix corebluetooth to coremidi handover

• Aligned CI to Flutter 3.44.2 so the newer BLE dependency resolves in GitHub Actions.
• Resolved the Windows example build failure caused by deprecated coroutine headers in older universal_ble releases.
• Restructured into a melos-managed federated monorepo.
• Bumped federated subpackages to 1.0.0 for the major API transition.
• Introduced shared BLE transport package (flutter_midi_command_ble) and optional BLE wiring via configureBleTransport.
• Migrated host API contracts to generated Pigeon interfaces.
• Added typed host models (MidiDeviceType, MidiHostDevice, MidiPort, MidiPacket) across platform bridges.
• Added web implementation package (flutter_midi_command_web) using browser Web MIDI.
• Added transport capabilities/policies and stronger async connection semantics (connectToDevice completes on connection).
• Added a typed MIDI parser/generator API (MidiMessageParser and MidiMessage.parse) with support for running status, realtime interleaving, SysEx, and NRPN/RPN message flows.
• Expanded test coverage across shared logic, platform interface, BLE transport, and web backend.
• Updated the example app with separate transport toggles plus distinct Refresh Devices and Scan BLE controls.
• Improved Windows MIDI enumeration with hot-plug device updates and better multi-port full-duplex pairing.

Added linux support

Updated Android plugin structure Fixed iOS compilation error, with latest Dart Fixed BLE Midi parsing on iOS

Updated Gradle version Merge PR #8

Better handling of broadcast receiver on Android.

Fixed message splitting on iOS Bluetooth MIDI Thanks to https://github.com/TheKashe for the contribution.

Added missing entitlement in iOS plist for bluetooth access

Moved Message Types into separate file: flutter_midi_command_messages.dart. Fixed threading issue. https://github.com/InvisibleWrench/FlutterMidiCommand/issues/4 Added teardown function to disconnect and close all ports and devices. Gradle dependency raised to 3.4.2 minSDKversion raised to 24 Version bumped to 0.1.0

Initial Release. Functioning discovery and connection to MIDI devices on Android and iOS, as well as BLE MIDI devices on Android. Functioning sending and receiving of MIDI data