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?
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.
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
Wait several minutes (e.g. search stackoverflow for this)
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.
I solved this problem by waiting ~14 hours. Then the upload worked without changing anything in the apk. Hope this can help someone.
I ended up fixing this issue by fixing the time zone in my clock settings.
Changing the days in your system will not fix it.
This problem is your windows (or other OS) timezone.
Correct your time zone:
just wait a minute or two in most cases. The time is probably just slightly off.
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.
Just adjusting the app's availability from 25 years to 24 will solve the problem
Related
This post relates to a rapidly changing event.
I signed the app bundle with a generated key using the android studio developer built in tool. I also opted into google play key signing. When I upload the app bundle to the release, it says
"Google Play is generating and optimizing APKs from your Android App Bundle. This may take a few minutes, depending on the size of your app bundle."
But this goes on forever. My bundle is only around 2 MB. Is this normal?
This happened to me and made me stuck for several hours. Finally got the solution,
Make sure the Date and time of your computer is correct at the time of generating the signed APK or app Bundle.
Basically it causes the the certificate to get rejected by Google server, and due to some kind of bug on Google side, the error is not reported to user when user upload App bundles (AAB), but it report back error in case of APK upload
There seem to be an issue on google's side and it seems to be fixed now
I have seen these same symptoms with a different cause, which is what brought me to this question, so I'm offering another potential cause and answer, for others who encounter the situation I did.
That is, I uploaded an APK and when it reached 100% it said "processing..." and stayed in that status forever.
I researched and found this answer, but in my case it was not a temporary problem. Another user mentioned that he had determined that this also happens when posting a 64-bit APK for a release before a 32-bit APK version. Posting the 32-bit APK first works, but when I post a 64-bit APK first, it sits "processing..." forever.
Change your internet connection. I have the same problem too, I've tried using mobile data, wifi in my home but still have the same problem. And then I'm using wifi at my campus, it's so fast and finally I can upload my app bundle without stuck at processing status.
This happened to me now and it was showing "uploading" for about 15 minutes on my fibre connection, So I reloaded the page and uploaded again. It just took seconds to upload that time. So try reloading the page and trying again.
I had updated my apk file and build a new version (upgrading the versionCode and versionName).
The files was successfully uploaded on the apk 2 days back, but still it is not updated :(
Can some one pls help me.
Its still showing "Processing update" as status on the console.
I tried un-publishing the app and re-publishing the same, it made thing even worse.
Now M unable to search my application.
Tried contacting the google guys, but still no progress.
Please help
Found a similar qstn here
My android app is not being updated on the Google Play Store
For a new app you need to have patience. It may take anything from 2 days to a week. There will be reviews and automated policy checks etc happening after which it will be available on store.
By republishing you just restarted the whole process.
Usual process may take maximum one week. Here only you can do is wait till they respond.
The chances are there the app may be rejected for the update, due to some technical reason. Keep on checking the status change. Also create a query to Google.
Answered by me bellow
When I try to upload my .APK file i get this error:
Upload failed
I have tried cleaning my project, exporting it, and running it about 100 times over a span of almost 24 hours. This is just an updated version of my .APK. I have already successfully uploaded several updated .APK to the play store. I changed the Version and I am using the same keystore for this update as I have for all my other updates. Any suggestions? And sorry that this isn't a code specific problem. Also I only made a small edit to one of my activities.
The problem has nothing to do with using Chrome. The problem is your session is invalid. Using any different browser such as Firefox, Internet Explorer, Opera, etc. would create a new session and allow the upload to work.
The real solution is to just log out and back in because whatever data Google uses to verify the upload is no longer valid, but they still allow you to navigate throughout your developer account like you are logged in with a valid session.
Thank you A-C
The solution to this problem was to use firefox instead of chrome
It's not your browser. Log out and log back in again, a simple page refresh won't do. Crazy I know, but it works. You'll also find your images will fail to upload without an error message.
For me, trying to logout and login again to my account solved the problem (just as mtg168 said)
Hope it helps!
How many times have you tried?
I usually get that once in a while, and when I get it I might get it 4-5 times in a row. Play Store just sucks some times.
Retry and it should work!;o
I think the problem could be that your session has expired. I just ran into the same problem, but when I logged out and then logged back in, the upload worked fine.
May be you need to specifiy a version name different than the one provided in version 2?
In my case, I happened to change the login password before uploading the apk. Sign out and Sign back in again did help.
For me it ended being related to a newline character in my strings.xml
No error message was shown for ~8 tries then it appeared randomly. Was able to upload after changing the newline character to \n from \u000d
I am an Android developer. In part of my job I have to upload a new version of our application daily.
The problem is for nearly three to four weeks I get following error at every time when I try to upload in market.
The server could not process your apk. Try again.
After retrying for nearly 20 times the application is uploading. Can any one pls explain what's happening and whether the problem is mine or in android market.... Pls provide me a solution.
Thanks in advance.
Regards,
Sniper
Off topic: Am I the only one who is thinking that uploading a new version each day is an overkill? Are you adding new features each day?
Back on topic: There was a general problem in the market last week.
Have you changed your signing certificate?
I think the probelm was occured due to lots of different applications trying to upload in same time. Try upoading in different time.
If you are following the application upload guidelines properly i.e. managing proper VersionCode and VersionName and app signing with same keystore, than the problem could be at Android Market side.
I have also faced the problem while uploading my app on market i.e. my application is uploaded(update) to the market but the update was not visible till 5 to 7 hours.
Assuming you don't have to change anything in the apk and just hit refresh ~20 times until it works, then this implies the issue is on the server.
If you are trying to send the exact same file twice and it only works once, then the problem is almost guaranteed to be on the server.
BUT
if you change anything about the apk, it could be an issue on your side. If the file name is changed or the version code is changed, then that would most likely be the issue. Even if the apk is rebuilt between a failed upload and a successful upload, then there are other factors involved and it might not be the server.
Did you check for any empty tags in AndroidManifest.xml ? Its worth to check.
I have a draft apk, unpublished, up on the android market store and I've recently made a some fixes and minor enhancements. Every time, I try to 'replace' the current version, I get a terse message of "The server could not process your apk. Try again." towards the very end of download process.
At first, I thought it might be flaky internet connections or such. But now, I'm suspecting it may be something is wrong in my apk file.
I have the exact same manifest file, used the same build and sign process. File is just under 6MBs. I've tried doing this using both chrome and firefox.
Suggestions?
I had the same problem last week. Just waited a few hours, and tried again.
It seems replacing an unpublished apk is still broken. Removing and then uploading the apk works, but in the process it also removes in-app products associated with the application and you have to create them all over again each time. Not cool when you're doing all this to understand and test in-app billing (and you don't want to trust Google's in-app billing documentation as far as I know).