Run Button Grayed out: Android Studio

Question

Why is the run button always grayed out in android studio after I get some errors. I need to restart/reboot my android studio every time to run it again. I am sure that I am missing something

Run bar:

Run Button:

I also get an error right now :)

Already disposed: Project (Disposed): Already disposed: Project (Disposed)
java.lang.AssertionError: Already disposed: Project (Disposed)
    at com.intellij.openapi.components.impl.ComponentManagerImpl.getComponent(ComponentManagerImpl.java:186)
    at com.intellij.psi.PsiDocumentManager.getInstance(PsiDocumentManager.java:41)
    at com.intellij.psi.SingleRootFileViewProvider.getLastCommittedText(SingleRootFileViewProvider.java:521)
    at com.intellij.psi.SingleRootFileViewProvider.access$400(SingleRootFileViewProvider.java:63)
    at com.intellij.psi.SingleRootFileViewProvider$DocumentContent.getText(SingleRootFileViewProvider.java:537)
    at com.intellij.psi.SingleRootFileViewProvider.getContents(SingleRootFileViewProvider.java:347)
    at com.intellij.psi.impl.source.PsiFileImpl.loadTreeElement(PsiFileImpl.java:199)
    at com.intellij.psi.impl.source.PsiFileImpl.calcTreeElement(PsiFileImpl.java:776)
    at com.intellij.psi.impl.source.PsiFileImpl.getFirstChild(PsiFileImpl.java:787)
    at com.intellij.psi.impl.source.xml.XmlFileImpl.getDocument(XmlFileImpl.java:47)
    at com.intellij.psi.impl.source.xml.XmlFileImpl.getRootTag(XmlFileImpl.java:58)
    at com.android.tools.idea.rendering.LocalResourceRepository.getViewTag(LocalResourceRepository.java:323)
    at org.jetbrains.android.inspections.lint.IntellijViewTypeDetector.getViewTags(IntellijViewTypeDetector.java:42)
    at com.android.tools.lint.checks.ViewTypeDetector.visitMethod(ViewTypeDetector.java:213)
    at com.android.tools.lint.client.api.JavaVisitor$DelegatingJavaVisitor.visitMethodInvocation(JavaVisitor.java:1189)
    at lombok.ast.MethodInvocation.accept(MethodInvocation.java:114)
    at lombok.ast.Cast.accept(Cast.java:94)
    at lombok.ast.BinaryExpression.accept(BinaryExpression.java:131)
    at lombok.ast.ExpressionStatement.accept(ExpressionStatement.java:63)
    at lombok.ast.Block.accept(Block.java:106)
    at lombok.ast.MethodDeclaration.accept(MethodDeclaration.java:240)
    at lombok.ast.NormalTypeBody.accept(NormalTypeBody.java:57)
    at lombok.ast.ClassDeclaration.accept(ClassDeclaration.java:239)
    at lombok.ast.CompilationUnit.accept(CompilationUnit.java:83)
    at com.android.tools.lint.client.api.JavaVisitor.visitFile(JavaVisitor.java:217)
    at com.android.tools.lint.client.api.LintDriver.checkIndividualJavaFiles(LintDriver.java:1652)
    at com.android.tools.lint.client.api.LintDriver.runFileDetectors(LintDriver.java:986)
    at com.android.tools.lint.client.api.LintDriver.checkProject(LintDriver.java:858)
    at com.android.tools.lint.client.api.LintDriver.analyze(LintDriver.java:425)
    at com.android.tools.lint.client.api.LintDriver.analyze(LintDriver.java:369)
    at org.jetbrains.android.inspections.lint.AndroidLintExternalAnnotator.doAnnotate(AndroidLintExternalAnnotator.java:146)
    at org.jetbrains.android.inspections.lint.AndroidLintExternalAnnotator.doAnnotate(AndroidLintExternalAnnotator.java:56)
    at com.intellij.codeInsight.daemon.impl.ExternalToolPass.doAnnotate(ExternalToolPass.java:222)
    at com.intellij.codeInsight.daemon.impl.ExternalToolPass.access$400(ExternalToolPass.java:43)
    at com.intellij.codeInsight.daemon.impl.ExternalToolPass$2.run(ExternalToolPass.java:133)
    at com.intellij.codeInsight.daemon.impl.ExternalToolPass$3.run(ExternalToolPass.java:170)
    at com.intellij.util.ui.update.MergingUpdateQueue.execute(MergingUpdateQueue.java:320)
    at com.intellij.util.ui.update.MergingUpdateQueue.execute(MergingUpdateQueue.java:310)
    at com.intellij.util.ui.update.MergingUpdateQueue$2.run(MergingUpdateQueue.java:254)
    at com.intellij.util.ui.update.MergingUpdateQueue.flush(MergingUpdateQueue.java:269)
    at com.intellij.util.ui.update.MergingUpdateQueue.flush(MergingUpdateQueue.java:227)
    at com.intellij.util.ui.update.MergingUpdateQueue.run(MergingUpdateQueue.java:217)
    at com.intellij.util.concurrency.QueueProcessor.runSafely(QueueProcessor.java:238)
    at com.intellij.util.Alarm$Request$1.run(Alarm.java:327)
    at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
    at java.util.concurrent.FutureTask.run(FutureTask.java:262)
    at com.intellij.util.concurrency.QueueProcessor$RunnableConsumer.consume(QueueProcessor.java:298)
    at com.intellij.util.concurrency.QueueProcessor$RunnableConsumer.consume(QueueProcessor.java:295)
    at com.intellij.util.concurrency.QueueProcessor$2$1.run(QueueProcessor.java:110)
    at com.intellij.util.concurrency.QueueProcessor.runSafely(QueueProcessor.java:238)
    at com.intellij.util.concurrency.QueueProcessor$2.consume(QueueProcessor.java:107)
    at com.intellij.util.concurrency.QueueProcessor$2.consume(QueueProcessor.java:104)
    at com.intellij.util.concurrency.QueueProcessor$3$1.run(QueueProcessor.java:215)
    at com.intellij.util.concurrency.QueueProcessor.runSafely(QueueProcessor.java:238)
    at com.intellij.util.concurrency.QueueProcessor$3.run(QueueProcessor.java:212)
    at com.intellij.openapi.application.impl.ApplicationImpl$8.run(ApplicationImpl.java:419)
    at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
    at java.util.concurrent.FutureTask.run(FutureTask.java:262)
    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
    at java.lang.Thread.run(Thread.java:744)
    at com.intellij.openapi.application.impl.ApplicationImpl$1$1.run(ApplicationImpl.java:149)

