[Flutter Plugin 95.0.0] "No Flutter SDK configured" in Android Studio Rabbit 1 (2026.2.1 Canary 1)

[tdevaux]

After updating the Flutter IntelliJ plugin to version 95.0.0 in Android Studio Rabbit 1 (2026.2.1 Canary 1) on macOS, the editor displays a "No Flutter SDK configured" banner on Dart/Flutter files.

Under Settings > Languages & Frameworks > Flutter, the Flutter SDK path / version configuration does not seem to recognize or properly configure the SDK.

Steps to Reproduce

1. Install Android Studio Rabbit 1 | 2026.2.1 Canary 1 (Build #AI-262.9437.185.2621.16076543).
2. Install / update the Flutter plugin to version 95.0.0.
3. Open a Flutter/Dart project.
4. Open any Dart file in the editor.

Expected Behavior

• The Flutter SDK should be detected/configured properly

Actual Behavior

• A banner appears at the top of the editor: "No Flutter SDK configured." with options Dismiss and Open Flutter settings.
• The Flutter SDK settings panel under Languages & Frameworks > Flutter fails to load/recognize the Flutter SDK path and version properly.

Workaround

Downgrading the Flutter plugin to 94.0.0 resolves the issue temporarily:

1. Uninstall Flutter plugin 95.0.0.
2. Download and install 94.0.0 from the JetBrains Marketplace.
3. Restart IDE.

Environment Details

• OS: macOS (Apple Silicon / aarch64)

• IDE: Android Studio Rabbit 1 | 2026.2.1 Canary 1

  • Build: #AI-262.9437.185.2621.16076543, built on August 13, 2026
  • Runtime version: 25.0.3+-15898627-b508.16 aarch64
  • VM: OpenJDK 64-Bit Server VM by JetBrains s.r.o.

• Flutter Plugin Version:

  • ❌ Broken: 95.0.0
  • ✅ Working: 94.0.0

[tdevaux]

There are also reports of this bug on Linux workstations.

[helin24]

Though this one has been marked as potentially related to SDK changes, I believe we checked that this is actually due to removing bazel functionality, probably in #9042

[helin24]

As discussed, this is a no fix.

If there's motivation to maintain a separate fork reapplying bazel functionality, @pq offered help to explore the practicality of this in person. We're also eager to hear any feedback about the MCP experience in g3, and please keep us updated if you need any setup help with alternative tooling.