INSTALL_PARSE_FAILED_INCONSISTENT_CERTIFICATES when installing the application for the first time

Question

I try to create and sign the application manually, but I continue to receive INSTALL_PARSE_FAILED_INCONSISTENT_CERTIFICATES when installing in the emulator, before I even managed to install it once.

Just in case, I tried to uninstall the application (yes, I gave the correct Java package name), but this did not solve the problem.

I also tried restarting the emulator and checking the "Clear user data" checkbox.

The name of the package includes the name of our company, so it cannot interfere with internal packages.

I did not find on the Internet any other explanations for the error, except "you have another version of the same application that is already installed," so I was kind of stuck here.

Thank!

Answer 1

Maybe it is not signed correctly? Try creating it using the Eclipse tasks or the Ant SDK and compare the APK. Or use jarsigner to verify the signature and make sure you expect.

Answer 2

I also ran into this problem, and the reason is that I already installed the same application, but signed with a different key (DEBUG key or release key). Removing the old installation manually and reinstalling enabled this.

Answer 3

This worked for me:

• go to settings
• then select apps
• select uploaded onces
• select the application and Delete for all users .

Then everything worked like a charm.

Answer 4

I already had an APK on the device> removing it to solve it> TNX

Answer 5

Today I stumbled upon this, and it seems like the act of signing the APK more than once that causes this.

When I create a standard 'ant debug' that automatically signs with the debug repository, then adds the files to the APK and resigns with the debug repository, all the steps and checks give me the expected results, but after installing the factory on the new machine - reset I get this message.

When I create the standard 'ant release', skipping the password request by pressing Ctrl-C, then add the files to the APK and cancel it using my personal key store, everything will work as expected.

You can use standard methods to create your APK files, but before you resign, you need to delete the META-INF directory inside the APK file to print it. On Linux / Mac, you can use the zip -d yourapp.apk "META-INF *" command.

One more thing: some people have reported problems performing unsign / sign operations on aligned APK files, so if you have this option, you should probably work with unaligned ones, and then zipalign as a last step.

Answer 6

For each new assembly, we run tests on the emulator. Since we wanted to start with a known configuration with each new test run, each time we create a new AVD after deleting the old one:

android delete avd -n $ {EMULATOR}
android create avd -n $ {EMULATOR} -t 26

Even on this newly created AVD, we saw:

Failure [INSTALL_PARSE_FAILED_INCONSISTENT_CERTIFICATES]

when installing both the APK for testing and the APU JUnit test.

It seems that we worked for us:

adb remove my.app.name
adb remove my.app.name.test

for the newly created emulator, although this leads to

Renouncement

Possible installation (after assembly):

[exec] 1174 KB / s (4430116 bytes for 3.683s)
[exec] pkg: /data/local/tmp/MainActivity-debug.apk
Successful execution [exec]

for testing the APK and testing the APK.

Answer 7

try to uninstall the application on the device and then run it on ice

Answer 8

This is the only thing that worked for me:

 $ adb uninstall com.example.testproj 

Hope this helps

Answer 9

• Change the package name in manifest.xml (example give = package = "com.first.rss")
• Change name in src
• Right click> Refactoring> Rename ... And specify a name.

Answer 10

Simply, if someone else got this crash and none of the above solutions work, make sure that you have disabled administrator rights for your application if you requested it.

Answer 11

Had the same problem when working with the application from multiple computers. Despite uninstalling the application from my device, the problem persists. However, I found that the package is still installed for other users on the device.

On your device, go to Settings> Applications and click on the package. Then press the menu / option button and select "Delete for all users."

This should allow the device to reinstall on your device.

Answer 12

I am having trouble completing the gradle task connectedDebugAndoidTest (or connectedAndroidTest ) against Genymotion. Running it on a regular emulator solved the problem.

Answer 13

If you have guest users on your device, switch to the guest user and check if your own application is already installed in the guest account, delete it or delete the guest user of your choice, and then run the application. Hope this helps!

Answer 14

This can happen if the package in AndroidManifest is different from the package in Java files.

Answer 15

I solved this by simply uninstalling the old application, uninstalling from the device and reassembling.