Open smackerdan opened 6 years ago
My key in appdeck.mobi looks the same as the one Google Play Console said I used for the first release, same fingerprint. After my second release gave an error that I used a different key, I uploaded my saved key to appdeck.mobi. Again it looks the same, but now appdeck.mobi says it's invalid.. Can you please help me fix this? I would pay for support. Google won't let me post an update without it. App ID 3667. Thank you.
I would like to update my app in Google Play but I cannot due to the error above. Could someone from appdeck please help. I would be happy to pay for support.
I have the same Problem. I even can't generate a new keystore. Please help.
cert_info: cert_info_error: alias not found, available alias in keystore:
I have the same problem. Can you please help me to upload the keystore or let me know what is missing
Why is there no help? Does anybody know?
When adding APKs to my new Android release, I got Upload failed You uploaded an APK that is not signed with the upload certificate. You must use the same certificate. The upload certificate has fingerprint: [ hidden number ] and the certificate used to sign the APK you uploaded have fingerprint: [ hidden number same as my keystore SHA1 ]
My Keystore looked fine. I tried uploading the one I saved using Download Keystore. Then I got a message saying "Key store is not valid: alias not found, available alias in keystore: myappname"
Then I notice this in the Key Store File: cert_info_error: alias [b] [/b] not found, available alias in keystore: myappname