Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

APKs to retain in Google Play Developer Console

Tags:

Today one feature was added by Google Play Developer Console Team for managing the releases.

It has three options there for releases :-

APKs to add -

I understand from this that When you upload new app or update your app then it will roll out on Google Play depends on the staged roll out percentage & it will deactivate previous APK's from production.

APKs to deactivate

This will list a set of APK's which were deactivated and no longer served on Google Play.

APKs to retain

I could not understand meaning of this new feature ? Can anybody help me for this ?

Thanks in advance.

like image 587
N Sharma Avatar asked Feb 23 '17 05:02

N Sharma


People also ask

Does Google console accept APK?

Google Play uses Android App Bundles to generate and deliver APKs that are optimized for each device configuration, providing users with more efficient apps. This means you only need to build, sign, and upload a single app bundle to support optimized APKs for a wide variety of device configurations.

What should be unique for each APK?

Each APK must have a different version code, specified by the android:versionCode attribute. Each APK must not exactly match the configuration support of another APK. That is, each APK must declare slightly different support for at least one of the supported Google Play filters (listed above).

How do I remove rejected APK from Google Play Console?

All you need to do is deactivate (if necessary) and then delete all . apk files and the app will disappear from your developer console. If the app was ever published, this will not work. You can unpublish an app, but you cannot delete any .

How many apps can I publish on Google Play on developer account?

There is no limit to the number of apps per developer ID that can be uploaded, simply size constraints per apk. Why would the Android team try to limit the amount applications uploaded by any developer?


1 Answers

A release can have multiple APKs for different flavors of build. So you might have a build for legacy Android and a build for shiny new Android where you decide you want to use a feature that is not available.

You may then decide that you are going to release a fix for shiny new version but not for legacy version. You would then retain the legacy version and replace the new version only.

like image 65
Ian Spencer Avatar answered Sep 30 '22 05:09

Ian Spencer