Installation failed with message Failed to commit install session

Question

Getting an error message while trying to run an apk through android studio 3.4 canary 1.

Gradle plugin version com.android.tools.build:gradle:3.4.0-alpha01

Installation failed with message Failed to commit install session 526049657 with command cmd package install-commit 526049657.. It is possible that this issue is resolved by uninstalling an existing version of the apk if it is present, and then re-installing.

I have tried uninstalling the apk, restarting android studio and the device and invalidating caches and rebuilding but nothing seems to work.

This seems to be an issue with android studio 3.4 canary 1, I reverted to 3.3 beta 1 and everything works fine. — Jude Fernandes, Oct 23 '18 at 15:45
I had the same problem and found the solution here https://stackoverflow.com/a/42695197 — Adekola Akano, Nov 25 '18 at 09:26

score 30 · Answer 1 · edited Dec 09 '18 at 06:42

30

I disabled "Instant Run" in settings, and it works for me.(Android Studio 3.4 canary)

Then you can see the adb command executed in the terminal is "adb push", while it is "adb install-multiple" before that is disabled.

edited Dec 09 '18 at 06:42

Milad Faridnia

9,113
13
65
78

answered Dec 08 '18 at 16:12

ime

401
3
5

This also solves others commit install session error like `pm install-commit` and `INSTALL_FAILED_INVALID_APK` error code. – stramin May 14 '19 at 12:58
Thanks man. You saved my life. I simply don't understand why even Google launched this feature if it is not stable. Leading to time wastage of Android devs. Phew. – Perry May 29 '19 at 06:45
This worked for me today with a clean install of 3.4. Thank you! – RichieHH Jun 04 '19 at 14:41
@Jude Fernandes This does seem to be a solution (worked for me). You should try it and possibly selected it as the solution to your question. – osprey Aug 01 '19 at 18:38

score 15 · Answer 2 · edited May 26 '19 at 05:45

15

On Android studio go to build menu : Build menu

Then:

First Clean

Rebuild

run it again

*******It works well **********

edited May 26 '19 at 05:45

Abdulrahman Falyoun

3,676
3
16
43

answered May 25 '19 at 15:47

Fitsum Alemu

359
3
2

After performing the above 3 steps, It didn't work until I restarted my system! – Sri Krishna Mar 30 '23 at 17:39

score 11 · Answer 3 · answered Oct 23 '18 at 07:24

11

build->clean project
rebuild project
Delete as shown below

answered Oct 23 '18 at 07:24

initialise

211
1
3
11

1

Deleted the app/build directory alone and then run. It works fine for me. – Dinesh May 08 '19 at 08:16
1

Just doing "build->clean project" did it for me. – Veda May 11 '19 at 11:06

score 3 · Answer 4 · answered Jun 21 '19 at 09:56

3

Disable "Instant Run".

File->Setting->Build, Execution, Deployment->Instant Run-> unCheck (Enable Instant Run to hot swap code/resource changes on deploy)

and Run your Project and after that go and Enable Instant Run to use the advantages of Instant Run

answered Jun 21 '19 at 09:56

Mohammad Davari

430
3
13

1

I face this problem again,tnx myself:)))) – Mohammad Davari Jul 27 '19 at 10:17

score 1 · Answer 5 · answered Apr 28 '19 at 21:36

If you have a version of the APK installed on a device/emulator and you create a new version of the APK that compiles against an SDK above the device/emulator sdk, you get this error vs. the original "yo, you are targeting 28 and this device has 26... come one, you need a 28 device/emulator".

You have to actually turn off instant run to see the right error.

Why would you do this? Good question! I mixed up my Q vs P devices and wasted an hour trying to figure out what was going on. :P

score 0 · Answer 6 · answered Jan 03 '21 at 15:50

0

Most easy solution is, wipe data of your emulator and run project again.

answered Jan 03 '21 at 15:50

VIKAS SHARMA

76
5

Jacqueline Woods · Answer 7 · 2021-12-15T01:17:11.863

0

I had fixed this problem by getting rid of the meta data section in my manifest. I have no clue how it was added to the manifest to begin with (I'm a noob), but once I removed it from the manifest, the app loaded right up.

<Activity

... />

remove the meta data line within the manifest and it should work.

edited Dec 15 '21 at 01:17

answered Dec 14 '21 at 01:48

Jacqueline Woods

11
2

1

Your answer could be improved with additional supporting information. Please [edit] to add further details, such as citations or documentation, so that others can confirm that your answer is correct. You can find more information on how to write good answers [in the help center](/help/how-to-answer). – Community Dec 14 '21 at 07:27

score 0 · Answer 8 · answered May 28 '22 at 10:38

0

This is what worked for me

Build > Clean Project

File > Invalidate Caches & Restart

answered May 28 '22 at 10:38

abd3llatif

170
1
6

score 0 · Answer 9 · answered Dec 12 '22 at 09:41

0

Just checked In AndroidMainfest file is not complaining any issue. I have updated targetSDK version 33 and it required "android:export" flag in activity section

answered Dec 12 '22 at 09:41

Amit kumar

149
14

Installation failed with message Failed to commit install session

9 Answers9

Linked