Anson VanDoren · Accepted Answer · 2022-03-31T23:16:24.293

41

If you've made major changes to your project structure, it sometimes takes restarting Android Studio to regain the ability to Run your project. Worked for me.

edited Mar 31 '22 at 23:16

answered Aug 07 '15 at 12:34

Anson VanDoren

956
1
12
22

9

I have made some major changes and wandering around to enable that run button. At last this answer solved it. But did not require to restart the Android Studio. Just reopened the project. `File > Close Project` – krishh Aug 24 '15 at 18:48
Just noticed that Close Project is actually much faster than a restart. Thanks for the tip. – Tharkius Sep 09 '21 at 16:45
Yep, every damn time. Hey JetBrains - lets fix this! – Peter Jul 16 '22 at 23:10
1

Amazing that 7 years later this is still not fixed – Thommy Nov 29 '22 at 11:00
Add another - 8 years later this is still not fixed – JCutting8 Apr 19 '23 at 19:33

score 39 · Answer 2 · edited Mar 31 '22 at 07:07

39

You should initially configure the application.

Click the edit configuration in the combo box left to run button then:

Select the app module

enter image description here

edited Mar 31 '22 at 07:07

Sambhav Khandelwal

3,585
2
7
38

answered Mar 25 '14 at 08:52

