Related
I recently downloaded Android Studio 2.0 and create a new startup app and did not add anything code by myself. After running the app, android studio installs the APK on emulator successfully but does not launch the app instead it gives the following error:
$ adb shell am start -n "com.example.muhammad.firstapp/com.example.muhammad.firstapp.MainActivity" -a android.intent.action.MAIN -c android.intent.category.LAUNCHER
Unexpected error while executing: am start -n "com.example.muhammad.firstapp/com.example.muhammad.firstapp.MainActivity" -a android.intent.action.MAIN -c android.intent.category.LAUNCHER
Error while Launching activity
I searched it on google and found that it was asked before but the provided solution isn't working for me either. I also did not add anything in the AndroidManifest.xml file.
AndroidManifest.xml
<?xml version="1.0" encoding="utf-8"?>
<manifest xmlns:android="http://schemas.android.com/apk/res/android"
package="com.example.muhammad.firstapp">
<application
android:allowBackup="true"
android:icon="#mipmap/ic_launcher"
android:label="#string/app_name"
android:supportsRtl="true"
android:theme="#style/AppTheme">
<activity android:name=".MainActivity">
<intent-filter>
<action android:name="android.intent.action.MAIN" />
<category android:name="android.intent.category.LAUNCHER" />
</intent-filter>
</activity>
</application>
</manifest>
MainActivity.java
package com.example.muhammad.firstapp;
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);
}
}
activity_main.xml
<?xml version="1.0" encoding="utf-8"?>
<RelativeLayout xmlns:android="http://schemas.android.com/apk/res/android"
xmlns:tools="http://schemas.android.com/tools"
android:layout_width="match_parent"
android:layout_height="match_parent"
android:paddingBottom="#dimen/activity_vertical_margin"
android:paddingLeft="#dimen/activity_horizontal_margin"
android:paddingRight="#dimen/activity_horizontal_margin"
android:paddingTop="#dimen/activity_vertical_margin"
tools:context="com.example.muhammad.firstapp.MainActivity">
<TextView
android:layout_width="wrap_content"
android:layout_height="wrap_content"
android:text="Hello World!" />
</RelativeLayout>
I had exactly this same problem today [Android Studio 2.3.3, Android 8.0 on the phone]
This is what I discovered. The app that I was trying to install was not shown in the android Application window [the one where you have them all]. But once I went in: Settings->Apps&Notifications->AppInfo I could see this screenshot where it was said that this app was "not installed for this user":
At that point I entered the app->clicked on the three points in the top right corner->Uninstall for all the users
Now when I tried to run the project through Android Studio the error message disappeared and the app was correctly installed
Hope this helps, have a good day
Antonino
If you are using android 2.0+, take the following steps
1. Go to run
2. Select edit configurations..
3. type -r in the Install Flags text field
4. Apply and Ok then run program again
tested(23/07/2016)
I encounter the same problem in AVD, when first start app it was fine but when launch the app again it reports "Error while Launching activity".
My resolution is: in AVD, uninstall the apk, maybe the reason is the new Android studio has an issue when install apk to a AVD.
Thanks, Yu
There is issue with studio 2.0+ instant run feature
Work around provided at Android Open Source Project - Issue Tracker
Don't waste time in re installation of studio or cleaning gradle build file often .
Just add -r flag in
Install flags in
Run->Edit configurations->General
For me, I was unable to solve the problem, which is absolutely infuriating for a piece of software as important as this. I'm a diehard Android guy, and this is frankly unacceptable, that I cannot even debug an app.
However, I did find a workaround that might help some.
For me, the Session 'app': Error Launching activity error didn't prevent the app being installed, but it did prevent debugging the app since there was no way to attach a debugger. However, there is another way.
Start the app on the phone, then click attach debugger to Android process (near the regular debug button, looks just like it), this allows you to attach a debugger to an already running app.
It's annoying as hell, but at least I can debug my app again.
After struggling for hours I came to conclusion that the problem is with the user files stored in AVD. Whenever I choose Wipe Data of an AVD the app works like a charm and does not show the error. But its really painful for developers to Wipe Data everytime before running the app as Wipe Data will only work if your emulator is not running.
In another test phase, I wiped the data of AVD and then started the app, it ran successully; but when I tried to run the app second time it shows me that error again.
Error while Launching activity
Then I opened 'Manage Apps' and delete my app from emulator. But it did not work either.
Workaround
Delete Android Studio but don't delete the SDK
Download and Install Android Studio 1.5.1 from here http://tools.android.com/download/studio/stable
Another Workaround (But that does not work for me)
Session 'app': Error Launching activity
Final Conclusion
I think the problem is with somewhere when we tried to 'Run' the app on second time. It does not uninstall the previous version of the app so when it found the package name already there it does not install the app then; results in error launching the activity.
I've been working on this same exact problem for the last 8 hours...you've had no issues after rolling back from 2.0 to 1.5.1?
I've noticed that, even with the error, running the app works fine sometimes.
You're not alone, brother. I'll be sure to update when I figure out the solution.
Also, what are your specs? I'm running the following:
Windows 7
AMD FX(tm)-8120 8-Core
AVD:
Android 6.0
CPU/ABI: Google APIs ARM (armeabi-v7a)
Target: API lvl 23
No accelerometer
heapSize: 64
If you want more details, let me know. A sample size of 2 is always better than 1.
I have been install the new version 2.10 just now ,and the problem seems like to be solved.So you can try it.
downgrading android version is not the curect way to fix the problem..if you like that you will lose new features of testing and developing in android studio.same kinda problem i faced previously when i upgrade to android 2.1.but i resolve my problem through restarting the android studio by selecting option of
"setting->invalid caches/restart".
Even though your problem is not fixed then try to create another avd with suitable system image.
make sure that you have downloaded a suitable system image for your emulator to run in cpu.
i solved my emulator launching problem in android 2.1 by downloading system image x86-64 with api level 23.try to download this system image if you are using 64 bit.
I had the same problem and solved it by following these steps:
Uninstall the app, in my case, from the actual hardware that is connected over the USB.
This is the key step! Uninstall the app from the "Recently uninstalled apps"
Rebuild the app.
Run it.
To fix this annoying problem I followed the three following steps:
Included the -r flag in the Install Flags. This may be
accomplished by clicking on Run -> Edit Configurations. Now
Select the General tab and type -r in the Install Flags text
area.
Click on File and select Invalidate Caches / Restart.
Uninstall earlier versions of the app. By this I mean to remove it by accessing General -> Apps and uninstall the app. Dragging and dropping the icon of the app to the trash in the home screen will not fix the issue.
There's a simple solution to this problem if you're running the app on an Emulator. This happens because of Storage space constraints. Increasing the storage space of the Emulator should solve this issue.
You can either free up some storage space from the Emulator itself or increase the storage space from the AVD Manager.
This happened to me after changing manifest permissions and trying to restart the app using AndroidStudio 3.5.1. The fix was to uninstall the app using adb and restart.
adb uninstall <your app package name>
Though I'm not sure about the exact reason for this problem, I just found a solution when I cleaned the project.
So, go to Build -> Clean project. This should help you
I had the same problem, in fact the last version of my application was disabled in the phone or emulator, to solve the problem just reactivated the application in my phone (settings-> apps-> disabled) and I recompile and the problem was solved.
I had this problem on LG-K220. It turned out that I have previously deinstalled this app, but this phone model had a system app which does not deinstall the app at first, but keeps it like in a recycle bin. No wonder Android Studio had troubles installing a new one. I completely removed the app and then it worked.
the solution is simple just uninstall package using adb command after you connect to your device
adb uninstall PACKAGE NAME
replace “PACKAGE NAME” with the name of the application you want to delete and press “Enter.”
In my experience this error occurs when you manually uninstall your apk when it's building or installing via android studio.
In a such case I simply create a apk and install it on the AVD or phone. After It will work as usual.
Hope this will help to someone.
Maybe you just set your phone or emulator to refuse all the requests of installing apk through USB.
Open your phone setting and change this to allow the installing. The problem is solved.
Hope it works for you!
I tried almost every solution found in the community, but the Error Launching activity never gone. Now I found what's the reason of my case.
I use a USB connected LG K20 Plus phone to test my projects built on the Android Studio 2.3.3, the Error Launching activity will appear if I uninstall the project in the phone, it will launch normally again if the deleted project is reinstalled.
I hope this will help people having the same or similar Error in your developing projects.
I recently downloaded Android Studio 2.0 and create a new startup app and did not add anything code by myself. After running the app, android studio installs the APK on emulator successfully but does not launch the app instead it gives the following error:
$ adb shell am start -n "com.example.muhammad.firstapp/com.example.muhammad.firstapp.MainActivity" -a android.intent.action.MAIN -c android.intent.category.LAUNCHER
Unexpected error while executing: am start -n "com.example.muhammad.firstapp/com.example.muhammad.firstapp.MainActivity" -a android.intent.action.MAIN -c android.intent.category.LAUNCHER
Error while Launching activity
I searched it on google and found that it was asked before but the provided solution isn't working for me either. I also did not add anything in the AndroidManifest.xml file.
AndroidManifest.xml
<?xml version="1.0" encoding="utf-8"?>
<manifest xmlns:android="http://schemas.android.com/apk/res/android"
package="com.example.muhammad.firstapp">
<application
android:allowBackup="true"
android:icon="#mipmap/ic_launcher"
android:label="#string/app_name"
android:supportsRtl="true"
android:theme="#style/AppTheme">
<activity android:name=".MainActivity">
<intent-filter>
<action android:name="android.intent.action.MAIN" />
<category android:name="android.intent.category.LAUNCHER" />
</intent-filter>
</activity>
</application>
</manifest>
MainActivity.java
package com.example.muhammad.firstapp;
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);
}
}
activity_main.xml
<?xml version="1.0" encoding="utf-8"?>
<RelativeLayout xmlns:android="http://schemas.android.com/apk/res/android"
xmlns:tools="http://schemas.android.com/tools"
android:layout_width="match_parent"
android:layout_height="match_parent"
android:paddingBottom="#dimen/activity_vertical_margin"
android:paddingLeft="#dimen/activity_horizontal_margin"
android:paddingRight="#dimen/activity_horizontal_margin"
android:paddingTop="#dimen/activity_vertical_margin"
tools:context="com.example.muhammad.firstapp.MainActivity">
<TextView
android:layout_width="wrap_content"
android:layout_height="wrap_content"
android:text="Hello World!" />
</RelativeLayout>
I had exactly this same problem today [Android Studio 2.3.3, Android 8.0 on the phone]
This is what I discovered. The app that I was trying to install was not shown in the android Application window [the one where you have them all]. But once I went in: Settings->Apps&Notifications->AppInfo I could see this screenshot where it was said that this app was "not installed for this user":
At that point I entered the app->clicked on the three points in the top right corner->Uninstall for all the users
Now when I tried to run the project through Android Studio the error message disappeared and the app was correctly installed
Hope this helps, have a good day
Antonino
If you are using android 2.0+, take the following steps
1. Go to run
2. Select edit configurations..
3. type -r in the Install Flags text field
4. Apply and Ok then run program again
tested(23/07/2016)
I encounter the same problem in AVD, when first start app it was fine but when launch the app again it reports "Error while Launching activity".
My resolution is: in AVD, uninstall the apk, maybe the reason is the new Android studio has an issue when install apk to a AVD.
Thanks, Yu
There is issue with studio 2.0+ instant run feature
Work around provided at Android Open Source Project - Issue Tracker
Don't waste time in re installation of studio or cleaning gradle build file often .
Just add -r flag in
Install flags in
Run->Edit configurations->General
For me, I was unable to solve the problem, which is absolutely infuriating for a piece of software as important as this. I'm a diehard Android guy, and this is frankly unacceptable, that I cannot even debug an app.
However, I did find a workaround that might help some.
For me, the Session 'app': Error Launching activity error didn't prevent the app being installed, but it did prevent debugging the app since there was no way to attach a debugger. However, there is another way.
Start the app on the phone, then click attach debugger to Android process (near the regular debug button, looks just like it), this allows you to attach a debugger to an already running app.
It's annoying as hell, but at least I can debug my app again.
After struggling for hours I came to conclusion that the problem is with the user files stored in AVD. Whenever I choose Wipe Data of an AVD the app works like a charm and does not show the error. But its really painful for developers to Wipe Data everytime before running the app as Wipe Data will only work if your emulator is not running.
In another test phase, I wiped the data of AVD and then started the app, it ran successully; but when I tried to run the app second time it shows me that error again.
Error while Launching activity
Then I opened 'Manage Apps' and delete my app from emulator. But it did not work either.
Workaround
Delete Android Studio but don't delete the SDK
Download and Install Android Studio 1.5.1 from here http://tools.android.com/download/studio/stable
Another Workaround (But that does not work for me)
Session 'app': Error Launching activity
Final Conclusion
I think the problem is with somewhere when we tried to 'Run' the app on second time. It does not uninstall the previous version of the app so when it found the package name already there it does not install the app then; results in error launching the activity.
I've been working on this same exact problem for the last 8 hours...you've had no issues after rolling back from 2.0 to 1.5.1?
I've noticed that, even with the error, running the app works fine sometimes.
You're not alone, brother. I'll be sure to update when I figure out the solution.
Also, what are your specs? I'm running the following:
Windows 7
AMD FX(tm)-8120 8-Core
AVD:
Android 6.0
CPU/ABI: Google APIs ARM (armeabi-v7a)
Target: API lvl 23
No accelerometer
heapSize: 64
If you want more details, let me know. A sample size of 2 is always better than 1.
I have been install the new version 2.10 just now ,and the problem seems like to be solved.So you can try it.
downgrading android version is not the curect way to fix the problem..if you like that you will lose new features of testing and developing in android studio.same kinda problem i faced previously when i upgrade to android 2.1.but i resolve my problem through restarting the android studio by selecting option of
"setting->invalid caches/restart".
Even though your problem is not fixed then try to create another avd with suitable system image.
make sure that you have downloaded a suitable system image for your emulator to run in cpu.
i solved my emulator launching problem in android 2.1 by downloading system image x86-64 with api level 23.try to download this system image if you are using 64 bit.
I had the same problem and solved it by following these steps:
Uninstall the app, in my case, from the actual hardware that is connected over the USB.
This is the key step! Uninstall the app from the "Recently uninstalled apps"
Rebuild the app.
Run it.
To fix this annoying problem I followed the three following steps:
Included the -r flag in the Install Flags. This may be
accomplished by clicking on Run -> Edit Configurations. Now
Select the General tab and type -r in the Install Flags text
area.
Click on File and select Invalidate Caches / Restart.
Uninstall earlier versions of the app. By this I mean to remove it by accessing General -> Apps and uninstall the app. Dragging and dropping the icon of the app to the trash in the home screen will not fix the issue.
There's a simple solution to this problem if you're running the app on an Emulator. This happens because of Storage space constraints. Increasing the storage space of the Emulator should solve this issue.
You can either free up some storage space from the Emulator itself or increase the storage space from the AVD Manager.
This happened to me after changing manifest permissions and trying to restart the app using AndroidStudio 3.5.1. The fix was to uninstall the app using adb and restart.
adb uninstall <your app package name>
Though I'm not sure about the exact reason for this problem, I just found a solution when I cleaned the project.
So, go to Build -> Clean project. This should help you
I had the same problem, in fact the last version of my application was disabled in the phone or emulator, to solve the problem just reactivated the application in my phone (settings-> apps-> disabled) and I recompile and the problem was solved.
I had this problem on LG-K220. It turned out that I have previously deinstalled this app, but this phone model had a system app which does not deinstall the app at first, but keeps it like in a recycle bin. No wonder Android Studio had troubles installing a new one. I completely removed the app and then it worked.
the solution is simple just uninstall package using adb command after you connect to your device
adb uninstall PACKAGE NAME
replace “PACKAGE NAME” with the name of the application you want to delete and press “Enter.”
In my experience this error occurs when you manually uninstall your apk when it's building or installing via android studio.
In a such case I simply create a apk and install it on the AVD or phone. After It will work as usual.
Hope this will help to someone.
Maybe you just set your phone or emulator to refuse all the requests of installing apk through USB.
Open your phone setting and change this to allow the installing. The problem is solved.
Hope it works for you!
I tried almost every solution found in the community, but the Error Launching activity never gone. Now I found what's the reason of my case.
I use a USB connected LG K20 Plus phone to test my projects built on the Android Studio 2.3.3, the Error Launching activity will appear if I uninstall the project in the phone, it will launch normally again if the deleted project is reinstalled.
I hope this will help people having the same or similar Error in your developing projects.
I am having a problem in running my app in Emulator. There are no errors or warnings in the code, its running perfect in device, but when it comes to emulator, it always crashes and the error message would be like this
[2012-01-16 16:13:55 - MyApp] Failed to install MyApp.apk on device 'emulator-5554!
[2012-01-16 16:13:55 - MyApp] (null)
[2012-01-16 16:13:55 - MyApp] Launch canceled!
I have tried the following things:
Run configurations > Target > Wipe user data > Run
Uninstalling the app and run it again
Restarting the emulator
adb kill-server && adb start-server
Creating a new Emulator and running the app in it
Restarting ADB
Restarting Eclipse
Starting the Eclipse after the emulator is launched completely
Increasing the ADB connection time-out to 1000
Restarting the System
Deleted the emulators and created new emulators and run in it after they are completely loaded
I don't know what else should I do. Sometimes if I run in a new Emulator the app runs for the first time and if I run it again after sometime, its the same crash report. I am not able to understand what is the problem.
Can anyone please suggest me what should I do now and where is the problem?
The Emulator used to work well before. This problem started a few days back.
Any help will be appreciated. Thanks All.
Have you defined all of your Activities correctly and completely in AndroidManifest.xml?
Can you paste the definition of your AndroidManifest.xml here?
Try that.
More possibilities:
Real refresh of AVD. It is funny, but Eclipse remembers your emulator. And if you turn it off and on it will be the same old good (or bad) one. You could reinstall all Eclipse for a real refresh. Or use a shorter, but tricky way. Change the max VM app heap size of the emulator. (Android SDK and AVD manager - Virtual device - Edit) Create it. Now you have a brand new emulator. Funny, isn't it? Now you can change the heap size back, if you wish.
Really, I think, you can maybe change any emulator parameter for the effect. Only I stumbled upon it by heap size and stuck to do it this way.
Try to repair the path.
Set the path environment variable with the path of "platform-tools" and "tools" found in the "sdk-home".
On windows(vista):- 1.Go to "Control Panel\System". 2.Select "Advanced System Settings". 3.Select the "Environment variable". 4.Set the path environment variable under the system variable with values "SDKHOME\platform-tools;SDKHOME\tools". Where "SDKHOME" is the home folder of Android sdk.
Check,if APK version of the application sits with that of the
emulator.
Try to set a longer waiting time for launch.
Increase AVD heap and SD card
Maybe, it would be good to try to recall all the changes that were done before the problem appeared?
Oh! One more: Don't you have by accident simultaneously launched emulator and connected device? If you have the same application (ssame name) on both, they could conflict in a similar way! They simply won't let each other to be launched
If nothing helps:
I was already so tired of Eclipse errors, that I have installed the IntelliJ Idea IDE, too. Now, if for the same project applications behave idself differently on both IDES, the problem is in IDE setting or emulator. If the problem is the same on both, I look for a bug in my application or the external device. Once I had a problem in OS - had to restart Linux. But in your case it is the most probable, that the problem is in AVD. I am afraid, the only variant you haven't try yet is to reinstall Eclipse. Uninstall, remove everything from the application except code, layouts and Manifest, and install Eclipse anew. Or make other Eclipse installation, with its own workshop. You can try the last version. But if the problem is in some setting, you can set it again...
Sorry, I have put here all methods I used or found.
here you can find a similar problem and the proposed accepted solution:
Honeycomb preview - can not install my app on emulator under Eclipse
I hope this helps.
This could be due to Antivirus/Firewall software installed on your PC. Have you tried to disable it?
You should also ensure that versions of Eclipse, ADT and Android SDK are up-to-date and compatible. Have you tried to contact update sites in Eclipse and in Android SDK manager? By the way, what versions of the that software do you use?
Let's go step by step.....
1º- You should try to start the emulator without the application installed.
2º- Once it is running correctly, try to install another .apk(like for example one default one....)
3º- Now, try to run the .apk. If the problem continues, try to delete the current VM and install another new one.
Can you see Emulator in "adb devices"? If yes, can you install any .apk?
If not - you have propablly something wrong with sdk
As some people have answered already partly. Make sure of a couple things which are very important specially because of the latest Android tools releases which requires.
The latest eclipse version. Yes, very very important:
http://www.eclipse.org/downloads/packages/eclipse-classic-371/indigosr1
Make sure you update the Android ADT plugin for eclipse:
http://developer.android.com/sdk/eclipse-adt.html#installing
I've encountered similar issue and that was what has helped. Restart your computer too possible?...
Use command prompt to start emulator
emulator.exe -avd google2.2 -scale 0.7 -dns-server 8.8.8.8
it may help you.
try cleaning your project or deleting the .APK file in the bin directory of your project.
I have created a sample Hello World program in android it was working fine till now. But suddenly I found that my application cannot run in emulator. I have tried with 2.1, 2.2 2.3 emulators. I found the following issue
Please ensure that adb is correctly located at 'C:\Program Files\Android\android-sdk-windows\platform-tools\adb.exe' and can be executed
I have checked in the menationed path adb is present there. Also If I double click that file I can execute the adb.
I've encountered a similar error. I have no explanation why but I may be able to help you out.
Exit out of eclipse (I assume that's what you're using).
Open task manager.
Go to the Processes tab.
Kill the process adb.exe.
Restart eclipse and see if that fixes it.
Are you using Eclipse? Try to go to Preference an update your sdk location. Click browse and locate it again.
When i am running my application. i am getting this problem "emulator.exe has encountered a problem and needs to close. we are sorry for the inconvenience." How to handle this type error at the same time my logcat file showing empty. is any emulator installation problem? How to handle this can anybody help me.
thanks.
go to command prompt>> and cd path where your android install
cd d:\android-sdk-windows\platform-tools\
run command
d:>adb kill-server
d:>adb start-server
Have you gone through these instructions
Try Minimum API level=8 (that would be Android 2.2.)
Failing that. Note the Eclipse and JVM versions in the system requirements. I would stick with Eclipse "Classic" (3.5) if you're just trying to get your feet wet. Ensure that your JVM version is compatible.
I got a similar problem with a Xoom emulator. Not sure what caused it, but removing the AVD and recreating it solved the problem for me.
Go to "Window" - > "Show View" - > "Devices"
After this you will be able to view devices in the bottom of your eclipse. Choose View Menu option and reset your adb. That's help you.