Regarding the size of the package after packaging the APK via Flutter

[lenzols]

Is there an existing issue for this?

• I have searched the existing issues

Unity version

Unity 6000.0 LTS

Common issues

• I have checked the common issues

Flutter version

3.32.2

Description

When building an APK through Unity tools or exporting Unity Library to Android Studio and building an APK on Android Studio, the package size is about 60M.
However, after exporting to the flutter project through our plug-in, the package size is about 130M, which has been built according to different CPU architectures.
As shown below:

How can I optimize the size of libil2cpp.so SO?

Minimum reproducible example (MRE)

No response

What platforms are you seeing the problem on?

No response

Devices

No response

Anything else?

No response

[jamesncl]

Hi, did you get to the bottom of this? I'd be interested to know more. To be honest it's a little over my head how the whole building and packaging pipeline works, but I wonder if the Flutter version includes both 32 bit and 64 bit ARM architectures whereas maybe the APK only includes one architecture, which is why it's double the size? I noticed the actual download size estimate was much smaller (44.5MB compared to 130.5MB) presumably because Play will split the bundle into separate downloads for each architecture, depending on the phone which is downloading the app. But to be honest I don't know, this is just a guess.