Install_Failed_Update_Incompatible When I Try to Install Compiled .Apk on Device

INSTALL_FAILED_UPDATE_INCOMPATIBLE when I try to install compiled .apk on device

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.

Failure [INSTALL_FAILED_UPDATE_INCOMPATIBLE] even if app appears to not be installed

I've seen this several times. Usually, it's due to having a signed release version on my phone, then trying to deploy the debug version on top. It gets stuck in an invalid state where it's not fully uninstalled.

The solution that works for me is to open a command prompt and type:

adb uninstall my.package.id

That usually completes the uninstall in order for me to continue development.

INSTALL_FAILED_UPDATE_INCOMPATIBLE when I try to install compiled .apk on device

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.

INSTALL_FAILED_UPDATE_INCOMPATIBLE shows up even after the original is completely removed

The solution is to modify the AndroidManifest.xml file. You need to remove the sharedUserId attribute in the second line.

The Reader.apk file is a system app, and it is made by the manufacturers of the device itself, who also made several other apps. Due to this, they were able to set the sharedUserId flag, which allows all of their apps to interact with each other. As a security design, all the apps are required to have the same signing key. When I tried to install the modified app, it failed to install because it was trying to share the user id with the other apps while lacking the proper signing key.

By removing the flag in the xml, you can successfully install the modified app. Change the following line in the AndroidManifest.xml file from this:

<manifest android:sharedUserId="android.media" android:versionCode="1"
    android:versionName="1.0" package="com.bn.nook.reader.activities"
    xmlns:android="http://schemas.android.com/apk/res/android">

to this:

<manifest android:versionCode="1" android:versionName="1.0"
    package="com.bn.nook.reader.activities"
    xmlns:android="http://schemas.android.com/apk/res/android">`

See this xda post for more details. (Full Disclosure: I wrote that post.)

INSTALL_FAILED_UPDATE_INCOMPATIBLE update from a playstore version to a new from AndroidStudio

This has got nothing to do with your database, this is because you're trying to install an .apk file that has a version number that is less than or equal to the version number of an app already installed on your device with the same application id.

Just increase your versionCode in your gradle.build file (or your AndroidManifest.xml if that's where you define it) and the operating system will let you install your new version without clearing the data.

If changing the versionCode doesn't fix it, then it is likely due to a conflict with the signing of the .apk like Sufian mentioned here.

The 'Generate an apk' option in Android Studio will run you through some prompts to assign a keystore to sign the .apk with, which is the manual way.

You can set up your build.gradle file to automatically sign your .apk with a keystore when you run a given flavour as your build. You can read about how to do this here.

---

Related Topics