alexandrius

1,097
1
10
21

My run configuration is ok: [Run Config](http://i.imgur.com/3mew7CV.png) It happens when the compiler finds an error. Then I fix the error and the run button stays grayed out. – kevingoos Mar 25 '14 at 09:32
Maybe you should just stop the app and then run it again, I mean to stop it in android studio – alexandrius Mar 25 '14 at 13:16
2

Stop is also grayed out :P – kevingoos Mar 25 '14 at 13:23
for me my avd was available in the dropdown, so I didn't have to fiddle wit the config screen – Harry Moreno Jul 18 '15 at 00:50
You just save my life and my job I already had a gun pointing at my head right now :/ – Neon Warge Dec 15 '16 at 06:46
@kevingoos Did you ever found out what was the issue? i'm in same boat now with Android Studio 2.3.2 – LoveForDroid May 24 '17 at 17:17
I am getting in this drop down Menu ``No Module`` – user1767754 Jun 18 '17 at 13:13
Just add one then – alexandrius Oct 24 '17 at 12:19

score 20 · Answer 3 · edited Apr 23 '22 at 23:18

20

For me, doing a Gradle sync solved that problem :

File
Sync Project with Gradle Files

edited Apr 23 '22 at 23:18

Ryan M

18,333
31
67
74

answered Apr 03 '22 at 13:51

Isma Rekathakusuma

856
12
18

score 7 · Answer 4 · edited Mar 31 '22 at 05:52

7

After an update of Android Studio or major changes to your project structure, you need to restart Android Studio and for the first time press run from the dropdown menu

edited Mar 31 '22 at 05:52

Sambhav Khandelwal

3,585
2
7
38

answered Aug 03 '16 at 07:59

Shimi Uhlman

149
1
6

Hamzah Malik · Answer 5 · 2016-03-08T21:35:51.140

5

Happened to me when my module settings weren't right. Go to module settings by right clicking the project in the left pane then make sure the target is set to android-23 or whatever version you want

edited Mar 08 '16 at 21:35

answered Dec 29 '15 at 22:32

Hamzah Malik

2,540
3
28
46

score 4 · Answer 6 · edited Mar 31 '22 at 08:50

4

After an update of Android studio the week of writing, the issue got resolved

edited Mar 31 '22 at 08:50

Sambhav Khandelwal

3,585
2
7
38

answered Apr 09 '14 at 10:36

kevingoos

3,785
4
36
63

also please share the version number of the AS you updated to – Sambhav Khandelwal Mar 31 '22 at 04:27

score 4 · Answer 7 · edited Mar 31 '22 at 12:09

4

In my case, this happened after upgrading the MacOS to Catalina and creating a new user. I had to first reinstall Flutter, get the path and add the path permanently to the environmental variables.

Then I had to go Preferences -> Languages and Frameworks -> Flutter -> add the Flutter SDK (where you installed the latest Flutter) to the Flutter SDK path.

edited Mar 31 '22 at 12:09

palme

2,499
2
21
38

answered Feb 02 '20 at 17:57

Dyary

753
7
14

score 3 · Answer 8 · edited Mar 30 '22 at 12:09

3

If you are not able to launch android app without activity then perform below mention steps.

Open Edit Configuration.
Select your application and check the do not launch activity.

edited Mar 30 '22 at 12:09

Sambhav Khandelwal

3,585
2
7
38

answered Apr 07 '16 at 11:22

rakesh rajput

606
4
5

score 3 · Answer 9 · edited Mar 31 '22 at 17:50

3

I fixed this issue by re-importing my Gradle Project. For me, everything was greyed out(Run/Debug/Build), and re-starting Android Studio was not enough to fix this issue.

I did: File -> Re-Import Gradle Project.

After a while, all the buttons in the Android Studio IDE started functioning normally again.

edited Mar 31 '22 at 17:50

Sambhav Khandelwal

3,585
2
7
38

answered Jun 12 '19 at 09:12

Arka Mukherjee

2,083
1
13
27

1

I didn't have this option, the most similar was "File > Invalidate aches / Restart" and it worked for me – Nisba Sep 22 '21 at 12:15

score 2 · Answer 10 · edited Mar 30 '22 at 12:05

2

For me, it was an issue with the app module which was not selected after Android Studio update. Select the app module in the combo box to the left of the run button.

edited Mar 30 '22 at 12:05

Sambhav Khandelwal

3,585
2
7
38

answered Apr 10 '17 at 04:22

Vijay Pal

181
1
2
5

score 2 · Answer 11 · edited Mar 29 '22 at 03:40

2

There are many solutions related to this problem.

Go to Setting->Plugins->uncheck the red one's and apply. Then again mark them (check them ) and apply .

Restart your android studio , it will work.

edited Mar 29 '22 at 03:40

Sambhav Khandelwal

3,585
2
7
38

answered Apr 29 '17 at 17:45

Jay

674
11
13

score 2 · Answer 12 · edited Mar 28 '22 at 01:34

2

Just sync the Gradle.

Done. This worked for me

edited Mar 28 '22 at 01:34

Sambhav Khandelwal

3,585
2
7
38

answered Nov 28 '21 at 09:42

GeneCode

7,545
8
50
85

score 1 · Answer 13 · edited Mar 28 '22 at 08:08

1

Go to Run > Edit Configuration then go to Defaults > Android app" then in General tab select App in module then "Apply" This is working for me.

edited Mar 28 '22 at 08:08

Sambhav Khandelwal

3,585
2
7
38

answered Nov 15 '17 at 08:33

Basant

741
7
16

I am not getting app option under module, it just shows – gegobyte Dec 05 '18 at 08:15
@Chinmay Sarupria, if "app" not appear in drop down then follow these steps "File>Invalidate Caches / Restart...>Invalidate and Restart" and try again above,i hope it will help you – Basant Dec 06 '18 at 09:29
Yeah I did something similar, I closed project and reopened it, Gradle synced the project and everything started working. – gegobyte Dec 06 '18 at 10:06

score 0 · Answer 14 · edited Mar 30 '22 at 12:03

0

Sometimes it happens without any reason. If there is no problem with Run configuration, restarting Android Studio usually helps.

edited Mar 30 '22 at 12:03

Sambhav Khandelwal

3,585
2
7
38

answered Feb 25 '17 at 12:27

Asim Gasimzade

75
1
9

score 0 · Answer 15 · edited Mar 28 '22 at 13:03

0

I closed the project, and in the screen listing my recent projects, I removed the project and then went to Open an Existing Android Studio Project -> Open.

This fixed the issue for me.

edited Mar 28 '22 at 13:03

Sambhav Khandelwal

3,585
2
7
38

answered Jul 26 '18 at 10:32

Ian Wambai

203
3
19

score 0 · Answer 16 · answered Mar 27 '22 at 16:21

0

It is very simple solution for the one like me for whom nothing mentioned above worked. Just follow: Build → Clean Project

answered Mar 27 '22 at 16:21

Sambhav Khandelwal

3,585
2
7
38

score 0 · Answer 17 · answered Jan 17 '23 at 23:01

0

Build -> Clean Project and then Build -> Rebuild Project worked for me.

answered Jan 17 '23 at 23:01

Rita

223
2
8

score 0 · Answer 18 · answered Jan 20 '23 at 17:33

0

Sync your project. This fixed my problem.

answered Jan 20 '23 at 17:33

Dilman Salih

101
10

As it’s currently written, your answer is unclear. Please [edit] to add additional details that will help others understand how this addresses the question asked. You can find more information on how to write good answers [in the help center](/help/how-to-answer). – Community Jan 22 '23 at 03:17

Run Button Grayed out: Android Studio

18 Answers18