How to Resolve APK Installation Error: Conflicting Package Signatures: Difference between revisions

Revision as of 06:52, 15 May 2019

When you install an APK, if you meed the error message: "An existing package by the same name with a conflicting signature is already installed."

3 Reasons

There is an APK has been installed, so if you install an APK has same package name and different signature, it will notice to you, and forbid the APK to install.
APK has not be signed.
APK is signed, but the certificate is just the debug key or it can not be authenticated by APP root certificate of terminal.

Solving Steps

To reason 1, please remove the installed old APK, then you can install the new one.
To other reason, please apply certificate from wizarPOS. Please refer to How to apply app certificate
Check your key store

   Use the command: keytool -list -keystore xxxx.jks -v
   If the keystore is correct, it should include the certificate the issued by the terminal owner. The default terminal owner is WizarPOS, so if you applied from WizarPOS, your certificate list should include a certificate which issued by the        issuer "Issuer: EMAILADDRESS=support@wizarpos.com, CN=releasetestv1, OU=Testing, O=wizarpos, L=Shanghai, ST=Shanghai, C=CN", the result is like the right picture:

caption

Check the alias name of the private key

   If your key store includes some private keys, please select the right private key with alias name, the private key is that be paired with the applied certificate.

Notice

If you use an IDE tool to sign your app, please don't use the default IDE key store. You must use the key store that you have created and applied certificate.

@@ Line 1: / Line 1: @@
-== Reason ==
+When you install an APK, if you meed the error message: "An existing package by the same name with a conflicting signature is already installed."
-# There is an APK has installed, so if you install an APK has same package name and different signature, it will notice to you, and forbid the APK to install.
-# APK has not signed.
+== 3 Reasons ==
-# APK signed, but use a wrong key, not from the terminal owner.
+# There is an APK has been installed, so if you install an APK has same package name and different signature, it will notice to you, and forbid the APK to install.
+# APK has not be signed.
+# APK is signed, but the certificate is just the debug key or it can not be authenticated by APP root certificate of terminal.
 == Solving Steps==
-* If reason 1, please remove the installed old APK, then you can install the new one. If for other reason, please read the follow solved steps.
+* To reason 1, please remove the installed old APK, then you can install the new one.
-* Apply certificate.
+* To other reason, please apply certificate from wizarPOS. Please refer to [http://sdkwiki.wizarpos.com/index.php/How_to_apply_app_certificate How to apply app certificate]
-    If you have applied certificate, please ignore this step.
-    About how to apply, please refer to [http://sdkwiki.wizarpos.com/index.php/How_to_apply_app_certificate How to apply app certificate] from FAQ
 * Check your key store
@@ Line 18: / Line 18: @@
      If your key store includes some private keys, please select the right private key with alias name, the private key is that be paired with the applied certificate.
-In the last, please notice that, if you use an GUI tool to signed your app, please don't create a new key store, just use the key store that you have created when applied certificate.
+== Notice==
+If you use an IDE tool to sign your app, please don't use the default IDE key store. You must use the key store that you have created and applied certificate.