Reviewing and fixing mobile app crashes is vital to improving mobile-app user experience. Dynatrace OneAgent for Mobile captures crashes and sends the stack traces to Dynatrace so that the criticality of the crash can be assessed and the root cause of the issue can be identified. With the mobile-crash analysis workflow, you can see the impact of crashes, identify the affected user groups, and quickly get to the root cause. By proactively resolving issues, you can thereby ensure that your applications consistently meet your business goals.
When working with a client-server setup, some crashes have their root cause on the server side. Dynatrace uses PurePath and OneAgent to correlate user actions with web requests, thereby giving you full visibility from individual user actions to the specific server-side database statements that contribute to mobile crashes.
To access crash reports for a mobile app
- In the Dynatrace menu, go to Mobile.
- Select the app you want to analyze.
- Select the Crashes tile, and then select Analyze crashes.
Crash analysis gives you an overview of all crash groups that occurred during the selected time frame and allows you to focus on a range of properties and dimensions that might be specific to the crash pattern. You can therefore analyze mobile app crashes based on operating system version, app version, user region, session duration, connectivity type, and various other dimensions.
Dynatrace groups crashes by similarity of the stack trace and occurrence in the source code. This usually also works across different versions of your app, so that you can easily find out if a crash is still present in the latest release. You can access each crash instance and filter it to investigate a particular part of the crash group.
You can also view an actual crashed user session and select a crash instance and the full listing of all user actions that occurred during the session before the crash under the Session information tab.
Symbolication and deobfuscation converts hexcodes and stack traces captured by Dynatrace into human-readable formats. By uploading symbol files, you can see clear text method names in the stack trace instead of hex codes or cryptic names provided by the obfuscator.
The following example is an Android stack trace, before and after deobfuscation:
With Mobile Symbolication API, you can manage iOS dSYM and Proguard mapping files.
Note: Because Apple performs optimizations after the upload of iOS app packages to App Store Connect, symbol files must be retrieved from Apple. This process can be automated with Fastlane.