INSTALL_FAILED_UPDATE_INCOMPATIBLE when I try to install compiled .apk on device

Question

I've compiled Trebuchet launcher from CyanogenMod 9, and trying to install it with adb:

$ adb install out/target/product/generic/system/app/Trebuchet.apk
3986 KB/s (7870141 bytes in 1.928s)
    pkg: /data/local/tmp/Trebuchet.apk
Failure [INSTALL_FAILED_UPDATE_INCOMPATIBLE]

I tried on Nexus S with CM9 and Galaxy Nexus with stock JB. Why I'm getting this error?

EDIT: In my case I've tried to reinstall system package with package manager. That's not supported, so I've got this error. Source of the error may differ in your case.

on some latest devices having multiple users facility, check if the app is installed for other users(i.e. guest login). A tester in my company was struggling with this issue for hour, when he came to me, it took 5-10 minutes also for me, to find out that the same app was installed under different guest login in that device, so wasn't getting shown on home screen or not even in settings — Shirish Herwade, Sep 16 '16 at 09:54

score 540 · Answer 1 · answered Oct 31 '12 at 15:00

540

it means the application which you want to install is already installed. just remove the old one and try again.

answered Oct 31 '12 at 15:00

Mustafa Güven

15,526
11
63
83

29

Worked for me, but I also had to reboot once too. – droidgren Jul 23 '13 at 07:28
35

I had to go into Settings -> Manage Applications to find the app and choose to Uninstall it from there as it wasn't showing up elsewhere. – David Conlisk Sep 16 '14 at 14:12
25

May also be require you to uninstall from all user accounts (my Nexus 10 had 3 users). – Tyler Kiser Apr 17 '15 at 00:04
Go to apps -> Internal memory -> uninstall the old build does the trick. – Smeet Jul 09 '15 at 18:01
Also tried this unsuccessfully: ./adb install -r Trebuchet.apk Real problem was that the app was installed for another user. – Randy Nov 19 '15 at 20:47
I factory reset my phone, and it still comes up with the same error when I try to install the apk. – zondo Oct 26 '16 at 12:14
its and issue..you can't just delete the existing app and reinstall – Ranjith HS Jan 19 '17 at 05:27
Or try: adb install -r my.apk – Berend de Boer Nov 30 '17 at 06:28
2

what if I just try to do an update of an existing app? this would remove everything my last app saved locally – miracle-doh Nov 16 '18 at 09:04
Just to add a little more for me is what that I tried to install a debug over a release version of my app which caused the issue. – Cesar Bielich Jan 11 '19 at 01:21

score 209 · Answer 2 · answered Apr 12 '14 at 11:07

209

Try

adb uninstall package-name

It works for me. I have remove my app using Titanium Backup. However,I think Titanium backup didn't removed my app totally.

answered Apr 12 '14 at 11:07

einverne

6,454
6
45
91

1

I noticed the same thing using DevDrawer. This worked. – tir38 Apr 27 '15 at 02:09
1

Thanks! This saved me from a huge unexplainable headache. Not sure how I got in this state... I'm debugging an app in Xamarin Studio and Visual Studio and it was working fine until it wasn't... oh well. – Jamie Jun 22 '15 at 04:08
1

When all else on the accepted answer failed...this worked. – DennisWelu Jul 13 '15 at 21:45
Great! Simple and easy. No need do reboot with this solution. – taciosd Jul 30 '15 at 02:54
It works for me. Before I tryied manual uninstall and reboot and nothing change, only with adb command it works. Thank you. – ricky.tribbia Sep 10 '15 at 08:07
It happened to me when I uninstalled my debug app manually via Settings. And wanted to install new app with different signature (from friends computer and/or signed with my release key). Uninstalling it again from command line was successful. Thanks for your tip. – ViliusK Mar 01 '16 at 21:50
If you have multiple plugged devices, use `adb devices` to list all the available devices and then run the following command : `adb -s [DEVICE_ID] uninstall package-name` – Jonathan F. Sep 13 '16 at 14:07
works for me too. I was having this error even after uninstaling the app normally, this solved it – diogo.abdalla Apr 03 '17 at 14:02
at least give us an example! it's not clear what the `package-name` should look like. in my case com.tapastalk.keyboard.konjugationkeyboard worked. you can use adb to list all the packages. – oliversisson Jan 25 '19 at 14:35
Worked for me: I had already uninstalled the app from the device, but somehow `adb uninstall` seems to have removed more remnants. No reboot needed. – Luc Aug 12 '20 at 08:33

