Keystore Problem. Google play error

Solar2D General Questions/Discussion
#1

Hello guys

I ve a big problem trying to upload my apk on googleplay.

It gives me this error.

You uploaded an APK signed with a certificate that is not yet valid . You must sign the APK with a currently valid certificate

I used this method to create a keystore :

http://wildlionsoftware.blogspot.it/2012/04/creating-android-keystore-for-corona.html

In April 2014 I published an app made with corona using the same tutorial and everything worked for me. Now I m following the same steps but nothing to do. Google play doesn’t accept this sign.

Does anyone know how to solve this problem?

Thanks in advance guys.

King Regards Briesanji

#2

Please read this tutorial:

http://coronalabs.com/blog/2014/08/26/tutorial-understanding-android-app-signing/

Rob

#3

I ve already followed this tutorial I did exactly what is written there. But google play tell me that is not valid. Probably I generated the keystore with a version of jdk too recent. I don’t know what can i do…

#4

From the error message it says your certificate “is not yet valid”.

You can find out the validity of your certificate by issuing this command (replace keystoreFileName with the name of your keystore file):

keytool -list -v -keystore keystoreFileName

In the output you’ll see a “Valid from… until…” entry. Make sure the dates are correct.

#5

Everything is correct.

In clclusion I Have two PC

In the first one I ve installed jdk 1.7.0_55

In the second one jdk 1.7.0_67

I tried to use keystores made with the first pc and everything work. I created 3 keystores and all of these are working

Then I tried to create keystores with the second pc (using the same infos used to create the other in the first pc,) and no one work. Google says that are not STILL valid (I also tried to update java to the 1.8.0_20 (the last one) but nothing).

If I use this code

keytool -list -v -keystore keystoreFileName

everything seems ok.

http://imgur.com/r3Jrjrp The screenshot of my CMD

#6

The C:\temp folder may not be the best place to store these.  Once you deploy an app to Google, you have to use the same keystore again for it.

If it works on one, why not just copy the keystore files from the working machine to the non-working one?

Rob

#7

Please read this tutorial:

http://coronalabs.com/blog/2014/08/26/tutorial-understanding-android-app-signing/

Rob

#8

I ve already followed this tutorial I did exactly what is written there. But google play tell me that is not valid. Probably I generated the keystore with a version of jdk too recent. I don’t know what can i do…

#9

From the error message it says your certificate “is not yet valid”.

You can find out the validity of your certificate by issuing this command (replace keystoreFileName with the name of your keystore file):

keytool -list -v -keystore keystoreFileName

In the output you’ll see a “Valid from… until…” entry. Make sure the dates are correct.

#10

Everything is correct.

In clclusion I Have two PC

In the first one I ve installed jdk 1.7.0_55

In the second one jdk 1.7.0_67

I tried to use keystores made with the first pc and everything work. I created 3 keystores and all of these are working

Then I tried to create keystores with the second pc (using the same infos used to create the other in the first pc,) and no one work. Google says that are not STILL valid (I also tried to update java to the 1.8.0_20 (the last one) but nothing).

If I use this code

keytool -list -v -keystore keystoreFileName

everything seems ok.

http://imgur.com/r3Jrjrp The screenshot of my CMD

#11

The C:\temp folder may not be the best place to store these.  Once you deploy an app to Google, you have to use the same keystore again for it.

If it works on one, why not just copy the keystore files from the working machine to the non-working one?

Rob