Android keystore not valid

Solar2D Android
#1

Hi guys!

I am testing one Android app for some time now.

But recently when trying to build a new alpha app version, I get a following error (I am on a Mac):

The password for the alias -xxx in Keystore located at /Users/user/Keystores/xxx.keystore is not correct or the file is not a valid Keystore

Nevertheless, when hitting “OK”, I am able to complete building process, and to upload my app to Google play Alpha channel.

I am using Corona Version 2015.2731.

Subject Keystore worked for 2 weeks (no errors) :slight_smile:

Should I disregard above error, or maybe do something about it (like create a brand new keystore)?

Many, many thanks!

Ivan

#2

If you are updating an app that’s already in google play (live), you have to update using the same keystore that you created the app with. I don’t know if Alpha versions count towards this requirement.  But if the app hasn’t been published yet, you might be able to change the keystore.

Let me ask engineering.

Rob

#3

Thanks Rob.
App has not been published besides Alpha.

I assume when I am done with testing at version 2.3 for example, that I should be able to publish 1.0?
Or I should publish 2.4?

I will standby for engineering response.

Many thanks.
Ivan

#4

The engineer said its likely it built, but when you go to download it, the OS will fail to load it because the signing doesn’t match. What you can try, since you’re getting an invalid password error is to build using the provided debug keystore and then re-building with your keystore which will reprompt you for your passwords. Remember there are two passwords and they may not be the same.

Rob

#5

Hi Rob,

I tried suggested approach:

  1. Built using debug keystore first.

  2. Selected mykeystore, Corona prompt me for password entrance.

I got the same error (wrong password - cannot unlock keystore).

What should I do if I replace this mykeystore with new one (delete app from Google Play or…) ?

Is there any way to change keystore password?

Please note that Corona prompt`s me for password only once (twice is when you are creating new keystore).

I am kind of positive that I used the same password for a number of times.

I do not know why it suddenly start to bug me (maybe because I updated JDK to 8 on my Mac.)

I changed JDK to 7, but no success…

Ivan

#6

Hi Rob,

Problem solved (for now) ! :smiley:

Like this:

  1. Copied original keystore A to another location

  2. Changed keystore B (that stayed on original location) password using terminal

  3. Started Corona, and as soon as I tried to build using keystore B, Corona did not even let me to enter password (I got “not valid keystore” error).

  4. So I selected keystore A (that was on another location) and entered orignal password - it was accepted as valid this time!!!

So I do not know what the heck is going on here, because password was always the same.

Changing keystore location solved this issue (what the heck! :slight_smile: )

UPDATE No. 2.

Problem not solved after all, error persist…  :(****  :angry:

I tried to copy-paste mykeystore to Windows computer.

I got an error: “wrong alias password or JDK not found”.

I succeeded only one time (on Mac), I do not know why it accepted password as vaild that one time??

It makes no sense…

UPDATE No. 3.

On a MAC computer:

When I click “Browse” and manually navigate to mykeystore, password is validated OK :slight_smile:

When I let Corona automatically selects mykeystore, password is NOT OK (error - but I am able to build) :slight_smile:

Can you build on a Windows using keystore created on a Mac?

Hope this helps!

Thanks for your support!

Ivan

#7

If you are updating an app that’s already in google play (live), you have to update using the same keystore that you created the app with. I don’t know if Alpha versions count towards this requirement.  But if the app hasn’t been published yet, you might be able to change the keystore.

Let me ask engineering.

Rob

#8

Thanks Rob.
App has not been published besides Alpha.

I assume when I am done with testing at version 2.3 for example, that I should be able to publish 1.0?
Or I should publish 2.4?

I will standby for engineering response.

Many thanks.
Ivan

#9

The engineer said its likely it built, but when you go to download it, the OS will fail to load it because the signing doesn’t match. What you can try, since you’re getting an invalid password error is to build using the provided debug keystore and then re-building with your keystore which will reprompt you for your passwords. Remember there are two passwords and they may not be the same.

Rob

#10

Hi Rob,

I tried suggested approach:

  1. Built using debug keystore first.

  2. Selected mykeystore, Corona prompt me for password entrance.

I got the same error (wrong password - cannot unlock keystore).

What should I do if I replace this mykeystore with new one (delete app from Google Play or…) ?

Is there any way to change keystore password?

Please note that Corona prompt`s me for password only once (twice is when you are creating new keystore).

I am kind of positive that I used the same password for a number of times.

I do not know why it suddenly start to bug me (maybe because I updated JDK to 8 on my Mac.)

I changed JDK to 7, but no success…

Ivan

#11

Hi Rob,

Problem solved (for now) ! :smiley:

Like this:

  1. Copied original keystore A to another location

  2. Changed keystore B (that stayed on original location) password using terminal

  3. Started Corona, and as soon as I tried to build using keystore B, Corona did not even let me to enter password (I got “not valid keystore” error).

  4. So I selected keystore A (that was on another location) and entered orignal password - it was accepted as valid this time!!!

So I do not know what the heck is going on here, because password was always the same.

Changing keystore location solved this issue (what the heck! :slight_smile: )

UPDATE No. 2.

Problem not solved after all, error persist…  :(****  :angry:

I tried to copy-paste mykeystore to Windows computer.

I got an error: “wrong alias password or JDK not found”.

I succeeded only one time (on Mac), I do not know why it accepted password as vaild that one time??

It makes no sense…

UPDATE No. 3.

On a MAC computer:

When I click “Browse” and manually navigate to mykeystore, password is validated OK :slight_smile:

When I let Corona automatically selects mykeystore, password is NOT OK (error - but I am able to build) :slight_smile:

Can you build on a Windows using keystore created on a Mac?

Hope this helps!

Thanks for your support!

Ivan

#12

Same problem here. 

but this fix:

"

UPDATE No. 3.

On a MAC computer:

When I click “Browse” and manually navigate to mykeystore, password is validated OK :slight_smile:

When I let Corona automatically selects mykeystore, password is NOT OK (error - but I am able to build) :slight_smile:

"

Worked for me.

#13

Hi Rob,

Same problem happened to me today  :smiley:

Same fix - manually select it  :slight_smile:

#14

Same problem here. 

but this fix:

"

UPDATE No. 3.

On a MAC computer:

When I click “Browse” and manually navigate to mykeystore, password is validated OK :slight_smile:

When I let Corona automatically selects mykeystore, password is NOT OK (error - but I am able to build) :slight_smile:

"

Worked for me.

#15

Hi Rob,

Same problem happened to me today  :smiley:

Same fix - manually select it  :slight_smile: