Description
The Flutter IntelliJ plugin's FlutterProjectOpenProcessor silently fails to open Flutter projects that lack a .idea directory in IntelliJ IDEA (Community and Ultimate). This is the same bug that was fixed for Android Studio in PR #8710 — the IntelliJ IDEA variant was never fixed.
Steps to Reproduce
- Clone any Flutter project (e.g.
flutter create test_app && rm -rf test_app/.idea)
- Open IntelliJ IDEA CE 2025.2+ with Flutter plugin v88.2.0+ installed
- File > Open > select the project folder
- Nothing happens. No error, no dialog, no project opens.
- The IDE log shows only:
Using processor Flutter to open the project at /path/to/project followed by nothing — no indexing, no FlutterInitializer, no error.
Expected Behavior
The project should open in a new window with Flutter module type set and Dart SDK enabled.
Actual Behavior
Nothing happens. The project silently fails to open. No error is shown.
Root Cause
FlutterProjectOpenProcessor.openProjectAsync() delegates to another ProjectOpenProcessor via getDelegateImportProvider(). For projects without a .idea directory, no other processor claims the project, so getDelegateImportProvider() returns null, and openProjectAsync() returns null — a silent failure. Since FlutterProjectOpenProcessor is registered with order="first", it already claimed the project, so no other processor gets a chance.
Workaround
Creating an empty .idea directory (mkdir project/.idea) before opening makes it work. Alternatively, disabling the Flutter plugin lets the default processor open the project.
Proposed Fix
Apply the same pattern as PR #8710 (the Android Studio fix):
- Remove
FlutterProjectOpenProcessor.kt
- Remove its
<projectOpenProcessor> registration from plugin.xml
- Add module-type-fixing logic to
FlutterInitializer (the existing startup activity for IntelliJ IDEA)
This lets the platform's default project opener handle opening, then the startup activity configures Flutter-specific settings after the project is loaded.
Environment
- IntelliJ IDEA CE 2025.2 (build IC-252.28238.7)
- Flutter plugin v90.0.0
- macOS
Related
Description
The Flutter IntelliJ plugin's
FlutterProjectOpenProcessorsilently fails to open Flutter projects that lack a.ideadirectory in IntelliJ IDEA (Community and Ultimate). This is the same bug that was fixed for Android Studio in PR #8710 — the IntelliJ IDEA variant was never fixed.Steps to Reproduce
flutter create test_app && rm -rf test_app/.idea)Using processor Flutter to open the project at /path/to/projectfollowed by nothing — no indexing, no FlutterInitializer, no error.Expected Behavior
The project should open in a new window with Flutter module type set and Dart SDK enabled.
Actual Behavior
Nothing happens. The project silently fails to open. No error is shown.
Root Cause
FlutterProjectOpenProcessor.openProjectAsync()delegates to anotherProjectOpenProcessorviagetDelegateImportProvider(). For projects without a.ideadirectory, no other processor claims the project, sogetDelegateImportProvider()returnsnull, andopenProjectAsync()returnsnull— a silent failure. SinceFlutterProjectOpenProcessoris registered withorder="first", it already claimed the project, so no other processor gets a chance.Workaround
Creating an empty
.ideadirectory (mkdir project/.idea) before opening makes it work. Alternatively, disabling the Flutter plugin lets the default processor open the project.Proposed Fix
Apply the same pattern as PR #8710 (the Android Studio fix):
FlutterProjectOpenProcessor.kt<projectOpenProcessor>registration fromplugin.xmlFlutterInitializer(the existing startup activity for IntelliJ IDEA)This lets the platform's default project opener handle opening, then the startup activity configures Flutter-specific settings after the project is loaded.
Environment
Related
FlutterStudioProjectOpenProcessor)