This is an interesting thread. If I’m reading this right, you’ve experienced an issue with a existing android certificate + the new build process that uses 64-bit JDK essentially causing Google to say “Hey this binary is not using the right certificate.”
I’m wondering if re-creating the certificate with the updated JDK will fix this.
Maybe I’ve misunderstood?
In any case I’m looking forward to more discussions on this.
Hey roaminggamer, with recreating the certificate, is there any guide out there on how to do this?
Look at the last post in this thread:
https://forums.coronalabs.com/topic/71172-android-build-failed-1/
It contains a keytool command that seems to help update the keystore to a modern encryption.
Rob
I have the same problem as the OP.
Trying to upload the game to google play results in:
"Upload failed
You uploaded an APK with an invalid signature (learn more about signing). Error from apksigner: ERROR (Jar signer ALLTHUMB.RSA): JAR signature META-INF/ALLTHUMB.RSA uses digest algorithm SHA-256 and signature algorithm RSA which is not supported on API Level(s) 15-17 for which this APK is being verified"
I’m using 2017.3189 and jre1.8.0_151 (although the original .keystore file was probably not generated with this version).
I’ve tried to follow the link above, but the last post seem more of a question than a tip if you ask me… And following it doesn’t seem to result in anything new written to disk.
keytool -importkeystore -srckeystore mystore.keystore -destkeystore newstore.keystore -deststoretype pkcs12 -srcstorepass storepass -deststorepass storepass -srckeypass keypass -destkeypass storepass -srcalias keyalias
Should create a new keystore called “newstore.keystore”.
Rob
Hi Rob, thanks for your input on this, i dont want to post again in the other thread as i know you are redirecting people to that one, so i will ask here. when i run the command using jdk1.8.0_152:
C:“Program Files (X86)”\Java\jdk1.8.0_152\bin\keytool -importkeystore -srckeystore mygamename.keystore -destkeystore mygamenameB.keystore -deststoretype pkcs12 -srcstorepass storepass -deststorepass newpass -srckeypass storepass -destkeypass newpass -srcalias yourkeyalias
it comes up with an error: Illegal option: files
If i run the same thing using jdk1.6.0_45 It works and creates the new keystore mygamenameB.keystore.
C:“Program Files (X86)”\Java\jdk1.6.0_45\bin\keytool -importkeystore -srckeystore mygamename.keystore -destkeystore mygamenameB.keystore -deststoretype pkcs12 -srcstorepass storepass -deststorepass newpass -srckeypass storepass -destkeypass newpass -srcalias yourkeyalias
Some interesting (maybe?) info.
On my other PC (using 2017.3184) I can build and upload the .apk to play store with zero problems. All my files in the project (source as well as .keystore files) resides in a “Google Backup and Sync” folder and are thus the same on the two PCs.
So simple logic says that the .keystore is not the (entire) problem.
Not sure which java version Corona uses though as I have several versions under C:\Program Files (x86)\Java and I don’t know how Corona “links” to the Java SDK.
Yes the latest public 3184 builds fine and accepted on play console, it’s the latest daily build which encounters this problem, it builds fine , runs fine on phone, but when uploading to play console runs the above error… I think now going forward we need to upgrade our keystores, but as mentioned in in having trouble doing that using the latest jdk. Also another question going forward with the daily builds,would the way we generate new keystores change from the way it’s documented?
I am having the same problem. What I did realize and if you can live without those users is that if you set the min SDK > 17 (like 18) everything works as expected. Unfortunately for me I have so many still running < 18 it isn’t an option.
Just as a small note. I created a new key and that did not resolve the problem. Only adding the min sdk to the build file did.
If it’s a problem introduced with the latest daily it surely must be an error with the SDK? I don’t see anything in the releas notes about any keystore / Android related updates.
Yes! That certainly did the trick!
I was aware that the problem was related to old API versions, but I didn’t know where to set the minimum API versions. So I was looking for this setting at the completely wrong place (at google play) and didn’t find it…
But it was right in front of my nose (in the build file)…
Thanks!
See if daily build 3193 resolves this!
Rob
Hey Rob and anyone who is interested, just uploaded a new update for my app using the latest daily build 3200 and my old keystore, and the google play console accepted the app without any problems. Cheers guys for helping on this!
Great to hear!
Rob