I just installed the latest 3100 build and I'm now unable to build for Android (though I can't say for sure if the problem started before 3100 because I haven't tried to build for a while, but I know it did work a few months ago).
What's happening is when I go to build, and I select the debug keystore and enter the password "android", I get the message:
"The password for the key store located at c:\program files (x86)\corona labs\corona\resources\debug.keystore was not valid, or the key store was not valid"
Now, distressingly, I get the same problem with my own keystore, a keystore that I used to sign a released game early this year. So it's not specific to the debug keystore. Which means I can't update my own game at the moment
Now,I did some googling and this seems to be a problem related to JDK installation. Indeed, I have the latest JDK installed and I have BOTH 32-bit and 64-bit installed. Everything I'm reading says Corona needs the 32-bit, so shouldn't be a problem.
I tried a couple of things. First, I removed the JAVA_HOME environment variable and I also removed any reference to Java (JDK or JRE) from the path. So, Java can't be run from a command line now. Still, Corona gives me the same error... which is weird because it makes me think it's picking up Java's location some other way - more on that later.
So, next, I added JAVA_HOME pointed to the 32-bit JDK, and added a path entry to that JDK's bin directory. Java runs now of course, but Corona has the same problem. And, even though I didn't expect it to work, I did the same with the 64-bit JDK, still no love, as expected.
Finally, I found the registry keys that seem to be associated with Java in the registry, and I updated them to point to the 32-bit JDK (even though that might break other things, I figured maybe Corona was looking at the keys to find Java) but that didn't fix it either.
Finally, I uninstalled 3100 and re-installed, but that didn't make a difference. Interestingly, things like my account information and preferences remained, so I searched the registry and sure enough, that's all stored there. So, I thought maybe Corona had cached a reference to a previously installed JDK (since I likely have updated since the last time I build for Android) but searching the registry for "corona" and scrutinizing every entry didn't lead me to anything like that.
The only thing I haven't tried at this point is uninstalling both JDKs and Corona, then re-installing just the 32-bit JDK, then Corona. But, even if that does work, it's not a suitable solution because I also need the 64-bit JDK on my system for other work, and ideally that's the JRE I'd want to be used by default.
At this point, I'm at a total loss. Can anyone offer any idea how to deal with this? I know that this has been a long-running issue with Corona, but this is the first time I haven't been able to resolve it somehow on my own. Very frustrating