Keystore Password Invalid

Solar2D Android
#1

I’m trying to do a test build for my game but I can’t get past key alias. The drop down is blank and when I click it it says “The password for the Key Store located at C:\Program Files(x86)\Corona Labs\Corona SDK\Resources\debug.keystore was not valid, or the Key Store was not valid.” I don’t know what to do here, I don’t know the password to my keystore.

#2

Hi Richard,

Can you please review this guide to ensure you’ve followed all of the steps? Please follow through the “App Signing” section.

http://docs.coronalabs.com/guide/distribution/androidBuild/index.html#signing

Regards,

Brent

#3

Like I said, I’ve selected the keystore in the CoronaSDK/resources folder but the KeyAlias drop down is blank so I can’t select “Debug” from the menu.

#4

I have the same problem. When I’m enter the “android” password is says “The password for the Key Store located at C:\Program Files\Corona Labs\Corona SDK\Resources\debug.keystore was not valid, or the Key Store was not valid.” too.

#5

Update JDK 1.6 to the newest version.

#6

Hi Richard,

I agree that you should reinstall JDK6. You wouldn’t be able to get to the Android Build window if the Corona Simulator was unable to find the JDK tool needed to read keystore files, so this issue suggests that the tool is failing to read the keystore file. I recommend that you repair/re-install JDK6.

Regards,

Brent

#7

Alright I have installed JDK1.6 Update 45, I uninstalled the other version I had and restarted, however I am still recieving this error.

#8

I have the same problem.  I just bought and downloaded Corona Pro (Build Version 2013.1082) and have built a new Keystore using Java 1.7.0_17-b02.  I followed the signing instructions, which by the way need to be updated to reference the correct folder names and cannot build the sample apps for debug or with the newly created keystore.

#9

Hi Richard,

Can you please review this guide to ensure you’ve followed all of the steps? Please follow through the “App Signing” section.

http://docs.coronalabs.com/guide/distribution/androidBuild/index.html#signing

Regards,

Brent

#10

Hi @ejtstoker,

It appears that you’ve installed JDK7. Please follow the directions in the guide linked up a bit in this thread. :slight_smile:

@Richard.Fyffe,

Your issue is somewhat perplexing. Are you on Mac or Windows? It’s important to note that on Windows, multiple versions of the JDK can coexist on the same machine without any problems. We’ve tested this with both a 32-bit and 64-bit version of the JDK 6 installed and a 32-bit and 64-bit version of the JDK 7 installed as well.  Corona will automatically pick up the 32-bit JDK 6 path from the registry and use the correct version.

The only known issue that we have is if the PATH environment variable is set to one of the other JDKs, then the final build step will use the wrong JDK version to sign the APK, causing it to be digitally signed wrong and prevent the app from being installed on an Android device… because Android only supports the 32-bit JDK 6. Oracle/Sun does not set the PATH environment variable when installing the JDK, but I suspect that some 3rd party Java tools do, causing this issue to come up every once in a while.

Best regards,

Brent Sorrentino

#11

ejtstoker,

You should not create a keystore with JDK 7 (ie: version 1.7) because it creates a keystore with an encryption that Android does not support.  You see, JDK 6 and JDK 7’s keytools use a different encryption by default.  Google requires that you use JDK 6 (ie: version 1.6), which is documented under their System Requirements here…

   http://developer.android.com/sdk/index.html

#12

Josh:

I cleared the computer of all Java 7 or 64-bit JDKs, reloaded JDK 1.6 32-bit and selected RSA as the method when I created a new keystore.  I re-installed Corona SDK Pro and still have the same problem.  I am running Windows 7 Professional Service Pack 1 (64-bit) with 12GB of memory.

Any additional insights would be appreciated.

Thanks.

Ed

#13

This actually happened to me not to long ago. I run two versions of JAVA. 32 bit jdk 6 for corona and 64 bit jre 7 for minecraft. Anyways I uninstalled all java enviroments through control panel/ program and features. Uninstalled corona, Rebooted,

Installed JDK 6 not JRE 6. Installed Corona and boyaa. Back and operational at least for the debug keystore. This is what solved my problem at least.

Thanks

#14

I thought I did that but I’ll try it again.

Thanks.

#15

My thanks to Method Mobile. After a few uninstalls and re-installs of both JDK 6 and Corona SDK I finally got Corona to build a test app. Now I have to fix my code to accommodate changes in the SDK.

Ed

#16

Like I said, I’ve selected the keystore in the CoronaSDK/resources folder but the KeyAlias drop down is blank so I can’t select “Debug” from the menu.

#17

I’m running windows 7 32bit and I changed my PATH variable but the problem still persists.

I tried this (deselect JRE when installed JDK right) but it didn’t work.

#18

Richard:

Here is what I did to fix this problem.

  1. Uninstalled Corona.  I even deleted the Program Files (x86)\Corona directory which was empty.

  2. Uninstalled all Java JDK

  3. Installed Java JDK 1.6.0_45 (the current version)

  4. Re-built my keystore using keytool. I made certain that I set the -keyalg   setting to RSA

  5. Reinstalled the current Corona.

  6. Built a test sample for Android and it worked with my newly created keystore.

Hope this helps.

Ed

#19

Hi,

I have this problem too. I have Java JDK 1.6.0_10 installed. Is this the cause of the problem?

Thanks.

#20

leopapilaya,

It probably is. I had to uninstall the JDK and Corona. Reinstall Corona, then install JDK1.6.0_45 then it magically recognized my keys (including the debug one).