May be unrelated here but I created a folder to store all my app keys and I thought I’d move the debug keystore there too (for easy swapping) but it didn’t work for some reason (blank password problem). However, the same file in the standard install location works just fine and correctly loads the default password.
2017.3100 (2017.6.22)
It shouldn’t be prompting you for a password. Can I get a screen shot of it asking you?
Rob
This is debug keystore NOT IN default location
You can see it asks for password and fails if you enter “androiddebugkey”
Edit: Just FYI really Rob as this shouldn’t happen
The debug keystore should be in the Corona folder where we put it. If you move it somewhere else, we treat it as a personal keystore and you’re going to get prompted for a password… The password is “android”. “androiddebugkey” is the name of the alias, not the password.
Rob
Perception I think there… if it is called “debug.keystore” it shouldn’t matter where it is placed IMHO. Dev v framework difference.
And yes “android” as password worked just fine.
It would be handy for me to have ALL keystores in the same location and Corona know whether it was debug of production. A minor annoyance.
I only mentioned it in this thread in case it helped others.
I can do better than that: check out the video here: http://www.zammetti.com/keystore_issue.mp4 … there you can see exactly what’s happening. As soon as focus leaves the Keystore field I get the error message saying the password is invalid. Doesn’t matter whether I tab out or click something else, it’s on loss of focus generally, and it’s every time. I typed ‘android’ as the password there but it doesn’t accept it.
EDIT: Whether I check save password or not doesn’t make a difference. And, as you can see, the alias field is empty (but that’s only logical given it apparently can’t open the store for lack of password).
Engineering is suggesting that you uninstall. Then run “regedit” and clear out any Corona Labs keys that you find.
HKEY_CURRENT_USER\Software\Corona Labs\Corona SDK
and
HKEY_CURRENT_USER\Software\Ansca Corona
You can also do this from a command prompt (cmd.exe or the new power shell)
reg delete “HKEY_CURRENT_USER\Software\Ansca Corona”
reg delete “HKEY_CURRENT_USER\Software\Corona Labs”
Then reinstall… You want to get the latest build any way, we’ve fixed quite a few things since 3100. The latest is 3109.
Rob
Bad news: installed 3109 as specified, and deleted those two keys. Reinstalled and it was like a fresh installation, had to enter email/PW and everything (didn’t have to do that last time I re-installed, I assume because those keys were still there).
But, no good: same thing happens… it still asks for password as soon as focus leaves the keystore field. Exact same sequence of events 
Does anyone have an update on this? I’m running in to the same issue.
I would recommend updating to the latest daily build and trying. I believe we’ve made some changes around those areas.
Rob
It may sound silly but have you tried a reboot?
Always a good suggestion, even if your name isn’t Roy or Moss 
But yes, I did try that, more than once after making changes. No luck.
The only thing I haven’t tried yet is a complete uninstall of both Corona and JDK, followed by a re-install of just the 32-bit JDK and then Corona. I’m reluctant to do that though because, really, I shouldn’t have to.
What is your Path to JDK? Mine is *C:\Program Files (x86)\Java\jdk1.8.0_77\bin* and that works fine.
Java.exe is version 8.0.770.3
JAVA_HOME now set to C:\Program Files (x86)\Java\jdk1.8.0_131. Path set to C:\Program Files (x86)\Java\jdk1.8.0_131\bin. No other Java-related entries defined, running java from command prompt shows it’s using this JDK (also did a locate java to be safe and yep, correct one located). After a reboot, still no good. And, we’re essentially on the same version, mine’s just newer by a few point releases… could always be a breakage in a version newer than what you have, but that’s a bit of a stretch IMO.
Any other ideas?
Did you find a solution for this? As I’m running into it myself too. Same specifications, same JDK version, etc.
Can you remove the 64 bit version and try?
Hi,
I’m getting the same problem. Tried to make an update on Google Play and got the following error message when trying to upload the APK:
You uploaded an APK with an invalid signature (learn more about signing). Error from apksigner: ERROR (Jar signer IAPPS.RSA): JAR signature META-INF/IAPPS.RSA uses digest algorithm 2.16.840.1.101.3.4.2.1 and signature algorithm 1.2.840.113549.1.1.1 which is not supported on API Levels [[15, 17]]
Have you found a solution?
Thanks in advance!
Hi Impossible (and Rob);
I had exactly the same problem building and uploading an app update to Google Play from my Mac about 3 weeks ago. Since I could find no mention of anything similar on this forum at that time, I tackled it with a lot of poking around and research on my own. The fix I found (for building from my Mac running Sierra) was a complete uninstall of Java SDK 1.8 and install of Java SDK 1.6. Once I was back to building using SDK 1.6, submission to Google went perfectly.
Note that I tried all of the mundane stuff such as building the app update with different Corona builds (3007, 3012, 3085) and lots of the other normal voodoo without any success in fixing the problem. From my research, it was definitely a Java SDK thing having to do with security hashes and signing.
Here was my upload error message from Google (about 90% similar to yours).
=======================================================================
Upload failed
You uploaded an APK with an invalid signature (learn more about signing). Error from apksigner: ERROR (Jar signer ADVERKEY.RSA): JAR signature META-INF/ADVERKEY.RSA uses digest algorithm 2.16.840.1.101.3.4.2.1 and signature algorithm 1.2.840.113549.1.1.1 which is not supported on API Levels [[10, 17]]
=======================================================================
Now a topic for Rob to contemplate. This is what threw me the most about the whole thing:
-
On about June 16th, I did an update build of a different app (Just Jumble) using Corona Build 3007. Google analyzed it and accepted it without any errors. It used the same KeyStore/signature as the update I would do next. My Mac had been upgraded to Sierra prior to this and I “think” I was using Java SDK 1.8. I can’t remember changing/upgrading Java any time recently.
-
June 30th, two weeks later, was when I did the subsequent update build on the app Just 2 Words using Corona Build 3007. again, I don’t “think” anything of significance (same Sierra and same Java SDK 1.8) changed on my Mac in those two weeks. And yet, Google gave me the error that we are talking about now.
This all makes me wonder if something changed in those 2 weeks in one of two places: #1 - Google’s App Analysis Tools that analyze submitted apps. #2 – Corona’s Build Process and something in the process related to keystone/signature.
And finally, an aside to contemplate that also relates to Java SDK version. The update I made back on June 16 (with Java SDK 1.8) has generated about 6-8 e-mails from users reporting “Unable to Install - 103” errors. There is another thread in the Corona Forums now on this problem and Googling will bring up some info from non-Corona developers who are also seeing this. The fix for this seems to be to NOT build with Java SDK 1.8 because of some security hash incompatibilities on certain older Android devices running certain Android versions. I’m about to do an interim update of the app we updated back on June 16th in order to build it with Java SDK 1.6 and get back on those devices.
Hope this info helps.
Steve
Hi Steve,
Thanks a lot for the detailed answer
I will give it a try a tell you if it works for me.
Cleverson