Build failure on Flutter 3.44.6 / AGP 9.0.1 / Kotlin 2.3.20 (Windows): :flutter_midi_command_android:compileDebugKotlin fails with incremental cache error

[nambi0915]

Environment

• flutter_midi_command: 1.0.6
• Flutter: 3.44.6 (stable)
• Dart: (from Flutter 3.44.6)
• Platform: Windows 11
• Java: 17
• Android Gradle Plugin: 9.0.1
• Kotlin: 2.3.20
• Gradle: 9.1

Description

I am unable to build even a fresh Flutter project after adding
flutter_midi_command.

The application builds successfully before adding the package.

After adding:

dependencies:
flutter_midi_command: ^1.0.6

the build consistently fails during:

:flutter_midi_command_android:compileDebugKotlin

Steps to Reproduce

1. Create a new Flutter project

   flutter create midi_test

2. Add

   flutter_midi_command: ^1.0.6

3. Run

   flutter pub get
   flutter run

Expected behavior

The project should build successfully.

Actual behavior

Gradle fails while compiling the Android plugin.

Error:

Execution failed for task ':flutter_midi_command_android:compileDebugKotlin'.

java.lang.Exception:
Could not close incremental caches

Storage ... is already registered

Full stack trace

(attach the complete stack trace here)

Additional information

• This happens on a completely fresh Flutter project.
• Removing flutter_midi_command immediately fixes the build.
• No application code imports or uses the package yet.
• The issue occurs before any plugin API is called.

Could you please verify whether flutter_midi_command 1.0.6 has been tested with:

• Flutter 3.44.6
• Android Gradle Plugin 9.0.1
• Kotlin 2.3.20
• Gradle 9.1

If this is a known compatibility issue, I'd be happy to test a fix or provide any additional information.

flutter doctor -v

[√] Flutter (Channel stable, 3.44.6, on Microsoft Windows [Version 10.0.26200.8894], locale en-IN) [276ms]
• Flutter version 3.44.6 on channel stable at C:\flutter
• Upstream repository https://github.com/flutter/flutter.git
• Framework revision ee80f08bbf (2 weeks ago), 2026-07-08 15:02:06 -0700
• Engine revision 83675ed276
• Dart version 3.12.2
• DevTools version 2.57.0
• Feature flags: enable-web, enable-linux-desktop, enable-macos-desktop, enable-windows-desktop, enable-android, enable-ios, cli-animations,
enable-native-assets, enable-swift-package-manager, omit-legacy-version-file, enable-lldb-debugging, enable-uiscene-migration

[√] Windows Version (11 Home Single Language 64-bit, 25H2, 2009) [1,306ms]

[√] Android toolchain - develop for Android devices (Android SDK version 36.0.0) [3.4s]
• Android SDK at C:\Android
• Emulator version unknown
• Platform android-36, build-tools 36.0.0
• ANDROID_HOME = C:\Android
• Java binary at: C:\Program Files\Common Files\Oracle\Java\javapath\java.exe
This JDK was found in the system PATH.
To manually set the JDK path, use: flutter config --jdk-dir="path/to/jdk".
• Java version Java(TM) SE Runtime Environment (build 17.0.12+8-LTS-286)
• All Android licenses accepted.

[√] Chrome - develop for the web [194ms]
• Chrome at C:\Program Files\Google\Chrome\Application\chrome.exe

[X] Visual Studio - develop Windows apps [192ms]
X Visual Studio not installed; this is necessary to develop Windows apps.
Download at https://visualstudio.microsoft.com/downloads/.
Please install the "Desktop development with C++" workload, including all of its default components

[√] Connected device (4 available) [627ms]
• SM S928B (mobile) • R5CX418GBYA • android-arm64 • Android 16 (API 36)
• Windows (desktop) • windows • windows-x64 • Microsoft Windows [Version 10.0.26200.8894]
• Chrome (web) • chrome • web-javascript • Google Chrome 150.0.7871.181
• Edge (web) • edge • web-javascript • Microsoft Edge 150.0.4078.83

[√] Network resources [1,334ms]
• All expected network resources are available.

Also attached the traceback file

flutter_midi_command_stacktrace.txt

[nambi0915]

Update: I found that the issue only occurs when the Flutter project is on a different drive from the Pub cache.

Example:

Project: D:\sample_flutter\sample_midi
Pub cache: C:\Users<user>\AppData\Local\Pub\Cache

Creating the exact same project on the C: drive builds successfully.

This suggests the issue may be related to Kotlin/Gradle incremental compilation with cross-drive paths on Windows rather than the MIDI functionality itself.

If this is a known limitation or there's a recommended workaround, please let me know.