mirror of
https://github.com/meshtastic/Meshtastic-Android.git
synced 2026-04-20 22:23:37 +00:00
2b8dbd6905
The libs.versions.toml entry 'androidx-compose = 1.11.0-rc01' was used by two satellite AndroidX-coords artifacts: androidx-compose-runtime-tracing = androidx.compose.runtime:runtime-tracing androidx-compose-ui-test-manifest = androidx.compose.ui:ui-test-manifest runtime-tracing is wired into every Android target as 'runtimeOnly' from AndroidCompose.kt. At rc01 it transitively requests androidx.compose.runtime:runtime:1.11.0-rc01, which Gradle's 'highest wins' then upgrades the whole runtime artifact to — while AndroidCompose.kt's resolutionStrategy still pins it to compose-multiplatform's version (1.11.0-beta02). Net result in the shipped APK on main: runtime-tracing bytecode: compiled against 1.11.0-rc01 APIs runtime classes at runtime: 1.11.0-beta02 (force-pinned) ui / foundation / animation: 1.11.0-beta02 That ABI skew between runtime-tracing and the runtime it traces is a plausible contributor to the recomposition / animation regressions we've been chasing on internal builds. Fix: both satellite artifacts now use version.ref = 'compose-multiplatform' so they always match the AndroidX runtime that CMP itself ships. Drops the unused 'androidx-compose' version ref. Verified via :app:dependencies that runtime/ui/foundation/animation/runtime-tracing all resolve to 1.11.0-beta02 cleanly. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> |
||
|---|---|---|
| .. | ||
| wrapper | ||
| develocity.settings.gradle | ||
| gradle-daemon-jvm.properties | ||
| libs.versions.toml | ||
| publishing.gradle.kts | ||