Default Activity not found in Android Studio

Question

I just upgraded to Android Studio 0.2.8 and I am getting an error that says "Default Activity not found" when I try to edit the run configurations.

When I launch Android Studio I get this error "Access is allowed from event dispatch thread only"

The activity I am using is a fragment activity.

So far I've tried rebuilding and invalidate caches/restart. Both were of no use.

Please let me know what I can do to fix the problem.

Possible duplicate of [Error: Default Activity Not Found](http://stackoverflow.com/questions/15825081/error-default-activity-not-found) — Sky Kelsey, May 10 '16 at 18:40

score 51 · Answer 1 · answered Sep 16 '13 at 13:02

51

Have you added ACTION_MAIN intent filter to your main activity? If you don't add this, then android won't know which activity to launch as the main activity.

ex:

<intent-filter>
      <action android:name="android.intent.action.MAIN"/>
      <action android:name="com.package.name.MyActivity"/>
      <category android:name="android.intent.category.LAUNCHER" />
</intent-filter>

answered Sep 16 '13 at 13:02

Anup Cowkur

20,443
6
51
84

1

Yes, this is done. I fixed the "Access is allowed from the event dispatch thread only" by using oracle JDK instead of openJDK. The default activity missing still persists though – Vipassana Vijayarangan Sep 17 '13 at 09:38
5

Also the name `"com.package.name.MyActivity"` could be ommitted if all the `` element is inside an `` element that corresponds to your MyActivity in your namespace. – Xavi Montero Nov 21 '14 at 18:35
Hah, I renamed a class named `Filter` including all variables named `filter` and apparently Android Studio decided to include `AndroidManifest.xml` and ``. This answer made my double check my `AndroidManifest.xml` and helped me find the bug =) – Stephan Henningsen Sep 20 '16 at 21:41
Where is this even documented? I can’t find it… – mirabilos Aug 14 '20 at 23:28

score 45 · Accepted Answer · edited May 23 '17 at 12:10

45

In Android Studio, right click on the project and choose Open Module Settings. Then go to the Sources tab in your module, find the src folder, right click on it and mark it as Sources (blue color).

EDIT: There is no sources tab in later versions of Android Studio, but you can edit the build.gradle file instead: https://stackoverflow.com/a/22028681/1101730 (thanks for comment Josh)

edited May 23 '17 at 12:10

Community

1
1

answered Mar 10 '14 at 18:42

Micer

8,731
3
79
73

27

How could I do this in *0.6.1*? I don't see a **Sources** tab. – lschlessinger Jun 27 '14 at 00:03
7

me neither. There are Properties, Signing, Flavors, Build Types and Dependencies – Junior Mayhé Jun 28 '14 at 00:41
4

I had no "Sources" tab, so I edited the build.gradle file instead: http://stackoverflow.com/a/22028681 – Josh Nov 10 '14 at 20:57
2

Perfect! Thanks for helping @Micer. Guys, in your IntelliJ project press 'F4', then you have three tabs (Sources, Paths, Dependencies), go to 'Sources' tab and check if the 'src' folder (in the tree structure) it's blue. If not press 'Alt+S' to include the source folder in the Project Structure. – Ryan Amaral Nov 14 '14 at 01:47
@Micer There is no Sources tab. – IgorGanapolsky Jan 05 '15 at 15:18
1

@IgorGanapolsky You're right, seems like Sources tab has been removed in later versions of Android Studio. Check Josh's answer. – Micer Jan 08 '15 at 14:40
1

I had same problem. I just restarted the android studio and it was fine. Not a logical answer but solved my problem. – user1154390 Sep 18 '15 at 09:26
1

this has moved in Android Studio 1.5.1 it as at File -> Project Structure... -> Modules -> Sources – Mark Ch Jan 26 '16 at 11:24
1

In Android Studio 2.2, the fix is slightly different. For an activity that actually does not have an activity that launches at startup, like a background app. It can be fixed by pull-down menu for the packages, then Edit Configurations > choose your package on the left > under General tab > Launch Options > Launch > Nothing – nevzo Sep 22 '16 at 21:15

syntagma · Answer 3 · 2018-10-17T23:01:21.273

33

I had the same problem while importing a project into Android Studio, probably caused by the fact that the project has been developed on an earlier version of Android Studio than currently installed on my computer.