score 114 · Answer 3 · edited Jun 20 '20 at 09:12

114

Uninstalling the application would be enough to avoid this problem.

INSTALL_FAILED_UPDATE_INCOMPATIBLE

but sometimes even uninstalling the message is raised again, it occurs in Android OS 5.0 +, so this is the solution:

Go to Settings > Apps and you will find your app with the message:

"Not installed for this user"

We have to uninstall manually for all users!, then we can install our compiled application with no problems.

Another options:

Remove the old application and install again.
Use Android Debug Bridge command:

adb uninstall [PACKAGE NAME]

edited Jun 20 '20 at 09:12

Community

1
1

answered Sep 21 '15 at 18:18

Jorgesys

124,308
23
334
268

2

Thank you! This is what I needed. Why and when did they start doing it this way? – Nick Nov 25 '15 at 22:35
apparently since OS 5.0 + – Jorgesys Nov 25 '15 at 22:36
1

Initially, I couldn't find my uninstalled app under Settings -> Apps. It turned out that in Lollipop 5.1.1, the uninstalled app was listed by the package name, not the app name. So, if you did an adb uninstall, and adb install still fails, look for your uninstalled app under your package name. So, com.acme.wileycoyote will be listed alphabetically under "c", not "w". – Yojimbo Jan 13 '16 at 17:56
Thanks, that works! My phone doesn't have the option "Uninstall for all users", I uninstall it by logging in all users... – DawnYu Mar 02 '16 at 17:16
Note that the app is listed at the very bottom irrespective of the alphabetic ordering !! – Avijit Gupta Apr 27 '16 at 14:10
Just needed to remove the old application and install again. Thanks – loonix Jun 05 '17 at 09:00
1

What "all users" when the user is exactly one - ME!!! Anyway, it works - upvoted. – WindRider Sep 26 '17 at 15:04
I've found the cause. This happens for apps installed through the IDE or adb and then uninstalled through the device. – WindRider Sep 26 '17 at 15:46
Your 'uninstall manually' solution, worked for me, after trying many other solutions. I also restart the phone after uninstalling manually. – Mohan Perera Jul 04 '18 at 05:18
adb uninstall command worked. – shuster Jan 25 '22 at 10:46

dharmendra · Answer 4 · 2015-05-14T11:50:02.513

23

Two ways that can be works

1: Uninstall app from mobile device manually

2: Open command prompt , trace path of adband execute following command

adb uninstall your_package_name

edited May 14 '15 at 11:50

answered Apr 08 '15 at 07:31

dharmendra

7,835
5
38
71

2

The only way which works for devices without display. – DenisKolodin Sep 06 '16 at 12:51
1

eg : "adb uninstall net.gavin.hello" where package name is on AndroidManifest.xml as "package="net.gavin.hello"" – Gavin Simpson Apr 15 '18 at 07:19

score 9 · Answer 5 · edited Dec 22 '15 at 12:15

9

go to : your adb folder \sdk\platform-tools\
type cmd
type : adb remount on command window
adb shell
su
rm /system/app/YourApp.apk
Restart your device

edited Dec 22 '15 at 12:15

Shirish Herwade

11,461
20
72
111

answered Feb 06 '14 at 07:03

user3278378

99
1
1

what does remount? can I using this keep release and debug version and mount and remount them easily? – piotrek1543 Jan 09 '16 at 21:20
2

Doesn't make much sense as user apks are not stored in `/system/app` but `/data/app` – m0skit0 Oct 04 '16 at 13:33
@piotrek1543 `adb remount` remounts system partition as read-write instead of default read-only. – m0skit0 Oct 04 '16 at 13:33

score 9 · Answer 6 · answered Feb 21 '16 at 12:49

9

