Google Play Console - How remove an update of published application

AndroidGoogle PlayGoogle Play-Console

Android Problem Overview


i'm desperate. I published the wrong update for an app on the play store by the new Play Developer Console.

No i need to rollback my update, simply REMOVING it and re-publish the previous.

I cannot understand 2 things:

  • how remove it from the apps versions menu
  • re-publish the previous one

Please help me! Thanks in advance

Android Solutions


Solution 1 - Android

In previous versions of Google Developer Console this could be possible unpublising the last .apk and enable to production your desired version

enter image description here

but now it can´t be possible.

Note that rollbacks aren’t supported due to the app versioning requirements of the Android platform. If you need to rollback, consider launching a previous APK with a new version number. However, this practice should be used only as a last resort, as users will lose access to new features and your old app may not be forward-compatible with your server changes or data formats, so be sure to run alpha and beta tests of your updates.

You can see the previous releases but you can´t enable again:

enter image description here

You need to create and publish a new release with a consecutive versionCode.

enter image description here

Solution 2 - Android

Click on Create Release Like you release a new version, but instead of uploading an apk click "Add From Library", Here you will get all the previous versions of your app, select the version you want to rollback to, then release it after review button.

Solution 3 - Android

Just build old app version with new versionCode and old versionName and publish it

Solution 4 - Android

Reviving this but for those that are looking for something similar but for Android App Bundles.

As it's not as clear cut as when doing it for .apk.

For .aab's you need to:

  1. unpack the aab (its just a zip file)
  2. decode the AndroidManifest which is a binary proto message with protoc
  3. to decode you will need the .proto file found in the aapt2 tool
  4. alter the version code/version name of the decoded android manifest
  5. encode it again with protoc using the .proto files used in step 2
  6. pack the aab with zip, but be careful not to zip directories and to remove the path prefix that you might add unwillingly
  7. sign the zipped file with your store credentials, using jarsigner
  8. zipalign the signed zipped file
  9. rename the zipped, aligned and signed to the final .aab file

You can find these same steps in the following gist, with some of the work prepared before hand.

https://gist.github.com/Farious/e841ef85a8f4280e4f248ba8037ea2c0

I tried to avoid hardcoding anything and to bulletproof it, but it might not be yet.

Solution 5 - Android

in play store classic version , developer console gives an option for Halt rollout . if you will Halt rollout than current version of your app , will be unpublished from play store. Now we can published new version of app.

Attributions

All content for this solution is sourced from the original question on Stackoverflow.

The content on this page is licensed under the Attribution-ShareAlike 4.0 International (CC BY-SA 4.0) license.

Content TypeOriginal AuthorOriginal Content on Stackoverflow
QuestionSimone CampagnaView Question on Stackoverflow
Solution 1 - AndroidJorgesysView Answer on Stackoverflow
Solution 2 - AndroidVaishakhView Answer on Stackoverflow
Solution 3 - AndroidIgor KostenkoView Answer on Stackoverflow
Solution 4 - AndroidFábio ReisView Answer on Stackoverflow
Solution 5 - AndroidImran khanView Answer on Stackoverflow