What solved it was simply choosing:

File -> Invalidate Caches / Restart...

and then selecting Invalidate and Restart.

edited Oct 17 '18 at 23:01

answered Sep 22 '15 at 16:19

syntagma

23,346
16
78
134

1

Thank you very much @syntagma, your guidance solved my problem after hours of effort. – MMG Mar 11 '20 at 05:45

score 17 · Answer 4 · answered Mar 16 '15 at 04:59

If you don't have the tab and you started with an empty activity try this. Below is a sample code example:

<application android:label="@string/app_name">

    <activity android:name=".HelloActivity">
        <intent-filter>
            <action android:name="android.intent.action.MAIN"/>
            <category android:name="android.intent.category.LAUNCHER"/>
        </intent-filter>
    </activity>

</application>

Now go to your AndroidManifest.xml file. Next copy the intent filter from this code. Look at your manifest file really good and paste the intent filter in the exact place it is in the code above. (after the .yourActivityName> part of the manifest.) I hope this helped.

Phileo99 · Answer 5 · 2018-11-08T18:13:43.190

14

If you are still getting an error that says "Default Activity not found" when you try to edit the run configurations even after executing:

Invalidate cache and Restart.

Then try deleting the Settings/Preferences folder:

/< USER_HOME_DIR >/.AndroidStudioPreview3.2

or on Mac :

/Users/<USER_NAME>/Library/Preferences/.AndroidStudioPreview3.2

edited Nov 08 '18 at 18:13

answered Jul 19 '18 at 03:00

Phileo99

5,581
2
46
54

If you have renamed your packages or you switched branches from your version control, sometimes Android Studio doesn't recognize all files and mess up things. The only solution that worked for me is to close AS, then deleted .AndroidStudioXY (where XY is your version number) which @Phileo99 pointed out. – Zbarcea Christian Oct 25 '18 at 10:09
1

You saved my life! Just do this /< USER_HOME_DIR >/.AndroidStudioPreview3.2 – nadafafif Nov 08 '18 at 10:11
you're welcome @nadafafif ! please upvote my answer if it helped you. – Phileo99 Nov 08 '18 at 18:14
@Phileo99 Already did that. Couldn't stop myself from doing it. :) Cheers. Keep helping like that. – nadafafif Nov 13 '18 at 10:41
That helped, but be aware that you will download a lot of stuff. It tooks around 15 minutes to download – Valgaal Feb 27 '19 at 23:48

score 10 · Answer 6 · edited May 23 '17 at 12:10

When I clicked "Open Module Settings", there was no "Source" tab, I think because that's been removed for newer versions of Android Studio (I'm on 0.8.14). So I had to do this instead:

Add these lines to the build.gradle file inside the android { ... } block:

android { ... sourceSets { main.java.srcDirs += 'src/main/<YOUR DIRECTORY>' } }

After editing the file, click Tools > Android > Sync Project with Gradle Files.

Credit to this answer and this comment.

score 9 · Answer 7 · answered Nov 16 '15 at 07:35

9

Following did the trick for me. From Run -> Edit Configuration.

answered Nov 16 '15 at 07:35

CoDe

11,056
14
90
197

I would advice against this solution as it caused the application to no longer be shown in the list of available applications on the Samsung Galaxy S5 Neo and the Samsung Galaxy S6. – Teun Kooijman May 22 '16 at 10:44

score 3 · Answer 8 · answered Jul 16 '20 at 18:08

My problem came down to an additional error that was popping up sometimes, stating

Manifest Merger failed with multiple errors in Android Studio

What ultimately was causing my problem was the fact that there were multiple manifests (a debug Manifest, and a manifest in the new module I had just imported), and they were not merging correctly due to this. After seeing this answer, I was able to analyze the merged manifest and find the cause of the issue and fix it.

score 3 · Answer 9 · answered Sep 23 '20 at 12:57

3

Press app --> Edit Configurations
After that change value in Launch on "Nothing"

answered Sep 23 '20 at 12:57

Valentin

400
2
11

Its kind of a workaround. This process will install the app but will not auto launch the app. – Vikrant_Dev Feb 17 '21 at 07:09

score 2 · Answer 10 · answered May 27 '15 at 18:10

this happened to me because I capitalized the paths in the manifest. changed:

