I have the same or similar issue. I have tried all versions of JDK and Corona.
My issue might be slightly different in that I am unable to use a keystore with my Google upload key added into it. I have been building and updating for Google Play for years, and today hit a wall, cannot update an app.
Since I last updated the app (about 5 days ago), I tried to 'update' the keystore (from a warning message in the console) -- after copying first, of course -- to pkcs12 format, but I am not sure that is relevant. I have tried backing everything out, but cannot get a build Google Play will accept -- either it says debug key or it says keys do not match.
Currently JDK 1.8.0_181, Corona 2018.3326
Lazy on my part, but I had always built Android using Debug keystore and keys. It seems that no longer works. But I have Google manage and re-sign my apps for the deployment, so loss of key is not supposed to be a problem. Or so I thought.
My problem now is getting a build signed with the 'upload' key that Google gives me to submit an app.
1. make a copy of debug.keystore (ideategames.keystore)
2. add the Google 'upload' key (upload_cert.der) to the keystore with keytool (keytool -import -trustcacerts -alias upload -file upload_cert.der -keystore ideategames.keystore)
3. Try to build the app with the upload alias
First problem: no matter what password I put on the new alias, it never works when I try to open it in Corona. So, I put no password, and then I just 'cancel' the request for password prompt, and it does not jump out.
Second problem: when the build happens, I get a 256 build error, which is 'Failed to sign the APK.'
I am wondering if it is a SHA1 vs SHA256 problem? But this is territory I am not that familiar with.
Any help? How do I get a build signed with the Google-supplied key?
BTW, the Corona help page on signing for Google Release Build (https://docs.coronalabs.com/guide/distribution/androidBuild/index.html) is...well.. kinda half-done, at best. " Supply the requested information and tap enter to sign your Android app." -- this is certainly false, as all this will do is create a keystore with one key in it, not sign the app. And when I do that, I cannot use that keystore to sign the app anyway.