APK signed with a certificate that is not yet vali

问题:

I'm trying to publish an app to google play, and it won't allow me, it says:

You uploaded an APK signed with a certificate that is not valid. 
You need to sign tour APK with certificate that is currently valid.

Screenshot:

How do I remedy this error?

回答1:

Solved it by changing the system date of my computer. I set it to today - 2 days and created a new keystore, tried to upload and it worked.

回答2:

I ran into this gotcha but my solution was different. My system time was valid, but maybe it was several minutes off. Anyway if you run into this message but appear to have a correct system time, here are two things I did which worked

1. Wait several minutes (e.g. search stackoverflow for this)
2. Rename the .apk.

Then try to upload again. It just worked for me the second time.

Another issue I ran into was ant release reporting that the keystore was tampered with or my password was incorrect when I signed my app. All I did was retry a second time and ant release just went through.

回答3:

I ended up fixing this issue by fixing the time zone in my clock settings.

回答4:

I solved this problem by waiting ~14 hours. Then the upload worked without changing anything in the apk. Hope this can help someone.

回答5:

Changing the days in your system will not fix it. This problem is your windows (or other OS) timezone.

Correct your time zone:

回答6:

just wait a minute or two in most cases. The time is probably just slightly off.

回答7:

I can't say the others are incorrect but they're mostly describing the same thing. The time stamp used when signing your APK was not "correct" for whichever Google uses to validate. Therefore you create signed packages in the past or future from Googles perspective, most likely future as the message indicates future tense "is not valid yet"

It's impossible to give a fixed amount of time by which we all must update our clocks by so what worked best for me was to just wait until it works.