The question was why he's getting this error. Uninstalling will solve this problem but in my case, while I was installing the compiled version of the apk, the problem raised. I was trying to build an update for my application. So what I did, I built a signed apk and then tried to install the apk and the apk installed perfectly. So, rather removing the old apk, I had to sign the newer update and then installed it.

answered Feb 21 '16 at 12:49

Reaz Murshed

23,691
13
78
98

1

Same here. Try to test the update process. So uninstall is not an option. – Martin Apr 10 '19 at 15:21

artem · Accepted Answer · 2018-03-16T19:34:47.820

8

I just renamed the package and it worked for me.

Or if you are using Ionic, you could delete the application and try again, this happens when ionic detects that the app you are deploying is not coming from the same build. It often happen when you change from pc.

edited Mar 16 '18 at 19:34

answered Aug 11 '12 at 00:58

artem

16,382
34
113
189

Nothing else worked for me. Thanks for the great idea! – Ken Pespisa Oct 08 '14 at 13:08
2

Too much work, I'd backup and remove apk and reinstall it. – pevik Jul 19 '16 at 13:10
didn't work on Android 6.0.1. Had to delete the app on the device and reinstall the same package. – kakyo Jun 11 '17 at 08:20
17

"I just renamed the package", **this is not work around, in fact you are creating another application!** – Jorgesys Feb 08 '18 at 19:13

score 7 · Answer 8 · answered May 12 '15 at 17:14

7

This maybe because you have more than one user in your device and you've just deleted the app on one (leaving the apk still present for the other(s)).

I've deleted in all accounts, and it worked afterwards.

answered May 12 '15 at 17:14

neteinstein

17,529
11
93
123

Do you mean Google accounts? – CACuzcatlan Sep 21 '15 at 22:20
Yes, exactly what i mean. – neteinstein Sep 23 '15 at 11:14

score 7 · Answer 9 · answered Jun 21 '18 at 10:31

This can happen if you sign your application with a different certificate. You can always use

adb install -r myapk.apk

to overwrite an existing apk on your device, but you will still get the error if you signed the new apk with a different certificate that of the installed apk.

In that scenario you would need to uninstall the apk from your device before attempting an install. However, this can also impact your application since your original signing may be tied to certain Developor API's, so you may need to update the console with your new credentials.

Mark Pazon · Answer 10 · 2015-10-18T01:25:17.083

4

If your device supports multiple users, you might have to delete the app for each account as well.

I usually use adb and that does the trick adb uninstall <your-package-name>

edited Oct 18 '15 at 01:25

answered Jul 17 '15 at 01:33

Mark Pazon

6,167
2
34
50

score 4 · Answer 11 · answered Jul 31 '16 at 08:59

4

if the APK is built in project with Android.mk file. Maybe it's because of the sign certificate has been changed.

in my problem, I have add LOCAL_CERTIFICATE := platform. as the original apk is signed without this tag.

answered Jul 31 '16 at 08:59

fordreamxin

125
1
7

This is really a comment, not an answer. With a bit more rep, [you will be able to post comments](//stackoverflow.com/privileges/comment). – Enamul Hassan Jul 31 '16 at 09:19

Sunil KV · Answer 12 · 2020-08-03T08:05:57.770

This might be Raised When the Application installed in you device as Different Signature then the Application(apk) you are Trying to install.(in easy words, earlier application is build by "System-A " and now build a Application By "System-B" and trying to install) You can solve this Issues in one or the other ways as showed Below.

Option 1:

   Uninstall the Application in your Device and install the New APK

Option 2:

Note: this option is applicable only if you have the Access to both old and new Systems via which Apk are build respecitively

if you don't want to Remove the APk or its not Allowed then you can get the Debug key, System-A and the same Debug to System-B

steps to take the Debug Key form "System-A"

Go to Terminal enter

./gradlew signingReport

you will get to know your results as Below

Variant: debug Config:
debug Store: /home/user/debug.keystore
Alias: AndroidDebugKey
MD5: CS:7B:E3:51:C5:2E:36:AA:3F:66:BA:ED:40:DB:86:25
SHA1: 2A:BB:C5:4E:64:4E:FE:12:4C:4E:2B:4E:4E:42:4E:4E:4E:4E:63:83
Valid until: Wednesday, May 6, 2048

get the "debug.keystore" file from the location showed above and transfer it to "System-B" then goto

    Android studio >> File >> Project Structure >> SigningConfigs
    set the location of the "debug.keystore" to Store File and then ok

Now build the Apk in your "System-B" and Run it will work

score 3 · Answer 13 · edited Oct 10 '12 at 12:03

3

I installed Astro file manager and searched for a previous version of the apk-file, found one on the sdcard and deleted the apk-file using Astro file manager.

edited Oct 10 '12 at 12:03

jonsca

10,218
26
54
62

answered Oct 10 '12 at 12:00

fll

39
2

score 2 · Answer 14 · answered Oct 23 '14 at 01:45

In my case there was no version of the App I could find through device manager or Astro.

What I ended up doing was:

1) Download the latest version of the App from the app store

