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.
Related
Deploying a Kivy app to Google Play Store is a true pain. I spent over a week now trying to deploying the app to the Play Store, whereas I spent only 5 days developing it.
After managing to overcome all problems during the build process with buildozer, I'm facing now another problem when I want to deploy my app to google store. This is the warning I'm getting:
Unoptimised APK
Warning:
This APK results in unused code and resources being sent to users. Your app could be smaller if you used the Android App Bundle. By not optimising your app for device configurations, your app is larger to download and install on users' devices than it needs to be. Larger apps see lower installation success rates and take up storage on users' devices.
Resolution:
Use the Android App Bundle to automatically optimise for device configurations, or manage it yourself with multiple APKs.
I know It's just a warning, I can ignore it right? I thought so too, but google store is not allowing me to deploy my app. So I must somehow solve this issue so that I can finally deploy my app in peace.
Here are the steps I'm making to build my app:
I followed all these steps (signed the app with key etc...)
I even tried using jarsigner as an extra step since the steps above didn't work
I also tried using zipalign to "optimize" my app
But none of that worked. Still google store is saying I need to make a bundle android app. But I'm using kivy/python so I can't use android studio to make a bundle and I can't find in buildozer docs how I can do this or if it is supported.
My app size is 28 MB, I even tried to remove some necessary stuff just to see whether it will work. So I reduced the size to 14 MB but that didn't work either. It's really frustrating. Building apps is fun while coding but the deployment process is real headache.
Here is a link to my app in case you want to play with the code or see the buildozer.spec file. I lost hope of uploading it to Play Store, hence I open sourced it.
Edit
here is how the google play console looks in my case:
This is the first tab, where I upload the app:
This is the second tab, where I should review and then release (notice here that I can't press the roll out to production button):
As you guessed, the message you're seeing about using AAB is just a warning, it doesn't prevent you from releasing the app. You're far from the first person to be confused by it though, the google interface is quite unclear.
The actual problem is that you need to make sure all the essential information is filled in on every page of the app store configuration. In your screenshot above, pages that have been completed are marked by a green circle with a check mark. In contrast, the "Store Listing" page only has a greyed-out check mark, indicating that you need to add something there before you can release the APK.
As discussed in comments, it turned out that the missing thing was screenshots of the app, and after adding them it could be released successfully despite the warning message.
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.
We're moving to another Google Play developer account, so I faced the following problem.
App with LVL transferred to this new account returned LICENSE_ALLOW, until I've uploaded a new version with a new public key from our new Google Play account. Now it returns ERROR_NOT_MARKET_MANAGED.
I hope it's because Google Play didn't register a new uploaded apk yet (while in Developer console I see a new version) - according to Android Market Doesn't Show My New Version, but usually you must only upload an apk, even not publish, to get rid of this ERROR_NOT_MARKET_MANAGED error.
Any suggestions are welcome!
Relax people, after approx. 30 minutes after I uploaded it, app finally started to answer LICENSE_ALLOW!
So if you face the same problem, don't worry, just wait for a while.
I've been dealing with the same issue; I'm not sure it's quite a safe as "relax" though :)
Two concerns I'm investigating:
1) It seems wrong to me that LVL reports this an application error rather than a license violation. So be careful how you treat this in your policy, google's sample code implies that an app error is a developer error and is something your should either fix, or at least not penalize the user for. However if you ignore this in production builds it may provide a way for a hacker to disable your licensing by altering the app version to > the released version. (I don't know how feasible this hack is, but I have run into all kinds of crazy hacks already in CN so it wouldn't surprise me)
2) As pointed out some other threads e.g. Android "Not_Market_Managed" error this creates a problem when publishing new builds. I have not yet been able to make this turn off by saving a draft apk into gplay, so if I actually have to publish to turn this off that would be bad news as there's no way to test this without releasing.
The strange thing is I do not always get this error with new dev builds. Another post speculated that LVL has some rule like you can be +1 over the published version code without triggering it. I hit this error when I had done two released quite close to each other; maybe they are right?
but usually you must only upload an apk, even not publish
From my experience, for LVL to work, you absolutely have to publish the app, even if it's with as much as a single alpha build. (Even though the documentation says uploading a draft should suffice -- idk maybe I was unlucky and it was a temporary malfunction)
Considering #mvk's point 2)
bad news as there's no way to test this without releasing.
This can be remedied by publishing the app with no Production build -- this way the application doesn't go public but you can still test all the Play Store-bound stuff.
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).