Quantcast
Channel: LiveCode Forums
Viewing all articles
Browse latest Browse all 757

Android Deployment • Android upload_certificate.PEM file?

$
0
0
Well, would you believe it, I've locked my keystore passwords for one of my apps in an old Notes file on iOS and forgotten the password to unlock it - it's quite an old note so it predates Apples "unlock it with your face" technology so I'm kinda stuffed. I know, I know - it was a stupid thing to do and I've resorted to keeping them in a little black book again.

Anyway here's the problem. I've created a new App Signing key (as per the livecode lesson here https://lessons.livecode.com/m/4069/l/3 ... stribution and opted to create the release_keystore. Subsequently I can build the app just fine. I can also drop the .apk onto my android devices and test it all out there which is cool. My problem is that I can't upload the new release to the Google Play store because the App Signing key is different to the one used to upload the app last time.

Google fortunately provide a way to change the App Signing key via a link on the App Signing section for the app in the google play console. The problem I have is that I'm not sure what I'm supposed to enter in place of the bold text in their instructions. Is the upload-keystore.jks file the release_keystore.keystore created in the lesson? Also, what do I specify in place of upload and upload_certificate.pem?

Below is the Request Upload Key Reset screen and instructions that I'm wondering how to proceed with
Screenshot 2024-11-13 at 11.18.16.png
Google tell me I've got limited time to upload a new version because the old one was built with old Android stuff and will be retired from the Play Store within the next couple of weeks. :roll:

Has anyone else been through this process before who would be happy to fill in the blanks and advise?

Cheers,
Al.

Statistics: Posted by j9v6 — Wed Nov 13, 2024 12:28 pm



Viewing all articles
Browse latest Browse all 757

Trending Articles