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

[leon]

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

[pllhnr · Accepted solution]

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.

[Thomas_Wirth1]

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.

[leon]

Thank you for the clarification, this makes sense now!

[Gru]

Having very similar error with compose BOM 2026.04.01
Version '1.11.0' of artifact 'androidx.compose.ui:ui' is not supported. Please use the latest version of the Dynatrace Android Gradle plugin.

[GlebMaliborsky]

Hi, the Jetpack Version 1.11. will be supported within Dynatrace Android Gradle plugin 8.339. It will be released soon, approximately in 2 weeks.

[seblaposte]

Hi, having same error 

> Version '1.12.1' of artifact 'androidx.compose.ui:ui' is not supported. Please use the latest version of the Dynatrace Android Gradle plugin.

Between dynatrace gradle plugin  8.349.1.1010 and androidx.compose.ui:ui:1.12.1

[Thomas_Wirth1]

Dynatrace Android Gradle plugin version 8.351 will support Jetpack Compose version 1.12. The release of version 8.351 is planned for mid of November.

[seblaposte]

Hi,

How can we get visibility into the roadmap for Dynatrace support of Compose BOMs ?
Why is there such a long delay between Dynatrace releases and the corresponding Compose BOM support, forcing us to postpone our version upgrades ?

[Julius_Loman]

Definitely, a better support parity is required from customers. Dynatrace support is often released several weeks or even months after Jetpack Compose stable releases. 
I raised a product idea.

[shahab_ebrahimi]

Hi,
Thanks for raising this. You're right that the wait for Compose 1.12 has been longer than it should be. 
The plugin instruments Compose at build time, so each Compose version has to be adapted and regression-tested before we allow it. That is why an unsupported version stops the build instead of being instrumented untested. Google usually publishes the release candidate only about two weeks before GA, so day-one support is rarely possible. The effort also varies a lot from one release to the next.
Supporting 1.12 required us to first move the agent build to Android Gradle Plugin 9, and that work was scheduled later than it should have been. Support for Compose 1.12 is planned for plugin version 8.351, in mid-November.