[Resolved] debug.Keystore not valid or incorrect password ??

Solar2D Android
#1

Hi,

Yesterday, my last app build was ok then I go to home.
Today, I’ve code my app and now when i want to build for Android (like yesterday !)
the Corona simulator say to me:

“The password for the Key Store Located at C:\Program Files\Corona Labs\Ressources\Corona SDK\debug.keystore was not valid, or the Key Store was not valid”

I don’t have change anything, and nobody have touch my computer !!

Please HELP !! What is the problem ?
How can I make a new Keystore & password ?

(I go to hollyday tomorrow and i must build my app before !!! [for deep testing during Day off])

Thanks !
[import]uid: 18246 topic_id: 29668 reply_id: 329668[/import]

#2

PROBLEM SOLVED !

Warning, today i’ve got a Java runtime update (not JDK, only runtime) and it was the Java 7 !
For ‘patch’ the problem i’ve do that:

  • uninstall Java 7 runtime, verify i’ve got the correct JDK and reboot.

But nothing Work !

Finally, just before I burn my desk, I reinstall the JDK 6 (32bits), reboot my computer and NOW it’s work fine !!!

OUF !! [import]uid: 18246 topic_id: 29668 reply_id: 119066[/import]

#3

Thanks for updating this with your solution. As mentioned in the docs Corona doesn’t support JDK7, only 6.

Peach :slight_smile: [import]uid: 52491 topic_id: 29668 reply_id: 119071[/import]

#4

Peach, I know and I never installed JDK 7 !!

The problem just append when the update of the ‘regular’ Java Runtime 6 today.
And it’s not a Runtime 6 normal update in fact, but they upgrade automatically 6 to 7 !!

[import]uid: 18246 topic_id: 29668 reply_id: 119074[/import]

#5

Tima - this is the “900-lb Gorilla” in the room that Corona doesn’t want the Android Dev community to know about.

In brief:

  1. Corona does not work with Java 7. If you have Java 7 installed, when you attempt to do a build, you will get the password keystore error and thus your builds will always fail.

  2. Oracle does not offer Java 6 anymore on it’s website. Thus, for new users who don’t have Java 6 installed, they are officially up a creek without a paddle.

  3. The normal Java update will automatically attempt to upgrade your computer to Java 7. You must manually block all Java updates to your machine to prevent this.

Big thumbs down. This is a huge problem that will only get bigger as more people upgrade their Java environment. Android is broken for Corona.

Regrets,
Jerry Palmroos
Charlotte

P.S. I’ve submitted bug reports twice on this, and never heard a thing back. [import]uid: 151653 topic_id: 29668 reply_id: 119227[/import]

#6

Jerry, what you are stating here is not completely accurate. Let me tell you how it really works…

Yes, it’s true that Corona does not support JDK 7, but that is because Android does not support JDK 7. Android only supports the 32-bit version of JDK 6. That is where that limitation comes from.

Both JDK 6 and JDK 7 can co-exist on the same PC, including the 64-bit versions. We’ve tested this and it works. The only time builds and app signing will fail in Corona is if the JDK 7 path has been added to the “PATH” environment variable. The standard JDK installation programs do not automatically add their paths to this environment variable, so this is actually not a common issue for us and our customers. We suspect a 3rd party Java tool is adding this path to this environment variable and is the cause of this grief that you guys are facing. Regardless, we recognize that this is an issue and have written up a bug report for ourselves to address this in the future. Currently, Corona finds the path to the 32-bit version of the JDK 6 via the registry, but unfortunately, the PATH environment variable is overriding this in the final build phase.

(ie: Removing the JDK 7 path from your “PATH” environment variable will make builds work again in Corona. That’s all you have to do.)

Your comment about Oracle not providing JDK 6 on their website is completely false. Please see the link below. At the time of this forum post, you can find it under “Java SE 6 Update 34”. In fact, update 34 came out recently.
http://www.oracle.com/technetwork/java/javase/downloads/index.html

The automatic Java Update will not replace your JDK 6 installation. Both JDK 6 and 7 were designed to coexist together. Look under your “Program Files” directory and you’ll find them both. The reason is that Java apps target a specific major version. They have to because APIs do get deprecated between major versions, so this allows older Java apps to continue working on the same system. Microsoft .NET apps works in the same manner, which is why it is common to see .NET 2.0 and 3.5 on the same PC… and they both receive their own service packs.