2) The app was still not visible in device manager until I restarted my device.

3) Remove the app from device manager

4) Run my project again

5) Everything works

Hope this helps someone

score 2 · Answer 15 · answered Mar 09 '19 at 03:44

C:\android-sdk\platform-tools\adb.exe: Command failed with exit code 1

Error output: adb: failed to install app\platforms\android\app\build\outputs\apk\debug\app-debug.apk: Failure [INSTALL_FAILED_UPDATE_INCOMPATIBLE: Package com.example.app1 signatures do not match the previously installed version; ignoring!]

Solution:

You already have the app app1 installed on phone (mostly download from play console, or upload key is changed)
Uninstall the app.

More details:

It's possible that you already have this app uploaded to play store using upload key, play console applied its own signature to it. That's why the app in your phone downloaded from google play does not have the same signature of your upload key.

By uninstalling app, there is no play store version of app, so mis-matches when you install a new version to you phone.

Hope that helps.

score 1 · Answer 16 · answered Apr 07 '15 at 21:43

1

Go to Setting/Apps/ Search for your app and unistall...

It´s worked for me

answered Apr 07 '15 at 21:43

Luis Colomé

101
2

score 1 · Answer 17 · answered Aug 08 '15 at 16:57

1

Go to Setting/Apps/ Search for your app and uninstall...
open command prompt and "adb uninstall "

It´s worked for me

answered Aug 08 '15 at 16:57

jettimadhuChowdary

1,058
1
13
23

score 1 · Answer 18 · answered Nov 23 '15 at 06:43

In my case, I have installed Application from Playstore and after when I am trying to run from Eclipse or Android Studio so it will try to install again on that APK that will not allow.

So First of all you have to Uninstall that Siged APK and after that you have to try.

Thank you.

score 1 · Answer 19 · answered Jan 11 '17 at 20:37

1

For MIUI users, apart for usual USB debugging option be sure to enable these settings as well:

Install via USB
USB debugging(Security settings)

then accept the prompt when you try installing app again.

answered Jan 11 '17 at 20:37

stevyhacker

1,847
2
23
31

score 1 · Answer 20 · answered Dec 30 '17 at 14:02

1

I got the same issue and did following to fix it.

Settings > Storage > Clear Cached Data
Settings > Apps > Uninstall the apps showing there. I had uninstalled my apps but it was showing there.
Restart and then everything went fine.

answered Dec 30 '17 at 14:02

Pankaj

5,132
3
28
37

3

The 2nd point helped. In my case the app wasn't installed for current user but was installed for other users. So, I clicked on the app in Apps list and inside the details page, clicked on More button (three vertical dots). There, it had an option 'Uninstall for all users'. That did it for me. Thanks! – Harisewak Sep 01 '18 at 05:07

score 1 · Answer 21 · answered Jul 08 '19 at 19:08

1

I just spent an hour trying to debug this and then realised that i was connected to my emulator instead of my phone. So even though i had succesfully deleted the app on my phone it was still failing. Stupid mistake but maybe this will help someone else.

answered Jul 08 '19 at 19:08

Adam Katz

6,999
11
42
74

