Has anyone successfully built an APK including maplibre-compose-material3 with AGP 9.x?

[alanonsr3]

What are you trying to achieve?

I'm building a third-party app that depends on maplibre-compose-material3 (0.12.1) and hitting a consistent issue where the composeResources entries from the AAR arrive in the output APK with corrupt compressed data blocks (method=8, invalid stored block lengths). The AAR itself is clean — extracting and inflating the same entries directly from the cached AAR works fine. The corruption happens during packageRelease with AGP 9.3.1.

noCompress expansion and android.enableResourceOptimizations=false have no effect. apksigner fails on the corrupt entries. 641 entries affected.

Has anyone successfully produced a signable APK with this library under AGP 9.x? Wondering if this is an AGP 9.x packaging interaction specific to KMP composeResources from AAR dependencies, or something specific to our setup.

I give Claude credit for the way the question is written because I couldn't figure out how best to present the question.

Affected Platform(s)

• Android
• iOS
• Desktop - macOS (JVM)
• Desktop - Linux (JVM)
• Desktop - Windows (JVM)
• Browser (JS)
• Browser (Wasm)

Library Version

maplibre-compose-material3 0.12.1

What have you tried?

-noCompress expanded to cover all composeResource file types
-android.enableResourceOptimizations=false
-AGP downgrade ruled out (KSP floor 8.10.0)
-Clean AAR in Gradle cache inflates correctly; corruption occurs during packageRelease only

Additional context

Android Studio required AGP 9.3.1 before building. AGP cannot be downgraded below 9.x due to KSP's minimum version floor. AGP 7.x is not an option from within Android Studio on this project without breaking KSP entirely.

[sargunv]

I could not reproduce. Tested on macos with JDK 21 and 25, AGP 9.3.1.

641 entries affected.

The maplibre-compose-material3-android .aar has only 261 entries on v0.12.1. Perhaps something other than this artifact is corrupted? Have you tried clearing all the gitignored gradle files, gradle caches, etc and building fresh? Does your build fail in CI as well?

Have you identified which entries are corrupted (say, with unzip -lv)?