Reason
- APK has not signed.
- APK signed, but use a wrong key, not from the terminal owner.
Solving Steps
If you have apllied certificate, pleaes ignore this step.
About how to apply, please refer to | How to apply app certificate from FAQ
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:
- 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 donn't create a new keystore, just use the keystore that you haved create when applied certificate.