Invalid keystore password error

Solar2D Android
#1

Hello all,

I am Rastislav Kiss, new in this forum and Corona. I like the idea of writing android apps in lua script, Android studio java templates are bit messy for me, so I optained free version of latest Corona sdk and trying, what can I do.

Hovever, I have one problem. When I try to build my app for Android with debug keystore, it shows me this error:

Build for Android
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.
OK

I searched for solution and found, that I need JDK 6, so I downloaded it (JDK 6.0_45), installed it (also jre 6 was installed) but nothing. Build was successful one time (surprising not directly after install, but few computer restarts), but after computer restart it did not work again. I tryed to uninstall all Java things from my computer and install only Java 6. Nothing, also after few reinstallations of Corona including registry cleaning. I wanted to write here yesterday, hovever when I wanted to copy exact error message, it not appeared, build was successful. Today it do not works again, so I am definitely asking, is there something I can do for Corona to build properly? Which keys in registry it is using for search of jdk? Because I looked to hkey_local_machine\software\javasoft\jdk, where jdk 8 hat it’s keys, but jdk 6 do not seems to be here, so how Corona is searching it?

Thanks.

Greetings

Rastislav

#2

What password are you using for the debug keystore?

Rob

#3

I’m having a similar problem.

Using Corona Simulator 2017.3068 (2017.3.31) and “android” as the password for the debug keystore as read here:

https://docs.coronalabs.com/guide/distribution/androidBuild/

Any idea what’s going on?

#4

I had the same problem. Then I signed for release build and resolved my problem…

https://docs.coronalabs.com/guide/distribution/androidBuild/#signrelease

#5

Are you on Windows or a Mac?

Can you post a screen shot if your build dialog box just before you hit the build button? Please don’t blur or gray out any fields.

Thanks

Rob

#6

@marcelrs Thanks! I’ll give that a try…

@Rob Here’s the screen capture. Thanks for looking into it.

#7

hmmm your key alias should say “androiddebugkey” try choosing another keystore and then res-electing the debug one

#8

I get the same behaviour for the debug keystore supplied and for a keystore created following the instructions at:

https://docs.coronalabs.com/guide/distribution/androidBuild/#signrelease

When I browse and select either keystore I am prompted to enter a password and this step always fails with the error:

“The password for the Key Store located at <Path> was not valid, or the Key Store was not valid”

I’ve tried generating a couple of keystores with dead simple passwords to be sure and I always get the same result.

Please advise.

#9

Are you on Windows or a Mac?

#10

@jono.tennant - My issue was caused because the jdk I had installed in my local machine was the 64bits version.

Make sure you have (and use) the x86 version for anything Corona-related. 

(“pro tip”: both versions can live in the same machine)

#11

@eduven that’ll probably be it. I’ll get the x86 version installed and give it another spin.

Damn, it even says “Locate the Windows x86 link and click it to download the file” in the corona instructions. No one else to blame.

Cheers for the responses chaps

#12

There’s always someone else to blame! :slight_smile:

I think we cold safely assume that most desktop computers with Java installed, have the 64bit version on it.

I think we could also safely assume that we don’t read manuals unless we really try. We just scan them.

Based on these two assumptions I’d say the manual could do a better job (a more prominent info block, a marquee, a blinking banner, something) at making us verify our installed jdk version.

There you go… We have a culprit! :slight_smile:

#13

x86 Java solved it for me

#14

What password are you using for the debug keystore?

Rob

#15

I’m having a similar problem.

Using Corona Simulator 2017.3068 (2017.3.31) and “android” as the password for the debug keystore as read here:

https://docs.coronalabs.com/guide/distribution/androidBuild/

Any idea what’s going on?

#16

I had the same problem. Then I signed for release build and resolved my problem…

https://docs.coronalabs.com/guide/distribution/androidBuild/#signrelease

#17

Are you on Windows or a Mac?

Can you post a screen shot if your build dialog box just before you hit the build button? Please don’t blur or gray out any fields.

Thanks

Rob

#18

@marcelrs Thanks! I’ll give that a try…

@Rob Here’s the screen capture. Thanks for looking into it.

#19

hmmm your key alias should say “androiddebugkey” try choosing another keystore and then res-electing the debug one

#20

I get the same behaviour for the debug keystore supplied and for a keystore created following the instructions at:

https://docs.coronalabs.com/guide/distribution/androidBuild/#signrelease

When I browse and select either keystore I am prompted to enter a password and this step always fails with the error:

“The password for the Key Store located at <Path> was not valid, or the Key Store was not valid”

I’ve tried generating a couple of keystores with dead simple passwords to be sure and I always get the same result.

Please advise.