I made a necessary update to my game while the first bundle that I uploaded is still in review. How do I delete the previous release, because I don't want to waste time with 2 releases being reviewed and published? This is for my graduation project and I'm running very low on time so any help is much much appreciated.
You can't delete a release.
As your previous one is still at review stage, upload a new release. Once there's a new release avaiable for review, they won't review the older one.
Related
I have published my first release of android APP on Google Play console, Its not approved yet (Still In Review for 5 days now).
I found that the app has an error and will crash on start.
I want to discard the first release and publish the new one which contains the fixes.
I think my app still in review for 5 days now because it crashes and I want to fix it but don't know how.
If I try to publish a new release on Google Play, it says "You cannot remove all production APKs and Android App Bundles"
Any Help
I have actually uploaded an update version of an app before its first release was approved and published. (The reason was I forgot obfuscation...) It was approved and published later without problem.
But I can't understand your saying:
If I try to publish a new release on Google Play, it says "You cannot
remove all production APKs and Android App Bundles"
If you tried just uploading an update version, I can't understand why it led to remove all production.
If you didn't just upload an update version but you tried to remove or something, you might doing something wrong. But you didn't disclose detail about that, nothing could suggest anymore.
I think you just exit upload window. Find button "сontinue uploading" in versions section and upload yours's new version of application.
Some one can help me, I have a problem when upload a new version of my app, I signed with release certificate but when new version is publishied users can't see "update" option only "open" even they has previous version of app. The problem began when I sign new apks from another laptop, but always using the same certificate.
I tried sign it with previous Gradle version and doesn't works.
If you changed the app version in the gradle and the Google Play Store ACCEPTED your new app version, you should just wait 24/48 hours, sometimes it takes just a lot of time to display new uptdates. If you still not find the app update after a few of days just post some screenshots and we'll provide to help you.
Happy coding!
If this question I'm about to ask was already asked, please just direct me to the link as I didn't find it. For the beta testing in google play, do you have to first un-publish a beta APK before the new one will take its place? Also can you upload the same version code or do you have to create a new version code with each APK upload in Beta?
The reason I ask is I was about to Beta test a new version of an application. I upgraded the application on my test phone and it crashed. I found out there was a line of code I forgot to take out for testing purposes which caused the upgrade to break. Which is funny because the testing code was testing, indirectly, the upgrade code. Anyway, so I didn't want to upload a whole new code version just overwrite the pre-existing APK upload. I was hoping this was possible due to it only being in Beta status. Also, I guess this means having to potentially wait another 24 hours for his new Beta APK upload to take effect. That was another thing I was hoping to bypass was uploading the same version in Beta would wipe out the pre-existing Beta version code so the changes would be immediately upgradable. Wishful thinking I'm assuming.
Thank You in advance.
No, you do not have to un-publish your application to upload a new Beta version. However, you must increment the version code in order to release a new Beta version. The version code must be incremented, so devices that installed your application can track whether an update is available, by comparing the installed version code to the Google Play version code.
Every time you release a new version or update your application info, it could take a few hours for these changes to propagate. In my experience, it only takes about 5 hours until people start receiving the update notification. If you are really bothered by the time it takes for new versions to be available, you could use a different app distribution service, for example HockeyApp, TestFlight, etc...
When your app is ready to production, you don´t have to unpublish, just "promote to production", you don´t have to change the versionCode.
If your Beta application has bugs, made the changes and you have to upload another .apk and yes, you have to change to the newer versionCode.
If your app was published, you can´t overwrite the pre-existing APK.
I have some questions related to updating an android app on Google Play, that I seem to find the answer nowhere. I updated an app, and after aprox an hour, I noticed a problem with that new apk, so I had to create a newer update. I read on Google Docs that an update would take up to 24 hours to be surelly released to users, so if I will update it again, would that be a problem? Will the users see only the last update? Can I deactivate an update and let only the last one to be released? I appreciate any answers!
If you notice a problem in just released version, you can deactivate it and activate the previous version (you can do that in advanced mode). Some users may get the new release in the meantime though.
You can later release a new version and users will then see this new version as the upgrade.
just sign your new apk with old keystore and got o console old app console and in you may/maynot unpublish your old version.just add new apk to production and it will update in 2-3 hours.
I activated a new version of my application on Google Play approximately 3 hours ago. The information about it already been updated (description, screenshots) but the apk not yet, continue the old version. It is normal to happen?
Make sure after you uploaded the APK, you 'activate' it. Just by uploading it, changing description and save it won't update the APK itself, you are just updating the description.
What I normally do is after uploading a new APK, I update the What's New section, go back to activate the APK and then finally hit 'Save' button.
Before Google Play, the APK update is almost instantaneous. But lately, new APK updates takes at least 1 to 4 hours to get updated on Google Play website.
UPDATE: nevermind, saw you 'activated' a new version in the question.
It will take more time to update the apk, generally I have seen anytime between 1-12 hrs, depending on the time of day you update the apk. Apk is updated once or twice a day. If you are lucky to update your apk just before the internal process updates then your will see it updated very soon.
Text and Picture on the other hand are just html that is rendered, so it is updated right away.
I try to update late night before or around 12 midnight, then by next morning 9am (london time), it is updated in google play / market.
Sometimes I have updated at 8am london time and it is reflected updated by around 10am!
HTH
I had a similar issue where my tester was able to see the production version of my app in Play Store but not the new Beta version update even though it was uploaded many hours before and available to other Beta testers as an update.
I had added him as a Beta tester to my Google Group, also added as a test user in my Google Play Store account. The solution was to force stop Play Store then restart it again.
The Beta Update was available as soon as he went back into the play store and searched for the app.