Android Studio Gradle Already disposed Module

Question

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

Oded Breiner gave the right answer. This happens when you rename and then forget to delete the iml file — Droid Teahouse, May 17 '15 at 22:57

TWiStErRob · Accepted Answer · 2018-10-10T11:31:52.790

361

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.

edited Oct 10 '18 at 11:31

answered May 19 '18 at 23:59

TWiStErRob

44,762
26
170
254

92

For lazy copy pasters: `find . -name *.iml -delete && rm .idea/modules.xml`, sync Android Studio – LukaCiko Sep 03 '18 at 11:28
1

Thanks very much on the insight. In my case there were two entries for the `app` module in `modules.xml` – Ishan Dec 13 '18 at 08:02
This works but Android Studio (3.4.1) keeps doing this to me when I switch projects. It will also keep trying to sync the previous module that i had open. Is there a long term solution for this? – Ben Wilkinson Jul 10 '19 at 17:36
@BenWilkinson Didn't notice in 3.4.1 the two projects I open are the same codebase from different clones. Although I choose "new window" most of the time. I would close AS, clean up both projects and hope that after the new sync they settle in. – TWiStErRob Jul 10 '19 at 18:52
for mac users `find . -name "*.iml" -exec rm '{}' + && rm .idea/modules.xml` – eugene Mar 24 '20 at 02:39

score 278 · Answer 2 · edited Feb 09 '22 at 12:40

278

I figured out this problem by:

./gradlew clean
Restart Android Studio

edited Feb 09 '22 at 12:40

spydon

9,372
6
33
63

answered Dec 30 '14 at 06:55

Hsiao-Ting

3,456
2
15
20

1

Its worked but I didn't get why its download gradle version ,I have already configure the latest gradle 2.2 – Kirtikumar A. Feb 11 '15 at 06:14
29

The 3rd time I came here to read that I have to restart Android Studio #eclipseflashback – passsy Feb 17 '15 at 20:54
2

Grandle and Android Studio are simply shameful: I removed a module via the GUI and it started to give me this errors. – Antonio Sesto Apr 19 '15 at 11:26
thought first it didn't work but forgot to restart :D then it worked thx – tung Jun 17 '15 at 09:48
Instead of command line, i did the same via Build->Clean Project option in studio menu, and then restart. Just in case anyone having issue using command line, this is simpler. Does the same thing. :) – Surendra Kumar Sep 05 '17 at 12:11
Didn't work for me when using Android Studio 3.2 Beta 1 – friederbluemle Jun 24 '18 at 06:35

user3144836 · Answer 3 · 2015-02-03T14:27:07.407

102

Simplest solution. (Try this first).

Quit and Restart Android studio. (Quit not close)
Build > Clean your project if needed.

edited Feb 03 '15 at 14:27

answered Jan 04 '15 at 17:01

user3144836

4,060
3
27
27

score 84 · Answer 4 · answered Jun 08 '15 at 11:17

84

works for me: File -> Invalidate Caches / Restart... -> Invalidate and Restart

answered Jun 08 '15 at 11:17

polmabri

1,103
8
10

Yep!!! A hard invalidation of caches is sometimes the only way to fix these things. – Joshua Pinter May 18 '18 at 18:31
3

Infuriating that we still have to do this in 2019! – aaronmarino Apr 25 '19 at 14:51
1

From all the other suggestions from users in this thread (`./gradlew clean`, to delete some project files, etc.), this was the only one that worked for me. – Augusto Carmo Nov 04 '19 at 10:03

score 11 · Answer 5 · answered Jun 13 '19 at 12:24

11

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.

answered Jun 13 '19 at 12:24

Youngjae

24,352
18
113
198

1

I think this is the most robust solution – George Jul 08 '19 at 15:48
This solution solved my issue when i upgrade my Android Gradle to the build:gradle:3.5.0-rc02 – Luis Cardoza Bird Aug 04 '19 at 17:46

score 6 · Answer 6 · answered Aug 21 '15 at 11:28

6

For me this happened when i deleted a module and built a new one with the same package name Solution:

Clean & Restart Studio

answered Aug 21 '15 at 11:28

Ajji

3,068
2
30
31

score 5 · Answer 7 · answered Feb 25 '15 at 12:33

5

In the left pane, change to "Project" view.
Delete MYMODULENAME.iml

answered Feb 25 '15 at 12:33

Oded Breiner

28,523
10
105
71

Delete mymodulename.iml – xgqfrms Jan 27 '17 at 08:08

savepopulation · Answer 8 · 2019-05-28T15:02:35.493

4

For an alternative solution, check if you added your app to settings.gradle successfully

include ':app'

edited May 28 '19 at 15:02

answered Apr 20 '15 at 10:37

savepopulation

11,736
4
55
80

score 2 · Answer 9 · answered Oct 02 '19 at 10:04

2

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

answered Oct 02 '19 at 10:04

vijay_t

776
6
14

invalidate and restart is best saviour – shubham chouhan Jan 17 '23 at 11:07

Mark O'Sullivan · Answer 10 · 2018-07-03T10:13:21.800

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.

score 1 · Answer 11 · answered May 21 '19 at 04:26

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

score 1 · Answer 12 · answered Jun 24 '19 at 11:37

1

below solution works for me

Delete all .iml files
Rebuild project

answered Jun 24 '19 at 11:37

ThaiPD

3,503
3
30
48

score 1 · Answer 13 · edited Jan 11 '21 at 11:03

1

For Solve this issue take it this simple steps.

Find the .idea folder in your Android studio under the Folder Project.
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 !

edited Jan 11 '21 at 11:03

pradeexsu

1,029
1
10
27

answered Jan 11 '21 at 10:26

Nishith Darji

301
3
5

score 0 · Answer 14 · answered Jan 10 '16 at 21:24

0

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.

answered Jan 10 '16 at 21:24

Adnan

5,025
5
25
44

score 0 · Answer 15 · answered Jun 13 '18 at 20:59

0

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

answered Jun 13 '18 at 20:59

Shai Epstein

179
1
3

score 0 · Answer 16 · answered Jul 22 '19 at 12:51

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

score 0 · Answer 17 · edited Dec 27 '21 at 08:53

0

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!

edited Dec 27 '21 at 08:53

marc_s

732,580
175
1,330
1,459

answered Aug 19 '19 at 21:52

Artalus

1,114
12
25

score 0 · Answer 18 · answered Dec 02 '19 at 15:57

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.

score 0 · Answer 19 · answered Aug 12 '23 at 05:46

0

I have tried the Invalidate cached, remove .idea folder, .gradle folder, all of them does not work, So I remove the full project, then clone the repo again. it solve my problem.

answered Aug 12 '23 at 05:46

Matthew

21
4

Android Studio Gradle Already disposed Module

19 Answers19

Linked