Migrating Android Studio 3.5 Project to 3.6 rc03 causes Unsupported modules detected error [149773516]

Fixed

Bug

Status Update

No update yet.

Description

ph...@gmail.com

created issue #1

Feb 19, 2020 01:08AM

IMPORTANT: Please read

https://developer.android.com/studio/report-bugs.html carefully and supply
all required information.

Studio Build: 3.6.0 rc03
Version of Gradle Plugin: 3.6.0-rc03
Version of Gradle: 5.6.4

OS: Win10

Steps to Reproduce:
1. Create an Android Studio v3.5.x project that also contains an Android gradle library module and java only module
2. Assemble and load project into device/emulator to confirm it is working
3. Now try to open and run the project in Android Studio 3.6 v3.6.0-rc03

Comments

ph...@gmail.com <ph...@gmail.com> #2Feb 19, 2020 01:16AM

Additional notes:
This error is shown (near location of Event Log) even after invalidating cache. However, if I invalidate cache, the build succeeds and I can run the app und Studio 3.6

Message last modified on Feb 19, 2020 01:24AM

vi...@google.com <vi...@google.com> #3Feb 19, 2020 05:44AM

Thank you for the feedback. To help us troubleshoot further, can you please share the relevant idea.log file (select Help > Show Log in Finder / Explorer) if this issue reproduces again?

ph...@gmail.com <ph...@gmail.com> #4Feb 19, 2020 06:31AM

attached are the log files

log.zip

1.2 MB

Download

vi...@google.com <vi...@google.com> Feb 19, 2020 09:37AM

Assigned to an...@google.com.

ph...@gmail.com <ph...@gmail.com> #5Feb 20, 2020 04:01PM

Additional Notes:

I noticed multiple *.iml files being created in the gradle module in question during gradle sync.
I removed my .idea folder and then restarted Android Studio, and re-imported my project, and that appeared to have completely get rid of this "Unsupported modules detected" error permanently.

xa...@google.com <xa...@google.com> Mar 9, 2020 08:51PM

Reassigned to so...@google.com.

so...@google.com <so...@google.com> #6Mar 9, 2020 09:14PM

Could you share your .gitignore file in the root of your project? (assuming you used Git).

Unless you indeed have modules created in IDEA, it usually means that your .idea/modules.xml file references .iml files that do not exist. The common cause is incorrectly set up .gitignore file which ignores .iml files but not .idea/modules.xml. It is safe to ignore this error in this case or you can fix it by deleting all the '.iml files and your .idea/modules.xml. Please make sure you have a backup copy of your project.

ph...@gmail.com <ph...@gmail.com> #7Mar 9, 2020 10:50PM

I am ignoring all *.iml files and the /.idea/modules.xml file in my .gitignore

.gitignore

194 B

Download

so...@google.com <so...@google.com> #8Mar 20, 2020 08:29PM

Thank you!

so...@google.com <so...@google.com> #9Mar 20, 2020 08:30PM

Could you let us know if you use branches in Git (or the VCS you use) and whether you switch branches from within the IDE?

ph...@gmail.com <ph...@gmail.com> #10Mar 20, 2020 08:44PM

I use, create and switch git branches outside of IDE, using SourceTree.

so...@google.com <so...@google.com> #11May 1, 2020 08:48PM

Marked as fixed.

Android Studio will now drop any empty modules not registered with Gradle or any other external system such that their .iml files do not exist. This will prevent this error message (which is more like a warning) and, moreover, prevent unwanted changes to the names of modules created from the Gradle project in the IDE.

ta...@gmail.com <ta...@gmail.com> #12May 26, 2020 06:49PM

This has been really frustrating experience. Not only this warning but having duplicate .iml files is also an issue.

Is there a way that this gets picked into 4.0?

so...@google.com <so...@google.com> #13May 26, 2020 11:13PM

If you don't use a custom .gitignore and get duplicate .iml files please file a new bug and describe the way you get them. We know that there are scenarios not involving .gitignore but we don't know how to reproduce them. Thank you!