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

Latest revision as of 03:17, 8 April 2024

Please visit new link of same subject:

https://smartpossdk.gitbook.io/cloudpossdk/faq/other-development/resolve-apk-signature-conflict

We're making a move! Our site's content is migrating to a new URL, to provide you with an enhanced browsing experience. Please update your bookmarks accordingly. Thank you for your continuous support!

@@ Line 1: / Line 1: @@
-== Reason ==
+{{Migrating|https://smartpossdk.gitbook.io/cloudpossdk/faq/other-development/resolve-apk-signature-conflict}}
-* APK has not signed.
-* APK signed, but use a wrong key, not from the terminal owner.
-== Solving Steps==
-* Apply certificate.
-    If you have apllied certificate, pleaes 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 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:
-[[File:Keystorelist.png|500|right|thumb|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.