Android Studio Gradle Already disposed Module
AndroidAndroid StudioAndroid Gradle-PluginAndroid Problem Overview
I have installed Android Studio version 1.0.1. I have imported my projects from eclipse and it works fine. Then I deleted a module and reimported it into my Android Studio project. The gradle build says "BUILD SUCCESSFUL" but it pops up an alert window with the message
Failed to complete Gradle execution. Cause: Already disposed: Module: 'MYMODULENAME'
I can't start my app now. Any idea what I can do?
Edit: I solved the problem with the following instructions:
- Switch project view from Android to Project
- Remove entry include 'MYMODULENAME' in settings.gradle
- The blue box in the module symbol don't show. Then you can delete the module in the context menu
- Import the module
Android Solutions
Solution 1 - Android
Note: this is purely an IDEA/AS issue, gradlew clean
| Build > Clean | Build > Rebuild will just waste your time.
Most of the solutions here are blind stabbings in the dark. Here's what I found to be the root cause:
- Some of the
.iml
files may be missing (maybe because we deleted it), check if the module erroring has.iml
. - If it is missing, check if
.idea/modules.xml
has an entry for that module
While syncing I noticed that IDEA/AS tries to put a new duplicate entry into .idea/modules.xml
while there's already one. This duplicate entry is probably disposed of twice while the sync tries to reset the modules in memory.
Quick Solution: In order to make it work the easiest is to delete .idea/modules.xml
along with the .iml
files. Additionally may worth deleting .idea/modules/
folder if it exists. Restart Android Studio (no need to clear cache) and force a Gradle sync from Gradle view or toolbar to recreate the files.
Solution 2 - Android
I figured out this problem by:
./gradlew clean
- Restart Android Studio
Solution 3 - Android
Simplest solution. (Try this first).
-
Quit and Restart Android studio. (Quit not close)
-
Build > Clean your project if needed.
Solution 4 - Android
works for me: File -> Invalidate Caches / Restart... -> Invalidate and Restart
Solution 5 - Android
Sometimes gradlew clean
or Invalidate Cache and Restart
does not help, because these methods do not clean Android Studio specific files by themselves.
In this case, close AS and remove .idea
directory and .iml
file in a root project where settings.gradle
file exists. This will make AS rebuild from the fresh ground.
Solution 6 - Android
For me this happened when i deleted a module and built a new one with the same package name Solution:
> Clean & Restart Studio
Solution 7 - Android
- In the left pane, change to "Project" view.
- Delete MYMODULENAME.iml
Solution 8 - Android
For an alternative solution, check if you added your app to settings.gradle successfully
include ':app'
Solution 9 - Android
Had a similar issue when working with RN components in my Android project and the only way to get around this issue was to ignore the gradle project.
To do this:
- Click on the gradle tab on the right hand side of AS
- Right click the gradle module which is causing an issue
- Click "Ignore Gradle Project"
- Perform a gradle sync which should be successful now
- If you need this module perform the 4 above steps again, this time when right click on the gradle project it'll show "Unignore Gradle Project"
- Gradle sync should now work
No idea what causes this but I've had this happen to me when using React Native Maps.
Note: If you're still having issues following this. Try to refresh the gradle project which was causing issues.
Solution 10 - Android
If gradle clean
and/or Build -> Clean Project
didn't help try to re-open the project:
- Close the project
- Click "Open an existing Android Studio project" on the "Welcome to Android Studio" screen
- Select gradle file to open
Warning Be aware it's a destructive operation - you're going to loose the project bookmarks, breakpoints and shelves
Solution 11 - Android
below solution works for me
- Delete all
.iml
files - Rebuild project
Solution 12 - Android
For me this happened when I removed a module and tried to build the project:
Simple solution was to Invalidate the cache & Restart.
Android Studio>File>Invalidate Caches>Invalidate & Restart
Solution 13 - Android
For Solve this issue take it this simple steps.
- Find the
.idea
folder in your Android studio under the FolderProject
. - In
.idea
--> Find this one..idea/.modules
- Simple Delete that
.modules
folder and restart Your studio. - when it reopens gradle sync Automatically and also recreate
.modules
folder and files. - Error has gone !
Solution 14 - Android
I also face this problem sometimes. Click on gradle console in bottom bar of android studio, at right side. It will show the exact error in logs. My problem was that I had compile SDK 22 and imported appcomact library was of sdk 23.
Solution 15 - Android
I had the same problem, after delete some gradle files (of aws)
i solved it by mark them "ignore gradle"
I believe it is not the best answer but it solve it for me
Gradle (at the right bar)--> right click on the problematic gradle --> ignore
Solution 16 - Android
Although the accepted answer didn't work for me (unfortunately I can't leave a comment), it led me in the right direction.
in .idea/libraries
i found that there were some duplicate xml files (the duplicates were named with a 2 before the _aar.xml
bit).
deleting those, restarting android studio and sync fixed the error
Solution 17 - Android
In my case, same as in this question, it happened because I had my project in a symbolic link directory. After reopening the project in the real directory and reconfiguring gradle (File -> Sync with Gradle files
) the problem went away. Shame on you, Android Studio!
Solution 18 - Android
I was having this issue because gradle
and Android Studio
were using a different path for the jvm
. In the Event Log
there was an option for AS and gradle
to use the same path. Selecting this and then doing an invalidate cache & restart
resolved the issue for me.