Session 'app': Error Launching activity

Question

After the Android Studio 2.0 update while the gradle build finishes I get this :

Session 'app': Error Launching activity .

It prevents the app from starting but it's installed in my emulator. This is what comes up in the Run tab :

Unexpected error while executing: am start -n "com.example.user.ypologismosmoriwn/com.example.user.ypologismosmoriwn.MainActivity" -a android.intent.action.MAIN -c android.intent.category.LAUNCHER Error while Launching activity

Here is the code:

package com.example.user.ypologismosmoriwn;

import android.support.v7.app.AppCompatActivity;
import android.os.Bundle;

public class MainActivity extends AppCompatActivity {

    @Override
    protected void onCreate(Bundle savedInstanceState) {
        super.onCreate(savedInstanceState);
        setContentView(R.layout.activity_main);
    }
}

It's just an empty Activity,nothing added

and the XML code is just a Relative Layout with 4 Texts and 3 Check Boxes

This is the logcat i am getting

Thanks anyone who is willing to help

It's the default manifest ,take a look [Manifest](http://pastebin.com/jdp4xaki) — Yiannr, Apr 10 '16 at 14:05
I've fixed the issue (on my Anroid watch Moto 360) by uninstalling the app before installing from AS — Kiryl Ivanou, Oct 14 '16 at 13:10
For everybody that needs more suggestions: https://stackoverflow.com/questions/36802588/error-while-launching-activity has different answers (sadly, none have yet worked for me) — lucidbrot, Sep 26 '17 at 12:57

score 136 · Accepted Answer · edited Feb 25 '19 at 06:48

136

I also faced this issue after I updated to AS2.0. I found that it is because of the instant run enabled. So my solution is to disable the "instant run". and it worked. To disable "instant run", you can go to Preference Dialog ( May be Setting dialog on Windows), then select Build, Execution, Deployment > Instant Run, and uncheck all the checkbox to disable Instant Run.

This is my temporary solution and it may help you. Later, I'll find a better way to this issue.

update by 2016/06/06

A better solution instead of disabling instant run. Remove the .idea folder and .gradle folder, then click button Sync Project with Gradle Files (or through the menu File -> Sync Project with Gradle Files), after this process finished, you are able to run your app as normal.

Good Luck~

edited Feb 25 '19 at 06:48

bv.

85
6

answered Apr 11 '16 at 16:01

Nick

1,614
1
12
10

1

Disabling instant run stopped the Session 'app': Error Launching activity error.Still though,the app wont start automatically in the emulator. – Yiannr Apr 12 '16 at 10:31
worked for me too. I could re-enable it after running it once without instant run enabled! – CodingYourLife May 05 '16 at 12:32
instead of removing `.idea` and `gradle` things you can simply do a clean project through: `Build > clean project` – TheMMSH Jul 24 '16 at 07:36
2

Do we need to delete `.idea` and `gradle` folder before each run?! – VSB Jul 25 '16 at 19:15
1

No, just at first time – Nick Jul 28 '16 at 03:45
Will we remove .gradle folder that is hidden file ? – Olkunmustafa Aug 17 '16 at 11:33
Deleting .gradle and .idea folders doesn't work for me. I still get the same error. I don't want to disable instant run because it's a handy feature. – Daniel Harris Sep 12 '16 at 07:07
Daniel, what's your version of AS? – Nick Sep 13 '16 at 08:37
Oh Thanks a lot, Searched the whole SO and ONLY this worked for me. – Syeda Zunaira Nov 07 '16 at 05:10
2

I just did a gradle sync to solve it. Was driving me crazy until I found this thread. In my case I had renamed the applicationId earlier to cause this problem. – riper Jan 11 '17 at 15:31
3

If you have are facing this issue after installing the app from the device, the app might still exit, try checking in the settings -> Apps -> Delete the app. Then try to run the app. It worked for me. – amj Jun 15 '17 at 15:20
1

The amount of problems Instant Run gives us is 100x times more than the benefits it offers. It's such an awful feature and too good to be true (and stable). – Subby Sep 07 '17 at 16:31
In my case, the instant run is already disabled. The removal of .idea and .gradle then sync worked for me. Thanks! – sticky Nov 30 '17 at 11:22

EdgeDev · Answer 2 · 2020-01-10T07:22:05.407

54

If you are using Android 7.0 and above it is likely that the app was installed in two places (Guest and Admin) and you only Uninstalled it for only one user and that is causing problems.

To solve that, go to: Settings -> Apps & Notifications -> See all Apps -> find the app you are trying to install.

Then click the menu on the top right corner and select Uninstall for all users

Run Your App from Android Studio it should work.

edited Jan 10 '20 at 07:22

answered Dec 24 '18 at 00:55

EdgeDev

2,376
2
20
37

