when build the apks, there are two base-master.apk (base-maseter.apk, base-master2.apk) about bundletool HOT 3 CLOSED

In bundletool 0.6.0, we enabled the optimization called uncompressed native libraries for devices on Android M and above.

This allows native libraries to remain uncompressed in the APK so that the Android platform doesn't have to uncompress them on the device to be able to read them. This leads to a size reduction of the app on the user device as well as a reduction in download size as well (due to compression algorithms performing better on uncompressed data). The optimization is guarded by the attribute extractNativeLibs=false in the AndroidManifest.xml which is why not only the APKs with native libraries will differ (on the compression), but also the master APK (for the manifest).

Because this optimization is available since Android M only, we generate two variants of the APKs, the compressed native libraries for devices on L and before, and the uncompressed native libraries for devices on M and later.

Calling bundletool install-apks selects the right APKs for the right device automatically based on the SDK version.

from bundletool.

Hello, wopeiseqi. I'm facing a similar behaviour, but i don't know why is this happening. Can you (or someone else) explain this?
For example:
I have a file "base-arm64_v8a" and "base-arm64_v8a_2", the second one is 3x larger then the first one. All files inside are identical but with compression.

from bundletool.

plecesne, Thanks for your replay! Now it's much clearer to understand!

from bundletool.