hello guys
i recently publish my game , everything was OK until today i try to update my game
looks like signing key is changed and i want to ask , is that possible to reverse last sign key for my game? because when want to upload new version google show me up an error that sign key is changed, is that very necessary
Please read this page carefully if you haven’t yet:
https://wiki.gdevelop.io/gdevelop5/publishing/android_and_ios/play-store/upgrading-from-apk-to-aab
1 Like
hello dear @Gruk
i have already enabled Play App Signing
just i got error while updating my game and google say
Your Android App Bundle is signed with the wrong key. Ensure that your App Bundle is signed with the correct signing key and try again. Your App Bundle is expected to be signed with the certificate with fingerprint
what should i do ?
How long since the last upload? Was it apk or aab?
I believe everything is explained in the page. If you didn’t do it properly the first time, which I guess is what happens here, you’ll need to use the “old upload key” method.
1 Like
dear @Gruk
last update was 10 December
it was aab
i use old upload key every time , but when i upload final packaging to google , its show me this error
Your Android App Bundle is signed with the wrong key. Ensure that your App Bundle is signed with the correct signing key and try again. Your App Bundle is expected to be signed with the certificate with fingerprint
is there any way to use custom upload key? or any better way??
Unfortunately you would likely need to check with google on what key it is showing via what you have.
Either your old upload wasn’t signed with a custom key at all (used the default GDevelop one) and therefore you cannot update it to a custom key,.or whatever it was signed with doesn’t match (according to google).
As far as I know you cannot change the key after the first publishing to the play store, so if it was uploaded with the generic key, thats what it will always be from now on for that play store entry.
1 Like
dear @Silver-Streak
thanks for your attention
as google suggest , i changed everything in game , even game name and upload it with another logo
i checked my google play console and check all of my games : Upload key certificate
for all game is same , even while i changed name , is that ok?
only App signing key certificate is different for each game
new game with new name show me this error again
is there any problem with publishing gdevelop games?
by default , Releases signed by Google Play
when i start packaging , i use old upload key
so what is the problem exactly?
i try to rename my project ,so i changed
unique name
game name
game logo
what should i do ?
Unfortunately, I cannot give any guidance here. I’m not seeing any other reports of signing issues elsewhere on the various GDevelop communication channels (Discord, forum, github). I suppose it could be something with your key in particular.
If you haven’t already, I strongly recommend contacting google for input, but other than that we’ll see if anyone else in the community can chime in.
1 Like
If you want Google to see your project as a different project, I believe the Package name is what needs changing.
But if a different project brings the same error, the issue is elsewhere.
1 Like
thank you dear @Silver-Streak
thank you dear @Gruk
i changed package name , even game logo
i really dont know where should i check at this time
hello again guys
problem solved , i like to share here if someone else had such problem fix it quickly
so , looks like when i try to packaging , by mistake i select new upload key
then when i upload update for my game , google show up SHA1 certificate error
the only way to fix this : contact google support to reset you upload key certificate , at same time ask gdevelop support to send you “upload-key-certificate.pem” file . when google reply you by email , you can attach .pem file and reset your upload key certificate , they will reset your upload key and you can upload your new AAB bundle
- i suggest an edit for gdevelop , please add an check box in signing option(or just save latest choose) to save user choose to prevent such mistakes
thanks dear @Silver-Streak and dear @Gruk
4 Likes