Sorry your browser is not supported!

You are using an outdated browser that does not support modern web technologies, in order to use this site please update to a new browser.

Browsers supported include Chrome, FireFox, Safari, Opera, Internet Explorer 10+ or Microsoft Edge.

AppGameKit Classic Chat / I cant upload my game to googleplay with appgamekit's signing system

Author
Message
kocak
2
Years of Service
User Offline
Joined: 9th Nov 2019
Location:
Posted: 28th May 2022 15:02
When i change the app signing key from "Let Google manage and protect your app signing key (recommended)", as i was insturcted to do this by agk forum members i cant pick any option becuase they conflict with appgamekit app signing process thus i cant do the tasks that option wants. The stepts required for the both option are listed below, can someone help me to upload my game?

Export and upload a key from Java keystore

Download the Play Encrypt Private Key (PEPK) tool. Download source code
Run the tool using the command below to export and encrypt your private key. Replace the arguments, and enter your keystore and key passwords when prompted.

$ java -jar pepk.jar --keystore=foo.keystore --alias=foo --output=output.zip --include-cert --encryptionkey=eb10fe8f7c7c9df715022017b00c6471f8ba8170b13049a11e6c09ffe3056a104a3bbe4ac5a955f4ba4fe93fc8cef27558a3eb9d2a529a2092761fb833b656cd48b9de6a

For increased security, create a new upload key (optional).
Show instructions
expand_more



Export and upload a key (not using Java Keystore)

Use this code (the code performs EC-P256+AES-GCM hybrid encryption) with the hex encoded public key (a 4-byte identity followed by a 64-byte P256 point) below to create your own tool exporting the encrypted private key.

eb10fe8f7c7c9df715022017b00c6471f8ba8170b13049a11e6c09ffe3056a104a3bbe4ac5a955f4ba4fe93fc8cef27558a3eb9d2a529a2092761fb833b656cd48b9de6a

For increased security, create a new upload key (optional).
Hide instructions
expand_less

Create a new upload key and use it to sign each release, instead of your app signing key. If you ever lose your upload key, or it's compromised, you can reset it to start using a new one.

Generate new upload key. Learn more
Export the upload key certificate as a PEM file using the following command. Replace the arguments in bold.

$ keytool -export -rfc -keystore upload-keystore.jks -alias upload -file upload_certificate.pem

Attachments

Login to view attachments
Zappo
Valued Member
17
Years of Service
User Offline
Joined: 27th Oct 2004
Location: In the post
Posted: 29th May 2022 01:20
I've never had any need to go through any of that. As previously mentioned in your other thread by myself and others, it is basically a three step process.

1) When you first publish a new app, get AppGameKit to generate the signing key with a password of your choice. You do not need to do this step if you are updating an existing app as you use the same key file and password you already created.

2) Use that key and password when you export to an Android App Bundle from AGK. This applies to the new app or if you are updating an existing app on the store.

3) When you upload it to the Google Play Store you let Google look after the signing for you and they do all the work.

This has worked for me every time. I uploaded an update to one of my apps yesterday using the same key file and password I had generated when I originally uploaded it (you MUST use the same key file and password for updates) and it has already been processed, passed by Google, and the new version is live in the store right now.
kocak
2
Years of Service
User Offline
Joined: 9th Nov 2019
Location:
Posted: 29th May 2022 16:56 Edited at: 29th May 2022 16:57
I am doing all this but i get the error on the screenshot. And this is my first time uploading anything to googleplay i also tried discarding the release and recreating to upload the file again. I couldnt attach the screenshot on this message so i attached it on the below one:
kocak
2
Years of Service
User Offline
Joined: 9th Nov 2019
Location:
Posted: 29th May 2022 16:57 Edited at: 29th May 2022 17:27
I am doing all this but i get the error on the screenshot. And this is my first time uploading anything to googleplay i also tried discarding the release and recreating to upload the file again. Edit: I had tried uploading an aab file(but nothing was uploaded) before with different package name that was invalid could that be the issue? do i have to delete the project and start filling all the information again?
Zaxxan
AGK Developer
1
Years of Service
User Offline
Joined: 17th Nov 2020
Location:
Posted: 29th May 2022 22:53
That error means that the key you are using is different than the key used to sign the first upload.
kocak
2
Years of Service
User Offline
Joined: 9th Nov 2019
Location:
Posted: 30th May 2022 11:25
But like i said i have never ever uploaded anything to googleplay in my life before
Zaxxan
AGK Developer
1
Years of Service
User Offline
Joined: 17th Nov 2020
Location:
Posted: 1st Jun 2022 05:20 Edited at: 1st Jun 2022 05:21
Unfortunately I have no more suggestions then, sorry. I have found the upload process fairly straight forward but long winded. I have seen the error but only when I used the wrong key. This must be very frustrating for you.

Login to post a reply

Server time is: 2022-08-18 12:42:04
Your offset time is: 2022-08-18 12:42:04