<intent-filter>
    <action android:name="ANDROID.INTENT.ACTION.MAIN"/>
    <category android:name="ANDROID.INTENT.CATEGORY.LAUNCHER"/>
</intent-filter>

to

<intent-filter>
  <action android:name="android.intent.action.MAIN"/>
  <category android:name="android.intent.category.LAUNCHER"/>
</intent-filter>

and it was fixed

score 2 · Answer 11 · answered Aug 09 '15 at 10:39

I ran into the same issue today and was going through the answers here.

For me the difference was that yesterday it worked fine, so I figured it could not really be a configuration issue, neither configuration nor Version of Android Studio changed.

Fortunately, I tried a restart of Android Studio before trying any of the other answers, and luckily that solved the issue.

So for all people out there who run into this: first thing to try is to restart Android Studio and only if that does not solve the issue try the other answers here.

Teun Kooijman · Answer 12 · 2016-02-17T17:11:58.933

I just experienced the same error in Android Studio 1.5.1. and just found the source of the problem. I am not sure whether the cause was a human error or some strange glitch in the behaviour of the IDE, but none of the existing StackOverflow questions about this subject seemed to show anything about this so I figured I post it as an answer anyway.

For me, either one of my team members or the IDE itself, had changed the launcher activities manifest entry, causing it to look like this:

        <activity
            android:name="com.rhaebus.ui.activities.ActivitySplash"
            android:launchMode="singleInstance"
            android:screenOrientation="portrait">
            <intent-filter>
                <action android:name="android.intent.action.MAIN" />
                <id android:name="android.intent.id.LAUNCHER" />
            </intent-filter>
        </activity>

While it should, in fact, look like this:

        <activity android:name="com.rhaebus.ui.activities.ActivitySplash"
            android:launchMode="singleInstance"
            android:screenOrientation="portrait">
            <intent-filter>
                <action android:name="android.intent.action.MAIN" />
                <category android:name="android.intent.category.LAUNCHER" /> <!-- Change Here -->
            </intent-filter>
        </activity>

So please double, triple, quadruple check the format of your launcher activity in the manifest and you might be able to save yourself some time.

Hope this helps.

EDIT: I strongly suggest people not to go with the answers that suggest to manually select a launcher activity inside the configuration options of your module, as this caused the application to no longer be shown in the list of installed apps on both the Samsung Galaxy S5 Neo and the Samsung Galaxy S6 (at least for me).

score 2 · Answer 13 · answered Dec 11 '18 at 08:21

You can get Android Studio not to complain by going to the "Edit Configurations" menu (tap "Shift" three times, type "Edit Configurations"), then change Launch Options > Launch to "Nothing".

I'll probably add a generic activity containing instructions, just to avoid any confusion.

score 1 · Answer 14 · edited Sep 17 '15 at 01:55

1

In Android Studio switch to Project perspective (not Android perspective).
Make sure that your project follows the gradle plugin's default structure (i.e. project_dir/app/src/main/java...)
Delete all build folders and subfolders that you see.
In the toolbar click Build -> Clean Project, then Build -> Rebuild Project.
Try to run the project.

edited Sep 17 '15 at 01:55

gustavohenke

40,997
14
121
129

answered Jan 05 '15 at 15:37

IgorGanapolsky

26,189
23
116
147

score 1 · Answer 15 · answered Mar 21 '15 at 00:31

1

Please make sure in manifest that package name is same with your main activity

answered Mar 21 '15 at 00:31

U three

43
7

score 1 · Answer 16 · answered May 18 '20 at 17:30

1

In my case, it worked when I removed the .idea folder from the project (Project/.ida) and re-opened Android Studio again.

answered May 18 '20 at 17:30

Yousef Gamal

1,026
2
17
32

Removing the .idea folder helped in my case, Thanks! For clarification all files with extension ".iml" were inside the .idea folder. Please DON'T remove only .iml files because this can lead to other errors! – Cordis Audax Agrinova Jul 30 '20 at 11:10

score 0 · Answer 17 · answered Jul 26 '14 at 16:50

0

Right click on the project and choose Open Module Settings.
Go to the Sources tab in your module.
Find your src folder.
Right click on it and mark it as Sources.

This solved the error in my case.

answered Jul 26 '14 at 16:50