This issue can exist in Android 7.0 devices as well. This solution works! – Maverick7 Sep 08 '19 at 10:24
This issue has bugged me a couple of times recently. And your approach is the same as the approach I used from https://medium.com/@kaikoenig/android-studio-session-app-error-launching-activity-7ef5820a927a. Thank god I found this approach! – Jiaheng Jun 11 '20 at 23:45

score 36 · Answer 3 · answered Nov 17 '17 at 14:14

36

Try reinstalling the app, this solved the error for me. The trick was that, I uninstalled my app, but Android didn't truly uninstall it. On my phone, there is a guest user (my sister uses it sometimes). If you uninstall the app from your main user, it will still be available on the phone, but only for the guest user. It looks like Android Studio can't handle this case. I guess it detects that the app is installed, so it will not be reinstalled again for the current user, hence the OS can't access and launch the activity. Nice bug, I'll report it.

answered Nov 17 '17 at 14:14

klenium

2,468
2
24
47

1

This is what helped me - very interesting Android behaviour – d4c0d312 Apr 30 '18 at 10:09
That was my case as well, thank you for finding this ! – Julian Honma Jul 12 '18 at 09:02
This was my case as well, when nothing else worked. It was especially interesting that I could build the app in Android Studio, but could not run it on the device. A quick `adb uninstall` did the trick! – Chad Schultz Oct 19 '18 at 17:30

score 26 · Answer 4 · answered Jun 17 '16 at 13:15

26

I've had same issue, rebuilding project clears the error for me.

build -> rebuild project -> run

answered Jun 17 '16 at 13:15

spek

361
3
3

1

by far the simplest solution! – new star Jun 21 '16 at 18:19
And the only correct. Disabling "Instant run" is totally wrong because actually it works ok in 99% of cases. – madhead Jul 08 '16 at 21:23

score 9 · Answer 5 · edited Jun 21 '16 at 08:51

9

This is issue with 2.0+ studio

Issue 206036: No local changes, not deploying APK

I found the nice workaround here just add -r flag here in edit configurations and also disabling instant

Waiting to get Instant run Feature run smoothly soon with no type 3 error more!!

edited Jun 21 '16 at 08:51

Ranjithkumar

16,071
12
120
159

answered Jun 12 '16 at 03:38

Rahul

337
3
10

1

@RanjithKumar you need to add this setting for each project and what i am doing is though it is showing error but new apk gets installed and then you can debug or play the same afterwards. Also uncheck Skip installation in Misc tab – Rahul Jun 28 '16 at 09:16

elliptic1 · Answer 6 · 2018-05-19T21:31:33.113

7

For me the problem was that the app I was trying to launch was already installed under a different user account on my phone. I saw this when I went to Settings->apps looking to uninstall it. I switched to the other user, uninstalled it, came back to the original user, and was able to install and launch the app from Android Studio with no more problems.

edited May 19 '18 at 21:31

answered Dec 21 '17 at 19:38

elliptic1

1,654
1
19
22

score 4 · Answer 7 · answered May 08 '16 at 20:39

I spent a whole lot of hours on this exact issue. The "instant run" fix was a total fail. And I wasn't missing the android.intent.category.LAUNCHER I removed all applicable Android Studio and SDK code and re-installed. Still a no go.

Ultimately I think my issue was marginal hardware. I'm running on a laptop with a AMD A6-4400M processor. There is no hardware acceleration / virtualization tools available. I was just running the standard Android Studio / Google emulator. It was painfully slow, and although I was eventually able to see the emulator and interact with it, I was never able to connect the emulator to Android Studio to upload APK's.

But I did discover an awesome fix.

Remove all Android Virtual Devices and install the GenyMotion Emulator (with VirtualBox).
I've tried GenyMotion emulators before (with a Linux) and it didn't make much difference in load up speed.
On this Windows 10 machine it works exceptionally well. Its pretty quick, easily connects to Android Studio and works well deploying my apps.
GenyMotion offers one personal use device at no cost. Kudos to the GenyMotion team!

Answer provided here in case anybody else gets stuck with this error, possibly with this root cause.

score 3 · Answer 8 · edited May 23 '17 at 12:34

I got the same problem and fixed it with this answer.

But this problem was created by myself, as I tried to debug my unit tests. Therefore I had to uncheck the Use in-process build option of the AS Settings in Build, Execution, Deployment > Compiler.

So in my case it works, if I disabled instant run. But it also works, as I enabled instant run and also the Use in-process build option.

score 3 · Answer 9 · answered Jan 15 '19 at 12:34

3

Just run adb uninstall <package name> in your terminal and reinstall the app again.

Hope it helps.

answered Jan 15 '19 at 12:34

kiran puppala

689
8
17

And to get the package name use `adb shell pm list packages` – h8pathak Apr 30 '19 at 08:28

CodyF · Answer 10 · 2016-07-22T15:10:57.713