So, I hope this clarifies things. I’m not trying to be antagonistic. I just want people to know the real facts. [import]uid: 32256 topic_id: 29668 reply_id: 119671[/import]

#7

Jerry, what you are stating here is not completely accurate. Let me tell you how it really works…

Yes, it’s true that Corona does not support JDK 7, but that is because Android does not support JDK 7. Android only supports the 32-bit version of JDK 6. That is where that limitation comes from.

Both JDK 6 and JDK 7 can co-exist on the same PC, including the 64-bit versions. We’ve tested this and it works. The only time builds and app signing will fail in Corona is if the JDK 7 path has been added to the “PATH” environment variable. The standard JDK installation programs do not automatically add their paths to this environment variable, so this is actually not a common issue for us and our customers. We suspect a 3rd party Java tool is adding this path to this environment variable and is the cause of this grief that you guys are facing. Regardless, we recognize that this is an issue and have written up a bug report for ourselves to address this in the future. Currently, Corona finds the path to the 32-bit version of the JDK 6 via the registry, but unfortunately, the PATH environment variable is overriding this in the final build phase.

(ie: Removing the JDK 7 path from your “PATH” environment variable will make builds work again in Corona. That’s all you have to do.)

Your comment about Oracle not providing JDK 6 on their website is completely false. Please see the link below. At the time of this forum post, you can find it under “Java SE 6 Update 34”. In fact, update 34 came out recently.
http://www.oracle.com/technetwork/java/javase/downloads/index.html

The automatic Java Update will not replace your JDK 6 installation. Both JDK 6 and 7 were designed to coexist together. Look under your “Program Files” directory and you’ll find them both. The reason is that Java apps target a specific major version. They have to because APIs do get deprecated between major versions, so this allows older Java apps to continue working on the same system. Microsoft .NET apps works in the same manner, which is why it is common to see .NET 2.0 and 3.5 on the same PC… and they both receive their own service packs.

So, I hope this clarifies things. I’m not trying to be antagonistic. I just want people to know the real facts. [import]uid: 32256 topic_id: 29668 reply_id: 119671[/import]

#8

@ peach

I am new to corona (just paid) and am getting the password is not valid. I have generated my keystore with JDK 6. Please help!!! [import]uid: 136978 topic_id: 29668 reply_id: 123780[/import]

#9

beech4u,

The most likely problem is that the JDK 7 path is in your “PATH” system/user environment variable. You will need to remove it. [import]uid: 32256 topic_id: 29668 reply_id: 123848[/import]

#10

Did you try remaking the keystore in case you actually put in the password wrong or the like? I presume you mean keystore password and not Corona password? (Just making sure!) [import]uid: 52491 topic_id: 29668 reply_id: 123850[/import]

#11

@ peach

I am new to corona (just paid) and am getting the password is not valid. I have generated my keystore with JDK 6. Please help!!! [import]uid: 136978 topic_id: 29668 reply_id: 123780[/import]

#12

beech4u,

The most likely problem is that the JDK 7 path is in your “PATH” system/user environment variable. You will need to remove it. [import]uid: 32256 topic_id: 29668 reply_id: 123848[/import]

#13

Did you try remaking the keystore in case you actually put in the password wrong or the like? I presume you mean keystore password and not Corona password? (Just making sure!) [import]uid: 52491 topic_id: 29668 reply_id: 123850[/import]

#14

Thanks Joshua…but could you be a tad bit more specific …what exactly am i supposed to change and where ?? Is this a setting on my computer config files or a setting within my corona downloaded software. My frustration is the lack of any meaningful documentation…and the assumption that we are all tech geniuses . Any and all step by step directions will be appreciated.
Also it would have been nice if after paying i still had access to the debug keystore for debugging purposes. [import]uid: 136978 topic_id: 29668 reply_id: 134548[/import]

#15

Thanks Joshua…but could you be a tad bit more specific …what exactly am i supposed to change and where ?? Is this a setting on my computer config files or a setting within my corona downloaded software. My frustration is the lack of any meaningful documentation…and the assumption that we are all tech geniuses . Any and all step by step directions will be appreciated.
Also it would have been nice if after paying i still had access to the debug keystore for debugging purposes. [import]uid: 136978 topic_id: 29668 reply_id: 134549[/import]

#16

