I've updated Android Studio to version 3.2.
After that update one of my projects don't want to index.
It freezes with the message
"Indexing paused due to batch update".
How can I fix this?
File gradle-wrapper.properties
:
distributionBase=GRADLE_USER_HOME
distributionPath=wrapper/dists
zipStoreBase=GRADLE_USER_HOME
zipStorePath=wrapper/dists
distributionUrl=https\://services.gradle.org/distributions/gradle-4.4-all.zip
File gradle-properties
:
org.gradle.jvmargs=-Xmx1536m
org.gradle.parallel=true
org.gradle.daemon=true
org.gradle.configureondemand=true
Press the play button to the right of this message and the issue would resolve.
You have to do it every time, because right now the problem is systematic and there is no solution to stop it from appearing.
I faced the same issue, it seems that Android Studio messes up the cache.
Go to File > Invalidate Caches and Restart
Then on the Pop Up that appears choose Invalidate and Restart
xxx.iml
file, the.idea
and.gradle
foldersI faced the same Issue but the situation which lead to this was different: I created a remote branch on the project's repository on GitHub and it was empty. And then I checkout to that branch locally while android studio was running.
I then deleted the local repository and created it again but this time it was not empty. Further I pushed the code to the remote branch as well.Now I thought that it will start the project normally but again the same happened.it resulted in an IDE error.
To solves this issue I deleted that local repository and again re-imported it.Than it started correctly.
I solved it by deleting all the *.iml files and the .idea folder
None of the other answers worked for me. Not even pressing the "play" button. All that worked was closing the project and re-opening it via "Open an existing Android Studio project".
The effect only lasts for a single session. As soon as I close and re-open the project, or AS 3.3, the problem re-appears.
Deleting
C:\Users\<user>\.AndroidStudio3.3\config\options\recentProjects.xml
(before starting AS 3.3) is an alternative way to accomplish the same thing.EDIT
Upon upgrading to AS 3.3.2, this solution no longer worked. However, after an "Invalidate Caches and Restart", the problem disappeared.