I published the wrong update for an app on the play store by the new Play Developer Console.
I need to rollback my update, simply REMOVING it and re-publishing the previous version.
I cannot understand 2 things:
how remove it from the apps versions menu
re-publish the previous one
In previous versions of Google Developer Console this could be possible unpublising the last .apk and enable to production your desired version
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:
You need to create and publish a new release with a consecutive versionCode.
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.
Just build old app version with new versionCode and old versionName and publish it
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:
unpack the aab (its just a zip file)
decode the AndroidManifest which is a binary proto message with protoc
to decode you will need the .proto file found in the aapt2 tool
alter the version code/version name of the decoded android manifest
encode it again with protoc using the .proto files used in step 2
pack the aab with zip, but be careful not to zip directories and to remove the path prefix that you might add unwillingly
sign the zipped file with your store credentials, using jarsigner
zipalign the signed zipped file
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.
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.
Related
I haven't published this app yet, but I uploaded an APK with a critical bug in it by accident, and I want to replace it. Can I still just remove and upload a new APK?
My main two concerns is that 1) I will have to change the version code and version number somehow because Google already signed my old apk and 2) I already completed all of the content rating, descriptions, ads or no ads, etc. settings. Do I have to do them again or will there be some sort of problem there?
Thanks!
Update 16 Feb 2020
As pointed out by #tuexss in the comments, the Artifact Library has been replaced by App Bundle Explorer
Original Answer
You can upload a new APK with the same version code and a version number if you haven't published the old APK. All you have to do is discard the current release, go to the artifact library and delete the old APK and then create a new release from the console and upload your new APK with the same version code and version number.
If you have published the old APK, i.e., you have pressed the start rollout to production button then you need to upload a new APK with increased version code. The version number isn't mandatory to be increased in every new release although increasing it will help you track the data in a better way.
In either case, you will not have to fill out the play console details again.
Just upload the new one, and make sure to have it 100% rollout. You can see it inside the Google Play Console once it's ready to publish. As far as I know you can't delete the apk but you can put a version on top and make sure it's the one that goes in the Store.
Sometimes You won't find 'Delete APK/AAB' in "App Bundle Explorer" Please follow the steps to clean delete the accidentally uploaded APK/AAB.
Edit release -> remove AAB/APK as follows.
Save the Release.
Now the Delete button would have appeared in "App Bundle Explorer" Section.
Once I have put an APK for the beta version can I rollback the APK if it contains any changes or errors in the same version?
You can't rebuild a new version of an apk from the apk itself.
Have the app developer do the following:
Rebuild project in its previous state with higher version number (must be higher than all previously submitted versions)
Resubmit
From Google's Android "Developer Console" page:
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 not Rollback your previous APK you need to upload new version with bugs fixed..
The user can use the OPT-IN url to opt-out of the testing track, this works for both open and closed tracks :)
I'm on the review summary after my apk was uploaded. It says,
Errors
Resolve these errors before starting the roll-out of this release.
You need to upload an APK or Android App Bundle for this application.
You cannot remove all production APKs and Android App Bundles.
I've looked at various sources and am not sure what the solution is.
As you can see from the first screenshot you are deactivating your first APK (version code 1). But you haven't uploaded a new version of your APK. You can't do a release without any APKs live. You have two choices:
reactivate your old APK (Press the "Retain" (Now it is renamed to Include) button by the version 1 APK)
upload a new APK
I assume you know what you want to do.
This seems like a code version issue. update the code version 1 to 2.
check into your manifest file:
android:versionCode="8"
and increase it,
that was the problem by me.
Just discard the earlier release and add new one, the issue would be resolved.
Oh man! you are adding a second release or second version of the android app see your screenshot it says apks to be deactivated ..
see in that image actually you are deactivating the earlier version so just go to above button BROWSE FILES
https://i.stack.imgur.com/aNF1C.png
Click BROWSE FILES and then select your apk file....
Now make sure that you are selecting a version 2 apk i mean not the same which you are deactivating that was version 1 or earlier version
You need to upload an APK or Android App Bundle for this application.
You cannot remove all production APKs and Android App Bundles.
It means that you have not selecteed any apk till now so just click BROWSE FILES and select apk file and you have to change the version also because you are adding a another version
look closely at your image
and for changing the version go to
Build gradle file of your app and see the version number you have to increment that by 1 or any positive quantity... increment only the version no decrement
see Version written there Version name "1.0" change it to "2.0" and versioncode 1 to 2
because now playstore wont accept your earlier version apk i.e 1 it wil only accept incremented version like 2 3 or 4 etc
I figured out the problem (and yes I activated the APK beforehand as well). I didn't change the package name entirely in my .xml file. Once I did, I rebuilt my APK and it worked.
Am having a bad time with android in order to create new release
i have created a Signed APK with two option
then i zipped the .apk file,after trying to upload it to google console am getting the below error
Your Instant App APKs do not declare a valid 'android:targetSandboxVersion' attribute in their AndroidManifest. Using the 'com.android.feature' Gradle plugin to build your Instant App would add this attribute automatically.
Note : the file zipped and all the solutions asking to zip the file, no luck :(
You need to be clear if you are producing an Instant App or a normal Android app. I think this is what is confusing you, or maybe you just aren't being clear in the question.
Android Instant Apps are special Android apps that launch from a web page, and don't need a user to install them. To build them you need the Instant Apps SDK, and to follow the development instructions here. Android Studio will produce a zip for you, you don't need to do it manually
For normal Android apps, you don't need to zip your APKs. Just upload the APK itself to the Play Console.
I think you are probably making a normal Android app, but because you are zipping it, the Play console thinks you are uploading an instant app. So stopping Zipping your APK, and just upload it to the Play Console as a ".apk" file.
While you are at it, I'd recommend using APK V2 signing - it gives much faster installation on modern devices.
I want to change package name of an android project/apk so that i can have different version's of an application.
For this i have gone through some stackoverflow' questions for this { link1 , link2}. My project is build with gradle. In these stack's answer's i was not cleared where to change in [roject's build.xml or sdk's build.xml.
Is this possible to change package name with "–rename-manifest-package" and release application on google play store? or i need to do somthing else.
For different version, change version on gradle file and make another apk then release it on google plays store. There is an option on google store it should be release new version or something like that.
However, it is not possible to change current application's package name which is on google play store.
If you cannot do, I'll try to add step by step guide.
EDIT:
At first you need to change your app's version in here which is build.gradle(Module: app)
and then you need to create new signed apk since you want to publish it;
After creating signed apk you need to access your developer account and click APK section first and then upload new version of your application.