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

From wizarPOS
No edit summary
No edit summary
Line 1: Line 1:
== Reason ==
== Reason ==
* APK has not signed.
# 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 signed, but use a wrong key, not from the terminal owner.
# APK has not signed.
# APK signed, but use a wrong key, not from the terminal owner.
== Solving Steps==
== 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.
* Apply certificate.
* Apply certificate.
     If you have apllied certificate, pleaes ignore this step.
     If you have apllied certificate, pleaes ignore this step.

Revision as of 02:24, 10 December 2018

Reason

  1. 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.
  2. APK has not signed.
  3. APK signed, but use a wrong key, not from the terminal owner.

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.
  • Apply certificate.
   If you have apllied certificate, pleaes ignore this step.
   About how to apply, please refer to How to apply app certificate from FAQ
  • Check your keystore
   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 keystore 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 keystore, just use the keystore that you haved create when applied certificate.