Indexing freeze with message: Indexing paused due to batch updated

Question

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

Answer 1

Stay Connected to internet.Let the batch to be updated.Wait one time and it will be easy the next time. OR...Click on the play button.

Answer 2

I faced the same issue, because my AS version is not the same with gradle plugin's version.

Answer 3

I did it by exporting the project into zip file and open it like normal. you can export by clicking the file navbar and choose export to zip file

Answer 4

I saw this error and none of the solutions posted here worked for me. I had a specific scenario (see below), and I could get rid of the problem in my specific scenario. Not sure if the OP had the same scenario, by here are my two cents:

In my specific case I had two projects open in Android Studio, where one of the project was from a sshfs-mounted directory (the other project was local to my computer). I believe that made Android Studio throw the "Indexing paused due to batch updated" message on, strangely, both the projects.

To get rid of the error on the local project, I had to close the remote mounted project. On closing that project, the message was gone for my local project.

Hope that helps.

Answer 5

I invalidated the cache and restarted Android Studio. That worked for me. You can do this by: File > Invalidate Caches / Restart > Invalidate and Restart

Answer 6

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.