Notice: The Monaca & Onsen UI Community Forum is shutting down.
For Onsen UI bug reports, feature requests and questions, please use the Onsen UI GitHub issues page. For help with Monaca, please contact Monaca Support Team.
Thank you to all our community for your contributions to the forum. We look forward to hearing from you in the new communication channels.
Same production keystore but different SHA1 fingerprints
raj wilson last edited by
I have been publishing my apps to the Playstore above 3 years using monaca. But last week I tried to publish the apk but the Playstore restricted my upload by responding with the below message :
“You uploaded an APK that is not signed with the upload certificate. You must use the same certificate. The upload certificate has fingerprint:”
and it showed new sha1 key.
What went wrong? Please help
emccorson administrators last edited by
Try exporting the certificate from Monaca Cloud IDE and compare it with the local copy of your certificate. If you don’t have a local backup of your certificate, you might be unable to fix this problem. (And if you don’t already have a backup, make one in case this happens again.)