Have a look at the following website. It has step-by-step instructions (with pictures) on how to get to your system’s environment variables.
http://www.windows7hacker.com/index.php/2010/05/how-to-addedit-environment-variables-in-windows-7

What I need you to do is check if the “PATH” environment variable references the JDK 7. If it does, then remove the JDK 7 path. Note that you should only delete the JDK 7 path and keep all of the other paths or else you might break other software applications that depend on this setting. If you are not confident in doing this yourself, then I suggest that you find someone who is PC savvy to help you.

Also, the debug keystore is easily selectable in the Android build window’s drop down box. You do not have to browse for it. [import]uid: 32256 topic_id: 29668 reply_id: 134570[/import]

#17

THANKS joshua!!!.. that was very helpful…I’m running Vista… but it’s basically the same setting… i will try it when i get home tonite… i also noticed last nite that my java updated itself to version 9 yikes… that will explain some… if not all my problems…lol
in regards to the debug.keystore drop-down option… when i select it it asks for a password and i supply the standard "android’ pswd but it doesn’t like that.
For now…i will assume that both my first and second issues are PATH related so I will take it one bite at a time…and report back my success/failure
ONCE again… thanks for your patience, help and expedient response…
People like you restore my confidence in corona each time i get frustrated…it’s a great product but sometimes gets frustrating when you are new and don’t know all the little idiosyncrasies related to it. I’m slowly learning…but it’s frustrating none-the-less… lol [import]uid: 136978 topic_id: 29668 reply_id: 134617[/import]

#18

Happy to help!

One more thing. Selecting the debug keystore in the Android build window should not ask you for a password. That’s definitely not normal. I’m wondering if there is something wrong with your JDK 6 installation. I think you should attempt to “repair” it, just in case.

Here is how to repair your JDK 6 installation:

  1. Go to the Windows “Uninstall a program” window under the Control Panel.
  2. Highlight the JDK 6 in the list.
  3. Click on the Repair button.
  4. Follow the onscreen instructions to repair the JDK.

Note that all a “repair” does is re-install the JDK. Windows keeps a copy of the JDK install program, so this is the easiest way to re-install it.
[import]uid: 32256 topic_id: 29668 reply_id: 134665[/import]

#19

I added the JDK6 location to my path variable
contents of Path variable
C:\Program Files\NVIDIA Corporation\PhysX\Common;%SystemRoot%\system32;%SystemRoot%;%SystemRoot%\System32\Wbem;%SYSTEMROOT%\System32\WindowsPowerShell\v1.0;C:\Program Files\Java\jdk1.6.0_31

contents of PATHEXT variable
.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH;.MSC
I then generated a new keystore called ISBN-key.keystore
Resulted in the same message
“… the password for the key Store located at C:\Program Files\Java\jdk1.6.0_31\bin\ISBN-key.keystore was not valid, or the key store was not valid…”
i enter my password and the message keeps coming back.

so in apparent frustration I resorted to using the debug.keystore as my fallback …so i re-installed the JDK6 per your instructions
I still have the same issue even with the debug.keystore…message reads as follows:
“… 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…”
when i click okay… it asks for the password… i enter the debug.keystore pswd “android” and I get the same msg back

“… 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…”
Now I’m obviously stuck and frustrated …i was always able to use the debug.keystore to play around and preview my changes on my test device but the very day/moment I decided to publish and paid for the subscription I lost the debug.keystore and have not been able to get my self generated keystore or any keystore for that matter to work.
I’m at wits end at this point… i have been screwing around with this since Thu, 2012-09-13 23:32
at this point any and all help will be appreciated. [import]uid: 136978 topic_id: 29668 reply_id: 134740[/import]

#20

The issue you are facing is with the JDK’s tools and not the keystore files. We use the JDK’s tools to access keystore files and the tools are failing us.

Honestly, I don’t what is wrong either.
Have you tried another PC?

Also, do you need the JDK 7? If not, uninstall it. You shouldn’t have to because I have a PC which has multiple JDK’s installed, but for some reason the wrong JDK tool is being selected… or it’s just not working correctly.

You can also trying install the newest version of the JDK 6 from Oracle’s website. You can find it via the below link under “Java SE 6 Update 38”. Make sure to download and install the x86 version, which is the 32-bit version.
http://www.oracle.com/technetwork/java/javase/downloads/index.html
[import]uid: 32256 topic_id: 29668 reply_id: 134745[/import]