2

Same issue, but for me problem was that Android Studio couldn't find my Default Activity. When I specified the intent filter to catch the MAIN action intent, I didn't specify the LAUNCHER category, and that caused the 'Error Launching activity' issue.

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

edited Jul 22 '16 at 15:10

answered Apr 22 '16 at 17:01

CodyF

4,977
3
26
38

1

The issue was there even though I hadn't change anything ,it was a default new project.Maybe it was caused after the 2.0 Android studio update. – Yiannr Apr 23 '16 at 10:34

score 2 · Answer 11 · answered Aug 29 '16 at 07:48

Just Run --> clean and rerun , In my case it helps. Prompts automatically like following message

would you uninstall already installed activity with same name

if activity is already installed first uninstall it and make project ready after installing app.

score 2 · Answer 12 · answered Apr 10 '17 at 12:13

I had this error because of my stupidity. In the manifest.xml I have wrongly declared two Activity as Launcher. Make sure you have only one activity as Launcher.

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

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

score 1 · Answer 13 · answered Aug 05 '16 at 09:51

1

I was facing the same problem in android studio 2.1.2 but worked after selecting Build -> Clean Project or alternatively Run -> Clean and Rerun

answered Aug 05 '16 at 09:51

bmacharia

1,026
10
12

score 1 · Answer 14 · answered Apr 04 '17 at 22:15

1

I tried all suggested answers. I found out this is a hardware issue on Android N phone with studio 2.3 version. App launches fine on phones below version 7.

answered Apr 04 '17 at 22:15

user3329166

126
6

score 1 · Answer 15 · answered Apr 09 '17 at 06:14

1

I've fixed the issue using this solution.If you are running the application in USB device then close all the virtual device like : genymotion / virtual machine .

answered Apr 09 '17 at 06:14

Hoque MD Zahidul

10,560
2
37
40

score 1 · Answer 16 · answered Aug 01 '17 at 01:37

1

Uninstall App on your real device or emulator. Then Run again. It's worked for me. I used Android Studio 2.3.3

answered Aug 01 '17 at 01:37

fathurzero

1,486
2
10
9

score 1 · Answer 17 · edited Apr 05 '18 at 06:34

1

Just disable Instant Run.

Go To File >> Settings >> Build, Execute, Deployment >> Instant Run

Uncheck The Box that says Enable instant run to hot swap code/resource changes on deploy

Re-run the emulator.

edited Apr 05 '18 at 06:34

Zoe

27,060
21
118
148

answered Aug 06 '17 at 12:56

devDeejay

5,494
2
27
38

score 1 · Answer 18 · answered Jun 26 '18 at 14:34

OK already so many possible solutions for this problem, if none of those works then try this.

I faced this problem when I first uninstalled my app then tried reinstalling from ADB. But then after trying these many solutions, I realized that uninstalling app nowadays does not really uninstall it. It just disables it for few days so that it can be enabled in case you change your mind.

Now I am not sure whether its done by LG or Native Android Nougat.

I just went in Settings-> apps-> my-app and uninstalled it completely. After that from Android studio I am able to install the app again properly without this error.

Yes, I hate this feature. If I uninstalled it then I don't want it. It took me a while to figure out what was wrong. — Panama Jack, Feb 29 '20 at 23:13

adray · Answer 19 · 2019-03-07T19:53:50.007

1

Adb also throws this error if applicationId, package of launching activity or module name contains error substring

edited Mar 07 '19 at 19:53

answered Mar 07 '19 at 19:45

adray

1,408
16
20

OH MY GOD I WISH I COULD KISS YOU. 2 YEARS I'VE BEEN DEALING WITH THIS ON AND OFF. – Bassinator Mar 24 '19 at 18:01
Google, why? I Demand to know who is responsible for this sloppy ass programming. – Bassinator Mar 24 '19 at 18:21

score 1 · Answer 20 · answered Mar 18 '20 at 13:34

1

None of the existing answers helped me as I had the same app installed in my other profile. Solution -

Switch to the other profile
Uninstall the app from 2nd profile
Switch back

answered Mar 18 '20 at 13:34

spiraldev

171
1
3

score 0 · Answer 21 · edited May 23 '17 at 12:17

0

I tried the above answer. However, none of the solutiond worked for me. I changed the emulator to USB and the code is running on the USB target device prefectly!

edited May 23 '17 at 12:17

Community

1
1

answered Jun 16 '16 at 18:19

Homayoun

21
5

I also had no problems with emulator, on my Android watch 'Moto 360' only. I've fixed it by uninstalling the app from device before and after that it install it from AS successfully! – Kiryl Ivanou Oct 14 '16 at 13:17

score 0 · Answer 22 · answered Jul 03 '16 at 15:12

0

All answers did not work for me.This error raised when I was trying to rename the app package.I have ended up creating a new project with the new package name and move my files to the new one.

