IssueTracker

This error shows up when there is a module in your project whose .iml file does not contain:

    external.system.id="GRADLE"

Can you please check your .iml files? Also, instead of opening the project, *import* it, that will completely rewrite your .iml files and you won't see that error again.

I can confirm that it works with AS 0.8.14 if I do

1) open AS,
2) delete the Gradle Java modules from the project,
3) re-import the Gradle Java modules to the project,
4) close AS,
5) re-open AS.

In that case AS does not *not* complain about Gradle Java modules to be non-Gradle Java modules, and I've confirmed that the generated *.iml files contain external.system.id="GRADLE".

However, if I do

6) close AS,
7) delete the *.iml files,
8) re-open AS,

then AS again complains *although* the generates files again contain external.system.id="GRADLE". It seems that the problem is related to "open" vs. "import". In the latter instructions, the *.iml files seem to get implicitly generated because the Gradle Java modules are referred to from setting.gradle.

Can it be that AS is somehow performing the check for non-Gradle Java modules before the *.iml files are generated in case of just opening (instead of importing) the project?

I see what is happening now. Yes, you are right. This is an issue with "open". I think I know how to fix this issue.

Thanks for the confirmation. On a more or less related note, as this would not have happened if I was committing the *.iml files, what is your recommendation WRT this? I know about [1] which recommends to share "All the .iml module files", but it's kind of annoying that these files get rewritten if e.g. dependencies change in build.gradle. In general, most of the *.iml files seem to be duplicate content WRT the build.gradle files and can be derived from them. So, should we commit *.iml files for Gradle Android modules to Git?

[1] https://intellij-support.jetbrains.com/entries/23393067

It is better not to add iml files to source control. For regular IDEA projects is OK because .iml files are the source of truth for project configuration. In the case of Android projects, the source of truth is gradle.build files, and .iml are generated from them every time you sync your project with Gradle.

Thanks for the clear recommendation!

@5 As you seem to know what the problem is, would it be appropriate to change the status from "NeedsInfo" to "Accepted"?

This issue is fixed in Studio 1.2.

It also happens if there are comments in .iml file like:

<!----------- My comment -------------->

I just received this error from AS 1.2.1.1 and I do not have any non-Gradle Java modules in my project.

I have one main android application + six Android libraries.

We do not commit our .iml files to source control.

I received the same error in version 1.3.2.

I received this error on 2.1.2.

[Comment deleted]

received this error in 2.3 canary 2

I am receiving this error in AS 2.3 Canary 2 after doing File->Invalidate Caches->Restart.  Mine is a CMake project.  This error is not very useful, since the project eventually builds anyway.

[Comment deleted]

I am seeing this with AS 2.3 Beta 1 as well. Since this issue has been closed for some time, I went ahead and created a new issue @ https://code.google.com/p/android/issues/detail?id=230550&thanks=230550&ts=1482021669

#18 & #19: Did you happen to get this error after switching to Gradle 3.2?

And are you, by any chance, using the com.github.dcendents.android-maven plugin? I upgraded from 1.4.2 of that to 1.5, and updated to Gradle 3.2 at the same time, and I'm seeing the error even after downgrading to AS 2.2.3.

I'm in the process of doing a clean install now, and then I'll be trying reverting back to the older version of both, to see if that changes anything.

I don't know what's changed, but after a clean install, and removing ALL .iml files, after an initial complaint on opening the project, it rebuild all the .iml files and now seems fine. It's weird that last night, I tried making a brand-new project, and got the same results, but I'll take what I can get.

That said, it seems interesting to me that several people at once all seemed to run into the same thing. There may be something going on, still.

The issue is still exist in android studio 3.0.1

Same here on android studio 3.0.1

Same here on android studio 3.0.1

Same here on android studio 3.0.1

The same in Android 3.1

also the same in Android 3.1

where can i find java gradle module?

same error in Android Studio 3.1.2

Msg Error in Android Studio v 3.1.2 :
6:48 PM Unsupported Modules Detected: Compilation is not supported for following modules: AndroidStudioProjects. Unfortunately you can't have non-Gradle Java modules and Android-Gradle modules in one project.
I do not have any non-Gradle Java modules in my project.

The error occurs also in:

Android Studio 3.1.4
Build #AI-173.4907809, built on July 23, 2018
JRE: 1.8.0_152-release-1024-b01 amd64
JVM: OpenJDK 64-Bit Server VM by JetBrains s.r.o
Linux 4.15.0-32-generic

I am not sure, but I believe this causes further errors which are quite problematic. I have several projects with this issue: in all of them, some dependencies that are defined in a module's build.gradle file cannot be resolved by AS. Actually, the dependencies are resolved and downloaded from the repositories and show up under "External Libraries" in Project view. However, everywhere I try to use any class from those dependencies... I get a "Cannot resolve symbol XYZ". So I end up stuck with unresolved imports, no way to navigate through classes, etc.

The wierdest thing, though, is that the app compiles fine and runs in a device. It's just AS cannot resolve symbols from well-resolved dependencies.

Project structure overview:
- "app" Android application module (Gradle); depends on "commons", "annotations" and "processor" modules -> *gets detected as non-Gradle*
- "commons" Android library module (Gradle) with common utils, views, dependencies, etc.
- "annotations" java module (Gradle)
- "processor" java module (Gradle)

The symbols that are not resolved by AS come from dependencies defined in the "commons" module.

I have invalidated caches, deleted .idea and .gradle folders, re-downloaded the project, deleted ~/.gradle/caches folder, deleted *.iml files... no luck whatsoever.

Any hints on this issue? Do you believe the "Unsupported Modules Detected" error has anything to do with the "Cannot resolve symbol" issue?

Thanks a lot and best regards.

Same error in 3.2.1

Did some research and this was the outcome after trying in Windows & Mac.

When importing a project you have a screen giving 2 options:
- Create project from existing sources
- Import project from external model

Inside the "Import project from external model" there are 2 more options:

- Android Gradle
- Gradle

If you select "Android Gradle" everything is fine, no false positive at all.
If you select Gradle you will get the false positive error message every time you open that project in Android Studio.

same error in 3.5.1

Same error in 4.0.0

Same issue I am facing every single time I open my project in android studio 4.0.0

AS 4,0,1  
for one of older project
deleted .idea and .gradle folders, re-downloaded the project, deleted ~/.gradle/caches folder, deleted *.iml files..
work ok.

This still happens with AS 4.0.1. All of my *.iml files specify 'external.system.id="GRADLE"', and the Java modules build
when I double-click on the "build" gradle task - but the IDE can't build the Java modules itself. Better to use a Makefile for
building I guess ...

who solved this issue on the latest versions of AS, please share your actions

this is happening here too, nothing works, I'm using Android Studio Ladybug Feature Drop | 2024.2.2 Canary 1 on a mac m2
bug reported