Migration from V10 to v11, bigger libs size

Environment

• Android OS version: All
• Devices affected: All
• Maps SDK Version: 11.21.1

Observed behavior and steps to reproduce

Hello,
While doing a migration of my app from Mapbox SDK v10 to v11 I was surprised by the new size of the raw file generated. From the diff of the previous release (with Mapbox v10) there is an increase of more than 16MB coming from libmapbox-maps.so and libmapbox-common.so. Here an example with x86 architecture:

I properly excluding some plugin I'm not using, as explained on the APK size page, but didn't see any changes on the lib sizing.

implementation(libs.mapbox.android) {
        exclude("com.mapbox.plugin", "maps-lifecycle-ndk27")
        exclude("com.mapbox.plugin", "maps-indoorselector-ndk27")
        exclude("com.mapbox.plugin", "maps-overlay-ndk27")
        exclude("com.mapbox.plugin", "maps-lifecycle-lint-rules-ndk27")
        exclude("com.mapbox.plugin", "maps-annotation-ndk27")
    }

Is it normal the v11 SDK is much bigger than the v10? Is there any config to setup to avoid this size increase?

Thanks for your help!

Start with the APK size page and the reported dependency exclusions, then compare the x86 sizes of libmapbox-maps.so and libmapbox-common.so between SDK v10 and v11.21.1 using the Kotlin configuration shown. Done means determining whether the increase is expected and identifying any supported configuration that avoids it, or documenting that none exists.