This is my first time building an app in the App Bundle. Publishing to Google Play, how to?

Question

Android

Hey! Need help publishing an app on Google Play.
Recently updated to Unity 2019.1.14, before I always built the application in APK and everything went without questions and difficulties.
Now, when I try to publish an APK in the market, I get 2 warnings:
1. The application does not meet the requirements of Google Play for 64-bit applications, they are asked to add x64 support and publish it in the App Bundle format.
2. An unoptimized APK file is again asked to be published in the App Bundle format so that users do not download APK with extra files for other architectures (x86, ARMv7)

Good. I went to the player settings in Unity, selected the IL2CPP backend, ticked all 3 architectures (ARMv7, ARM64 and x86), checked the Build App Bundle checkbox in the build settings.

After compiling, I have 2 files: the app's Aab file and a hefty zip file. How to deal with them further?

I understand that the aab file just needs to be fed to the developer console? And what is this zip archive for then, what to do with it?

Answer 1

In general, yes, only the .aab file is loaded into the console. The second file of the hefty zip-archive is symbols.zip - the file generated by default when compiling on the IL2CPP backend. It is needed only for debugging the application. It stores the length and addresses of all functions needed by IL2CPP for debugging stack traces. If you delete the file, then during debugging it will simply not be clear where and in what function the error occurred, there will be no debugging information. This file does not affect the performance of release.
Here on the unity forum there is a discussion about adding the ability to disable the generation of symbols.zip when building a release on IL2CPP. As far as I understand, the feature has not been implemented.

Answer 2

just dealt with this problem yesterday.
You need to disable x86 assembly. leave only arm7 and arm64. the meaning is that for any architecture (be it intel or arm), if there is a 32-bit assembly, then, according to the new rules, it must also be 64-bit. 64 bit intel is not (will not be) in the unit, so the only option is to turn off 32 bit.
In about a healthy aab and something else. There is a checkmark where something about split. whether architecture, whether resources to share. In general, you can remove it and there will be just a large AAB file, which will then be cut by Google into several apk for different platforms.

Answer 3

you fill in a small one like a regular apk or aab
and the second is an oob file, you also need to upload
a couple of examples here https://stackoverflow.com/questions/14015134/expan...