ConquerAndroid

231
2
3

score 0 · Answer 18 · answered Aug 06 '14 at 19:12

0

If you changed name of directories (class structure) for example com.dir.sample to com.dir.sample1, after that don't forget to change package com.dir.sample to com.dir.sample1.

answered Aug 06 '14 at 19:12

Zafer

316
4
13

score 0 · Answer 19 · answered Jan 19 '15 at 09:18

0

Modify "Workspace.xml" (press Ctrl + Shft + R to search it)

Modify the activity name with package name
Make sure to change "name="USE_COMMAND_LINE" to value="false"
Reload the project

Done!

answered Jan 19 '15 at 09:18

neo-av-in

141
1
4

I'd search with Ctrl + Shft + F, + R = replace where F = find. – Shishdem Mar 26 '15 at 12:38

score 0 · Answer 20 · answered Oct 31 '15 at 09:07

0

For those like me who were struggling to find the "Sources tab":

Here you have to mark your "src" folder in blue (first click in Mark as: Source, then in your src folder), and you're good to go.

answered Oct 31 '15 at 09:07

Rocío García Luque

3,597
31
31

score 0 · Answer 21 · answered Dec 31 '16 at 04:43

0

There are two steps you can take:

Go to configurations and enter the name of activity to be launched
If it is still not working Disable Instant Run

answered Dec 31 '16 at 04:43

Harish Rana

484
3
8

score 0 · Answer 22 · answered Dec 20 '18 at 06:42

0

I have tried all solutions, but not working at all. than I have tried to disable Instant run in my android studio.

Go to Android Studio Settings or Preferences (for MAC) -> Build,Execution,Deployment -> Instant Run.

uncheck the Instant run functionality and than after click sync project with gradle files from file menu

now run your build...

answered Dec 20 '18 at 06:42

Mayur Sakhiya

326
2
14

This is no longer valid for Android Studio 4.0+ – Jorge E. Hernández Jul 07 '20 at 23:37

score 0 · Answer 23 · answered Oct 04 '19 at 11:28

0

In some case you can have model with some category field, if you will refactor it in all places, it may refactor it in manifest file and then and the tag xml will became invalid.

answered Oct 04 '19 at 11:28

Pavel Poley

5,307
4
35
66

score 0 · Answer 24 · answered Jun 07 '20 at 12:34

Many possibilities can be happened for this kind of case (Default Activity not Found) If all code are fine, especially on Manifest, just just need to Invalidate Cache and restart the studio,

But sometime it is happened when you have duplicate activity declaration on manifest, not only for the Main activity, it is also triggered by child activities as well.

That happened with me, Default activity not found because i have duplication child activities on manifest, after deleted that, everything is well

score 0 · Answer 25 · answered Jun 28 '20 at 01:37

0

Check if there is any duplicate tag in your AndroidManifest.xml file.

answered Jun 28 '20 at 01:37

Devansh Maurya

832
12
11

score 0 · Answer 26 · answered Jul 04 '20 at 16:18

0

I figured it out. I mistakenly added final keyword in activity declaration. Once I removed it everything works!

public  class SplashActivity extends AppCompatActivity {
...
}

answered Jul 04 '20 at 16:18

Asad35Waheed

121
11

score 0 · Answer 27 · answered Feb 17 '21 at 08:17

0

In my case, this happened because of sudden shutdown of the system. I followed these steps:

Close Android Studio
Go to

C:\Users\my_user_name.AndroidStudio4.0\system\caches

Delete "caches" folder
Relaunch Android Studio

answered Feb 17 '21 at 08:17

Vikrant_Dev

430
2
15

score -1 · Answer 28 · edited Jun 20 '20 at 09:12

-1

In Android Studio
Go to edit Configuration .
Select the app.
choose the lunch Activity path.
apply, OK.

Thanks!!

edited Jun 20 '20 at 09:12

Community

1
1

answered Mar 30 '15 at 12:06

Mstack

321
1
12

score -1 · Answer 29 · answered Jun 02 '20 at 13:07

-1

Default Activity name changed (like SplashActivity -> SplashActivity1) and work for me

answered Jun 02 '20 at 13:07

Mehmet Agah Balbay

59
2
3

Default Activity not found in Android Studio

29 Answers29

Linked

Related