Real User Monitoring
User session monitoring, key user actions - everything RUM.
cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Compose BOM version strictly coupled to Dynatrace Android Gradle Plugin – dependency resolution failure

leon
Visitor

We are experiencing a Gradle dependency resolution issue that seems to indicate a strict coupling between the Jetpack Compose BOM version and the Dynatrace Android Gradle plugin.

After upgrading the Compose BOM to version 2025.12.01, the Gradle sync fails with the error reported below.

This happens even when using the latest available version of the Dynatrace Android Gradle plugin.

This raises the question of why the Compose version must be so tightly bound to the Dynatrace plugin version, and how this situation is expected to be handled when upgrading Compose.

Environment

  • Compose BOM version: 2025.12.01

  • Dynatrace Android Gradle Plugin version: 8.331.1.1004 (latest at the time of writing)

 

Steps to Reproduce

 

  1. Update Jetpack Compose BOM to 2025.12.01

  2. Run Gradle sync

  3. Sync fails with a dependency resolution error

 

Actual Behavior

Gradle sync fails with the following error:

"Could not resolve all dependencies for configuration ':app:debugAndroidTestRuntimeClasspath'.
Version '1.10.0' of artifact 'androidx.compose.ui:ui' is not supported.

Please use the latest version of the Dynatrace Android Gradle plugin."

 

The error persists even when using Dynatrace Android Gradle plugin version 8.331.1.1004

3 REPLIES 3

pllhnr
Dynatracer
Dynatracer

Hi leon,
I can tell you support for Jetpack Compose version 1.10 is on the way and will be released end of February with OneAgent for Android version 8.333.

A small addition to the answer of my colleague regarding this part of you question:

This raises the question of why the Compose version must be so tightly bound to the Dynatrace plugin version

This build verification is only enabled, when a Dynatrace auto-instrumentation feature for the Jetpack Compose library is enabled. Dynatrace added this verification to protect customers from accidentally instrumenting untested versions and shipping this instrumentation to their user base.
The auto-instrumentation is part of the plugin and therefore a Dynatrace Android Gradle plugin version update is needed, when a new Jetpack Compose version is released.

Thank you for the clarification, this makes sense now!

Featured Posts