Doing the same stupid mistake but opposite to what you are doing. I was trying to install on my emulator while my phone was also connected. – Ahmad Gulzar Sep 15 '22 at 07:45

score 1 · Answer 22 · answered Dec 28 '19 at 14:43

1

Samsung Galaxy Phones has a feature Known as Secure Folder Removing App from That Solved The problem for me.

also adb uninstall packagename can Not remove App from Secure folder.

answered Dec 28 '19 at 14:43

Saeed Arianmanesh

1,269
2
22
33

score 1 · Answer 23 · answered Aug 11 '20 at 20:46

You have to sign your application and then run it!

If you are preparing a new update for your application, it is not a problem to continue working. In the end, before releasing the prepared version, when you sign the application, the problem will be solved and users will have no problem installing your application.

score 0 · Answer 24 · answered Feb 17 '16 at 07:04

RankoR@ you must have installed the application from a different computer. in my case thats where the problem arose .. all you need to do is just uninstall the application and reinstall it or run it from the computer you are working .. this might be a late reply but it will help some one .. thanks

score 0 · Answer 25 · answered Jan 14 '18 at 16:29

It happened to me when I installed a dev build using Instant Run, and uninstalled from Google Play. For some reason the data from Instant Run is still in the device and can't install/uninstall the app again.

Only way to fix it: - disable Instant Run in android studio - install from android studio (it should work only from here) - uninstall app

now it should be clean to install from Google Play or adb.

score 0 · Answer 26 · answered Mar 26 '18 at 10:29

0

its occurred if you build your apk from some other PC and update it from different PC.

answered Mar 26 '18 at 10:29

Prashant Jajal

3,469
5
24
38

1

What is the solution for this case? – dpaksoni Jul 17 '19 at 05:08

score 0 · Answer 27 · answered Jun 25 '18 at 15:43

0

If your Manifest file has this line -

android:sharedUserId="android.uid.system"

is causing this error! just comment this line and you are good to go!!

answered Jun 25 '18 at 15:43

DesignIsLife

510
5
11

score 0 · Answer 28 · answered Oct 24 '19 at 10:45

I don't see anyone mentioning my case so let me add it - it happens when you build the app in one mode (e.g. Dev) and then try to override it with a different mode (e.g. Production).

The solution is the same as for the other cases - delete the app on the device/simulator and run again.

score 0 · Answer 29 · answered Oct 29 '19 at 15:48

If you are attempting to debug from a different computer than you were originally you will get the dreaded INSTALL_FAILED_UPDATE_INCOMPATIBLE error. However, there is a way to proceed without uninstalling the app and losing your data.

To see how to transfer the debug.keystore that is required so you don't get the message "The device already has an application with the same application but a different signature. In order to proceed you will have to uninstall the existing application." (and lose your data). See Update the app in another machine with same debug.keystore in android

score 0 · Answer 30 · answered Oct 23 '20 at 05:21

0

you just run adb uninstall {{package_name}}. That's it. Now you try the build.

answered Oct 23 '20 at 05:21

Karthikeyan Ganesan

1,901
20
23

score 0 · Answer 31 · answered Aug 09 '21 at 13:09

WORK PROFILE / WORKSPACE

Don't forget that, depending on which user account you have on your phone (like a Google Workspace -G Suite Account profile with Device Management set to advanced) may generate a Workprofile to your phone.

90% of people have it but don't even know it. You normally see the Workprofile on the All app view. Is litterally like a separate workspace with separate Apps.

You can recognize when you are browsing app from Workprofile if they have a little lock of luggage. Anyway :

You must delete the App from the Workprofile As well!!!

score 0 · Answer 32 · answered Sep 02 '22 at 08:52

0

In my case I'm getting this error but the app is not showing in the emulator. In that case try uninstalling apk useing adb command

adb uninstall <package-name>

answered Sep 02 '22 at 08:52

Nipun Ravisara

3,629
3
20
35

INSTALL_FAILED_UPDATE_INCOMPATIBLE when I try to install compiled .apk on device

32 Answers32

Another options:

Option 1:

Option 2:

WORK PROFILE / WORKSPACE

You must delete the App from the Workprofile As well!!!

Linked

Related