answered Jul 03 '16 at 15:12

How sad was that .. :( – simo Aug 23 '16 at 11:18

score 0 · Answer 23 · edited Apr 05 '18 at 06:34

I had same problem. I was using AVD with arm processor image and received this same message. The only way for me to make Android Studio 2.1.2 runs the app with instant run was change to an X86 processor image. The error was gone and ( until this moment) I think the emulator works faster than ARM emulated. My workstation configuration is Intel I5, 6Gb RAM. Maybe this helps until next fix.

score 0 · Answer 24 · answered Oct 14 '16 at 13:11

0

I've fixed the issue (on my Anroid watch Moto 360) by uninstalling the app before installing from AS

answered Oct 14 '16 at 13:11

Kiryl Ivanou

1,015
2
12
22

score 0 · Answer 25 · edited Apr 05 '18 at 06:35

0

Disable "instant run", you can go to Preference Dialog ( May be Setting dialog on Windows), then select Build, Execution, Deployment > Instant Run, and uncheck all the checkbox to disable Instant Run.

And Reboot your Device this should make the thing work....instant run has a bug in Android studio 2+ This should do the magic

edited Apr 05 '18 at 06:35

Zoe

27,060
21
118
148

answered Oct 18 '16 at 06:45

atish naik

226
2
11

score 0 · Answer 26 · answered Dec 08 '16 at 08:24

0

it occured when I changed the applicationId in app gradle file. It works for me after I sync gradle.

answered Dec 08 '16 at 08:24

Maggie

51
2

score 0 · Answer 27 · answered Mar 02 '18 at 11:48

I tried, clean & rebuild project and Invalidate Cache & Restart also manually removed .gradle and .idea folders, but that didn't solved the issue.

I have 3 user acounts in my phone. So, I didn't select Uninstall for all users, and it only uninstall my app from first user account, but it was still there in guest and second user account.

So, I removed it from rest of the accounts and it solved my issue!!

score 0 · Answer 28 · answered Apr 30 '18 at 05:26

0

I got the same error. This issue was caused by uninstalling the app from the device (uninstalled from only 1 user)

Solved by logging into the other user and uninstall the app from there.

and it solved.

answered Apr 30 '18 at 05:26

Hatim

1,516
1
18
30

score 0 · Answer 29 · answered Jul 14 '18 at 10:33

0

I did all suggestions above, but they didn't work! I rebuilt the project, uninstalled the app from my real device, unplugged USB, then I run Android Studio and run the app on my real device and the issue was gone.

Hope this helps!

answered Jul 14 '18 at 10:33

parse

1,706
17
27

score 0 · Answer 30 · answered Aug 10 '18 at 05:31

0

I had the same error as in the headline. after I changed the version name and version code in the gradle, the sync happened and then it worked. so maybe even only sync can help sometimes.

answered Aug 10 '18 at 05:31

Gilad Levinson

234
2
12

score 0 · Answer 31 · answered Jan 25 '19 at 06:13

Sometimes when you uninstall the application from android device it does not get uninstalled completely. It goes to disabled state. To fix this, Go to Settings -> Apps -> Disabled Apps -> Select your app and uninstall.

Then go to android studio and run the app. The isssue is resolved.

score 0 · Answer 32 · answered Apr 26 '19 at 07:05

0

Clearing the device data worked for me...

Close your emulator

Go to AVD Manager

Under "Actions" select "Wipe Data" (for the device your intend to use)

Then run your app again!

Hope this helps...

answered Apr 26 '19 at 07:05

Rafa

21
1

score 0 · Answer 33 · answered Nov 21 '19 at 19:28

0

The only one best Answer is to run uninstall command from adb and install the app again

C:\Users\YourUser\AppData\Local\Android\sdk\platform-tools>adb uninstall applicationId

applicationId: from gradle module file

answered Nov 21 '19 at 19:28

Mohammad Abu Hmead

621
2
7
18

score 0 · Answer 34 · answered Feb 29 '20 at 18:44

My Answer is specifically for Redmi/Mi Phone users. I faced this issue multiple times.

Sometimes we uninstall the app but it is not completely uninstalled but app will not display on screen and also it will not be listed in Settings -> Apps.

After checking multiple answers, What worked for me is below command

Go to Android Studio and click on Terminal tab in bottom of Android Studio. Connect your device, once adb detects your device, Run this command and try again to Run your application. Hope it will help.

adb uninstall com.shyam.smsapp

com.shyam.smsapp replace with your application package name

score 0 · Answer 35 · answered Jul 21 '22 at 13:16

0

write this line in terminal, it works for me adb uninstall

answered Jul 21 '22 at 13:16

Ahmed Mohamed

301
1
12

Session 'app': Error Launching activity

35 Answers35

update by 2016/06/06

Linked