I created a new android release in the Google Play Console. In the process I forgot to click the "Retain" button on the old APK. I didn't notice my mistake until I started to rollout the new release (which I immediately halted). I cannot find a way to edit the new rollout to retain the old APK from the current release. Is there way to fix this problem?
The reason I need to retain the old APK is that the new one does not support older SDKs.
You can do it by choosing Create Release, then Choose APK From Library, thus "republishing" your previous version.
To be honest, I did not think of it myself, it was suggested by Google Play support.
Related
I directly pushed an app for release via managed publishing. Releasing it will cause chaos for our users as some endpoints are incorrect. How do I remove that build and replace it with a new one?
App has been approved in managed publishing, worried that even if I push a separate build to prod track, this bad app will also get released
Trying to delete the apk does not work as the delete buttons are missing. What can I do as the app really cannot go out in this state? Is there some way to remove the app?
Just don't release it.
That's one of the advantages of Managed publishing. It's not released released until you confirm it in the Managed Publishing section.
The bad version is not released. Just upload a newer version with a fix and push it to the release track just as you did with this version.
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.
I upload wrong version in android console, but i save the last one, it is the posibility to turn back into last version?
I lost the last package, i built a new one package but it is crashing in many old devices.
thanks!
Do you mean you published a wrong apk on you Google Play publish account?
Then there's no way to completely turn back to a previous version, but you can mitigate it. Just make a new publish but instead of drag&drop your apk select it from artifact library.
It should automatically change your wrongly uploaded apk to deactivated and your previous apk to retained Any user that could have download the wrong apk will still have it but at least no more users will download it.
After doing that you should upload a new apk with a new version number fixing the problem
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.
My application is currently in alpha. On the google play developer console, I accidentally uploaded a new APK as production rather than alpha.
In advanced mode, there is a deactivate button. But if I deactivate and try to save I get the generic message "The application could not be saved. Please check the form for errors." I don't see any errors on the form. How do I deactivate?
I tried uploading a later version to alpha - that seems to work - but I don't want ANY version in Prod, as my app is not yet ready for prime time.
According to a Google customer service rep I contacted:
The Deactivate button is provided in your advanced mode when you want to support multiple APKs but when your new update supports the same number of devices as your previous APKs, the system won't allow such update. So it is required for you to deactivate the older version in order to upload your new APK.
The Deactivate button is only useful for situations where you have multiple active APKs.
Furthermore, discussing with them, there is apparently no functionality at this time that allows for you to remove APKs from the Production tab once they've been uploaded to that tab, AND there's apparently no way to enable Beta testing if your app is unpublished, so at this point it seems there's no way to undo what you've done if you accidentally upload an APK to the Production tab by mistake. The workaround proposed by the representative was to change the package name of the app, change the keystore used to sign, and create an entirely new application.
Further discussion with the representative indicated that the "error" is that you can't have a Production tab without an APK if there was one there already, but it sounds like there's a bug in that it doesn't actually report that that's the cause.
In latest play console you can goto Publishing Overview->managed publishing status-> press manage button on right then turn on managed publishing