Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

Updating an APK in Google Play without changing the expansion file

I have a "draft" APK in my Google Play console, and it's connected to an APK expansion file. The version code is 9, and the expansion file is "main.9.com.something.something.obb".

Now, I'm trying to update the APK before I release. I increased the version code, along with some code changes. When I upload the APK, I choose to use "main.9.com.something.something.obb" as my expansion.

Now, Google Play tells me this:

This configuration cannot be published for the following reason(s): Version 9 is not served to any device configuration: all devices that might receive version 9 would receive version 10.

But if I try to delete version 9, it won't let me, because it says that there are other versions depending on its expansion file!

So it's an infinite loop and I can't update my APK. The only solution I found is to re-upload the APK expansion (400MB), which is unacceptable. I don't want to do this every time I update the app, because users will need to re-download the expansion.

Also, I'm almost sure that this was never like that, and it's a bug that got introduced in the last period. I remember APK options like "deactivate" and so on, and now I can't find them. Any help?

like image 377
SirKnigget Avatar asked Aug 19 '13 13:08

SirKnigget


People also ask

What is the max APK size for Google Play?

To know more, read The Future of Android App Bundles is here, on the Android Developers Blog. If your app needs more than 100MB of memory, you can use expansion files to store additional APK assets. You can store two expansion files per app. Each expansion file can be up to 2GB in size.

What is APK expansion files?

File name formatSpecifies whether the file is the main or patch expansion file. There can be only one main file and one patch file for each APK. <expansion-version> This is an integer that matches the version code of the APK with which the expansion is first associated (it matches the app's android:versionCode value).


1 Answers

I actually solved this a few months ago but forgot to post the answer here.

I contacted Google Play support, and they clarified to me that this behavior happens only in "draft" mode. Once your app is published, you can update your APK without touching the expansion file, and reference the previously stored file.

My app is now published and there were no problems after moving from "draft".

like image 134
SirKnigget Avatar answered Nov 15 '22 06:11

SirKnigget