Unable to run Android Emulator, not applicable for “main.dart” configuration

[archenroot]

Thanks for the feedback! If your issue is related to the Flutter framework itself,
please open an issue at
github.com/flutter/flutter.

Steps to Reproduce

So initially this worked, but I have a bigger project with multiple modules based on on either flutter or java (for API development), like this:

Initially the main project SDK was set to Android and I added a flutter app and it worked, but with adding some java modules I switched main project SDK to JDK and worked on those apis, today I tried to test again mobile app with latest APIs, but it says:

When I open AVD manager I can start the emulator without issues:

I tried to connect directly to phone via wifi, by:
over USB do:
[11:33:23] zangetsu@zeus  $  ~  adb tcpip 5555
restarting in TCP mode port: 5555
And then:
[11:33:28] zangetsu@zeus  $  ~  adb connect 192.168.88.97:5555
connected to 192.168.88.97:5555

No, my phone is directly visible in idea, but same result:

My project SDK settings, I switched back from JDK to Android SDK:

And also configured it on module itself:

I am watching idea log, but don't see much..

When running manually from command-line it works:

Version info

[✓] Flutter (Channel master, 2.6.0-12.0.pre.222, on Gentoo/Linux 5.13.10-gentoo-x86_64, locale en_US.utf8)
• Flutter version 2.6.0-12.0.pre.222 at /data/proj/private/flutter
• Upstream repository https://github.com/flutter/flutter.git
• Framework revision ed60103645 (2 days ago), 2021-10-06 06:53:04 -0400
• Engine revision f967ebb685
• Dart version 2.15.0 (build 2.15.0-178.0.dev)

[✓] Android toolchain - develop for Android devices (Android SDK version 31.0.0)
• Android SDK at /data/devel/sdk/android
• Platform android-31, build-tools 31.0.0
• ANDROID_HOME = /data/devel/sdk/android
• ANDROID_SDK_ROOT = /data/devel/sdk/android
• Java binary at: /opt/android-studio/jre/bin/java
• Java version OpenJDK Runtime Environment (build 11.0.10+0-b96-7249189)
• All Android licenses accepted.

[✓] Chrome - develop for the web
• CHROME_EXECUTABLE = /usr/bin/google-chrome-stable

[✓] Linux toolchain - develop for Linux desktop
• clang version 12.0.1
• cmake version 3.21.3
• ninja version 1.10.2
• pkg-config version 0.29.2

[✓] Android Studio (version 2020.3)
• Android Studio at /opt/android-studio
• Flutter plugin version 61.2.2
• Dart plugin version 203.8430
• Java version OpenJDK Runtime Environment (build 11.0.10+0-b96-7249189)

[✓] Android Studio
• Android Studio at /opt/android-studio/
• Flutter plugin can be installed from:
🔨 https://plugins.jetbrains.com/plugin/9212-flutter
• Dart plugin can be installed from:
🔨 https://plugins.jetbrains.com/plugin/6351-dart
• android-studio-dir = /opt/android-studio/
• Java version OpenJDK Runtime Environment (build 11.0.10+0-b96-7249189)

[✓] IntelliJ IDEA Ultimate Edition (version 2021.2)
• IntelliJ at /opt/idea-ultimate-bin-2021.2.2
• Flutter plugin version 61.2.4
• Dart plugin version 212.5486

[✓] Connected device (3 available)
• Android SDK built for x86 (mobile) • emulator-5554 • android-x86 • Android 11 (API 30) (emulator)
• Linux (desktop) • linux • linux-x64 • Gentoo/Linux 5.13.10-gentoo-x86_64
• Chrome (web) • chrome • web-javascript • Google Chrome 94.0.4606.81

• No issues found!

[stevemessick]

It looks like you have a monorepo project, which is not supported by the Flutter plugin. The Flutter plugin currently requires Flutter projects to be opened as top-level projects in the IDE, not as modules embedded in a larger project. This is tracked in #5291

Fortunately, it is easy to open a project in its own widow. Just choose the option to use a new window.

[archenroot]

@stevemessick - the issue is bit elsewhere as I tried today open the module as project which didn;t work, I tried even create new flutter project, but I do not see any device in dropdow box while I started even running emulator via AVD manager window.

But there is really nothing suspicious in the idea.log
idea.log

Here is output of 'flutter devices':

Its bit different issue then one suggested by you.. it seems. it will be also good if the plugin can do more debug/error logging. ..