How to Deal with Install_Parse_Failed_Inconsistent_Certificates Without Uninstall

How to deal with INSTALL_PARSE_FAILED_INCONSISTENT_CERTIFICATES without uninstall?

It means the new copy of your application (on your development machine) was signed with a different signing key than the old copy of your application (installed on the device/emulator). For example, if this is a device, you might have put the old copy on from a different development machine (e.g., some other developer's machine). Or, the old one is signed with your production key and the new one is signed with your debug key.

INSTALL_PARSE_FAILED_INCONSISTENT_CERTIFICATES when install app for the first time

Maybe it's not signed correctly? Try to build it with Eclipse or the SDK Ant tasks and compare the APKs. Or use jarsigner to check the signature and make sure it's what you expect.

INSTALL_PARSE_FAILED_INCONSISTENT_CERTIFICATES on adb install

The problem is that the apk files (during Eclipse and ant build) have been signed with different certificates. To make the signatures consistent between builds that have been built on different machines, place the debug keystore in version control:

• Use keytool-importkeypair to make the key/certificate pair:
  https://stackoverflow.com/a/4257367/1097104
• Place the created keystore file in version control
• Set Eclipse to use the file: Windows > Preferences > Android > Build
• Set ant properties to use the file: https://stackoverflow.com/a/9019925/1097104

This is handy if you tend to cross-install builds from your own machine and build machine.

What is INSTALL_PARSE_FAILED_NO_CERTIFICATES error?

Did you edit the AndroidManifest.xml directly in the .apk file? If so, that won't work.

Every Android .apk needs to be signed if it is going to be installed on a phone, even if you're not installing through the Market. The development tools work round this by signing with a development certificate but the .apk is still signed.

One use of this is so a device can tell if an .apk is a valid upgrade for an installed application, since if it is the Certificates will be the same.

So if you make any changes to your app at all you'll need to rebuild the .apk so it gets signed properly.

Can't upgrade Android app (INSTALL_PARSE_FAILED_INCONSISTENT_CERTIFICATES)

finally solved, changing the DATABASE_VERSION did the trick: I didn't changed the DB at all, but changing the version, with the onUpgrade method totally empty, was the solution. If any of you have this same problem, I want to recommend also this post, because it has another possible solutions to the problem. Cheers.

Installation error: INSTALL_PARSE_FAILED_NO_CERTIFICATES

This is fixed now. Should someone find themselves with the same unique project setup and bug the solution may be of some value.

The problem stemmed from the configuration of our resource directories in the POM of our test project (the project containing our unit tests). They were pointing to the resource directories of the project being tested. This set up should work so I'm going to guess that it's a bug in the Maven Android plugin that causes the resources to remain unsigned.

So the solution was to remove the references to external resource directories (I can't say why it was done that way initially but removing them appears to have no ill effects) and configure the resource directories in the standard way (taking as an example the POM provided by the maven plugin project archetype with tests).

---

Related Topics