Mobile applications: Issues with mobile RUM

[maliborskaya]

General Troubleshooting

If you've encountered an issue related to mobile application monitoring, first ensure the following:

• Your technology is supported by Dynatrace. See Technology support | Mobile app Real User Monitoring.

• You're using the supported version of the OneAgent SDK or Dynatrace Android Gradle plugin. See the table under How long are versions supported following rollout?.

• The issue that you're experiencing is not related to any of the currently known limitations. Check one of the following pages:

  • Dynatrace Android Gradle plugin | Instrumentation-specific limitations
  • Dynatrace Android Gradle plugin | Build-specific limitations
  • OneAgent for iOS | Known limitations
  • Instrument SwiftUI controls | Known limitations
  • Dynatrace Cordova Plugin | Troubleshooting and current restrictions
  • Dynatrace Flutter Plugin | Known issues
  • Dynatrace React Native Plugin | Troubleshooting and applicable restrictions

• You've enabled logging and checked the logs to see what went wrong. See the information below on debug logging for the following technologies and operating systems. You might also need to provide the logs if you decide to contact Dynatrace Support.

  • Android
  • iOS
  • SwiftUI: You can find the log file of the most recent build at dynatrace_instrumented/current/instrumentation.log. Log files of previous builds are located in time-stamped archives under dynatrace_instrumented.
  • Cordova

  • Flutter
  • React Native
  • Xamarin
  • .NET MAUI

• The other monitoring tools that you use are compatible with Dynatrace. See the related information for Android or iOS.

 

Specific issues

To troubleshoot specific issues, check one of the sections below.

 

Why is OneAgent not sending monitoring data for my mobile application?

You might have to adjust the application or server infrastructure to allow OneAgent to reach Dynatrace. Explore Adjust communication with OneAgent SDK for Android or OneAgent for iOS advanced configuration for more information.

The following list contains some problems that you might experience.

• Verify that you used the correct application identification keys: applicationId and beaconUrl. These are provided in the mobile instrumentation wizard for Android or iOS in Dynatrace.
  • For standard Android projects, the application identification keys are located in the top-level build file. See Instrument your application via Dynatrace Android Gradle plugin for the example.
  • For iOS projects, the application identification keys are stored in the Info.plist file.
• Ensure that you adapted Network Security Configuration correctly. You should include system CA certificates.

• Check if Dynatrace is reachable from within your company network.

Why is OneAgent not sending monitoring data for my hybrid application?

You might have missed one of the configuration steps described in Instrument hybrid apps.

 

Why is my reported action name, value, or web request URL truncated?

OneAgent truncates such reported values when they exceed 250 characters.

 

Why are some of my web requests missing?

Dynatrace automatically instruments most web requests. However, you have to manually instrument web requests in certain cases. Check the information on web request monitoring for OneAgent SDK for Android, Dynatrace Android Gradle plugin, or OneAgent SDK for iOS.

For the Dynatrace Android Gradle plugin, web requests might be missing when you use the Firebase plugin.

 

Why are web requests not associated with a given user action?

OneAgent only attaches web requests to a user action triggered within a specific timeframe. The timeframe starts when the action opens and ends 500 ms after the action closes. You can change this value with the timeout property for Android or with the DTXAutoActionTimeoutMilliseconds configuration key for iOS.

 

Why are some of my user action names incorrect?

To construct user action names, OneAgent captures the control title from different attributes/fields, so make sure that you pass the correct values to these attributes/fields. For details, see the information on user action naming for Android, iOS, or our React Native plugin.

You can also define user action naming rules to change the automatically generated names to a predefined name. See Create custom user action names for mobile applications.

 

Technology-specific troubleshooting

For issues specific to your technology or operating system, check one of the following pages:

• Mobile applications: General issues with Dynatrace Android Gradle plugin
• Mobile applications: Build issues with Dynatrace Android Gradle plugin
• Mobile applications: Issues with SwiftUI instrumentation
• Dynatrace Cordova Plugin | Troubleshooting and current restrictions
• Dynatrace Flutter Plugin | Troubleshooting
• Dynatrace React Native Plugin | Troubleshooting
• Mobile applications: Issues with Dynatrace Xamarin NuGet package
• Mobile applications: Issues with Dynatrace .NET MAUI NuGet package

If you can't resolve an issue with your mobile application, please contact a Dynatrace product expert via live chat within your Dynatrace environment.