How to solve APK without optimization Warning when publishing in google play?

system · June 12, 2019, 12:39am


	Attention	Topic was automatically imported from the old Question2Answer platform.
	Asked By	mgferr

I am able to create and run the apk but whe I try to publish it to google play I receive the following warning: " APK without optimization ".
Then it asks to use android app bundle but I didn’t find anything in the docs to help me do that.

system · June 12, 2019, 7:48am


	Reply From:	wombatstampede

The play store just proposes that you can optimize the apk in terms of size by using a special format wich provides alternatives for arm 32-bit/64-bit/intel cpus.

As you say, it is a warning but not an error (as long as your apk stays below 100MB). The downside of not using App bundles is that your apks may be bigger than they could be.

As far as I know, Godot does not directly support the new App Bundle feature of google play.

This may get easier to implement in the godot 3.2 version as the android export will be completely changed.

Anyway, another way of optimizing your apk’s size is to use multi apk support:
See this disscussion on github:

github.com/godotengine/godot

On the future of Android exporting

opened 02:53PM - 14 May 18 UTC

closed 12:49PM - 20 Jul 19 UTC

reduz

discussion platform:android topic:porting

Hi everyone! I want to open this issue to: * Discuss problems and solutions o…n improving the Android export workflow * See who might want to volunteer to implement the solutions discussed. I wrote the original Android port of Godot, but I'm a bit disconnected from mobile development as I haven't worked or published a mobile game since 2015. Thankfully many contributors have kept the port up to date. There is however, a serious problem with it, which is that the approach used for exporting is slowly becoming obsolete. Originally, the Android port used Ant for building, which was quite very limited, so many of the hacks done were thought around that. As the build system required Java installed and many other dependencies, I just took a pre-genreated APK and hacked it (modified binary resources inside) for exporting. This used to work OK for a while, but afterwards we started seeing many limitations to this approach: * It's a hack, basically * It makes it difficult to include third party add-ons. Community is often in pain due to the difficulty of adding third party APIs such as Admob or proprietary monetization/ad/analytics/etc. APIs. This needs to be made easier. * It seems Google does not like our approach very much, given #18192 So I suggest we use this issue to discuss on how the Android exporter could be changed. I see two ways of doing this. **Proposal 1:** Keep the current exporter, but create an Android Template Builder. This would get an different export template, unzip it to a directory, allow you to make changes (add third party API support without recompiling Godot, change permissions, manifest, etc), then you can zip it again and create a new export template which is used with the current system. **Pros**: Exporting remains rather simple for those who just want to test code on Android (no need to download Android SDK, which is a hassle, unless you need to) **Cons:** May still not solve all problems or future problems that may arise due to us hacking the APK. **Proposal 2:** Do away entirely with the current export system and make the UI build the APK every time exporting is requiered by calilng gradle. Allow installing extensions from UI (or asset library) for ADMob and other stuff with almost no effort. **Pros**: A lot less code and no need to do APK hacking. If you have android building properly set-up, it's easier to download stuff and make it work transparently. **Cons**: If you just want to test on Android, you will need to get Android SDK with the right components, which can be a hassle. Can this be automated by Godot by calling the Android tool? In any case, one of the goals of doing this change, is that you can download third party APIs from our asset library and get them to just work.. something users have a hugely difficult time with currently. **NOTE:** Please keep the discussion on the above topic, don't propose or discuss features that are not directly related to this.

I’ve already tried to use multi apk but it keeps the warning, I tried to upload different formats of apks, each one with unique screen and architecture but this still fails.
Notice that this is a blocking warning so I am not able to publish the app.
Is there any other filters that google use to validade this optmization which I can find in godot configs?

mgferr | 2019-06-12 12:42

A blocking warning? How big (MBs) is your apk?

I get this Warning too but it lets me continue.

wombatstampede | 2019-06-12 13:15

It is 56Mb when built with all architectures and 24Mb each one when built to single architecture. This is the full warning message:

Unoptimized APK 
Warning:
This APK results in unused code and resources being sent to users. Your app could be smaller if you used the Android App Bundle. By not optimizing your app for device configurations, your app is larger to download and install on users' devices than it needs to be. Larger apps see lower install success rates and take up storage on users' devices.
Resolution:
Use the Android App Bundle to automatically optimize for device configurations, or manage it yourself with multiple APKs.

mgferr | 2019-06-12 13:44

Ok. This should not block your release. The play store “user interface” is sometimes a bit misleading. Are you absolutely sure that you didn’t oversee a “continue” or “publish” (or similar) button?

I uploaded my last update apk maybe 3 or 4 weeks ago. I was also displayed this info but I could continue publishing the update.

If you still find no way. Then you might show a (complete) screenshot of the webpage. (If there is sensitive information feel free to blur it though)

Edit:
I am speaking of the web page which is (still) displayed after to click on “Close” acknowledging the warning.

Edit:
Check if there’s anything else that stops play.google.com from publishing the app. (Missing mandatory fields in the store listing, maybe Privacy Policy or content rating…) Normally, the UI should give you a hint when something isn’t completed.

wombatstampede | 2019-06-12 14:23

That’s it. I had to complete the Pricing & Distribution and App Content tab to make it ready to publish.
Thank you, man.

mgferr | 2019-06-12 14:50