Support and limitations

  • Latest Dynatrace
  • Reference

On this page, you can learn about the supported versions, limitations, troubleshooting resources, and support options for Android.

Supported versions

Requirement

Minimum version

Android API level

21

Gradle

7.0.2

Android Gradle Plugin

7.0

Java

11

Kotlin

2.0.21

Jetpack Compose

1.3 - 1.9

Limitations

  • HTTP requests—Only web requests from the frameworks HttpURLConnection and OkHttp (including frameworks that are based on these frameworks) are automatically instrumented; web requests from other frameworks have to be manually instrumented.
  • WebSocket and non-HTTP protocols—webSocket requests (ws://, wss://) and other non-HTTP protocols require manual instrumentation.

Instrumented files

The Dynatrace Android Gradle plugin only instruments the AndroidManifest.xml and .class files. It doesn't instrument the following components:

  • Native code—code written with the NDK is not instrumented.
  • Web components—files such as .html and .js are not instrumented.
  • Resource files—layout .xml files and other resource files are not instrumented.

Build-specific limitations

  • There might be compatibility issues with other performance monitoring plugins, especially when these plugins instrument OneAgent for Android. We recommend either using only one performance monitoring plugin or verifying via manual testing that the plugins you've chosen are compatible.
  • Android library projects—the Dynatrace Android Gradle plugin auto-instruments only Android application projects. It doesn't support the auto-instrumentation of stand-alone Android library projects. Internal libraries are auto-instrumented when added as a dependency to your Android application project.
  • Android Gradle plugin excludes property—with the excludes property of the Android Gradle plugin, you can disable instrumentation for specific classes. This property is similar to the exclude property of the Dynatrace Android Gradle plugin. However, when you use the Dynatrace property, our plugin still instruments some very important classes to ensure that instrumentation is always valid. With the Android excludes property, all the specified classes aren't instrumented, which might negatively affect the instrumentation.

Third-party obfuscation tools

OneAgent for Android and its transitive dependencies provide ProGuard rules designed for R8. If you use third-party obfuscation tools instead of R8, you are responsible for configuring them to honor the required keep rules. Failure to do so may result in runtime errors due to incorrectly obfuscated classes.

If you use Android Gradle Plugin features such as ignoreFrom to filter out keep rules from dependencies, be aware that this may affect OneAgent functionality.

Event limitations

  • Events per minute—There is a restriction on the number of events that can be generated within a single minute. Exceeding this limit may result in events being dropped or not processed. The default limit is 1,000 events per minute.
  • Event and session properties.

Troubleshooting

For troubleshooting mobile application monitoring issues, refer to the following resources:

Get support

You can get support by reporting a bug or asking a question in Dynatrace Community.

Report a bug

To report a bug or open a support case:

  1. Go to support.dynatrace.com.
  2. Open a support ticket with the following information:
    • Your Gradle configuration (with sensitive data redacted).
    • Debug logs from the OneAgent (see Enable debug logging).
    • OneAgent version.
    • Operating system version and device model.
    • Android Studio and Gradle versions.
    • Steps to reproduce the issue.
    • Any error messages or stack traces.

Community

Related tags
Digital Experience