Investigate Obfuscated Stack Traces with RUM Debug Symbols

This page is not yet available in Spanish. We are working on its translation.
If you have any questions or feedback about our current translation project, feel free to reach out to us!

The RUM Debug Symbols page lists all the debug symbols that are uploaded for a given type of RUM application. You can use this page to investigate obfuscated stack traces.

The following error message appears when a stack trace is not properly deobfuscated in RUM or Error Tracking: The stack trace could not be deobfuscated because no debug symbols could be found for this application. If you are not obfuscating your application, ignore this message. Otherwise, upload your debug symbols to see deobfuscated stack traces. You can view all your uploaded symbols on the RUM Debug Symbols page.

Deobfuscation failed: The stack trace could not be deobfuscated because no mapping files could be found for this application. If you are not obfuscating your application, ignore this message. Otherwise, upload your mapping files to see deobfuscated stack traces. You can view all your uploaded files on the RUM Debug Symbols page.

This can occur for a number of reasons:

The stack trace was not obfuscated

Datadog tries to deobfuscate all stack traces, including stack traces that are not obfuscated (for example, from running local tests or for non-production builds).

You can ignore this warning. The stack trace is already readable.

No debug symbols uploaded for this version

Use the RUM Debug Symbols page to see if there are debug symbols for your application. This page is filtered by type (JavaScript, Android, iOS, React Native, Flutter). Use the filter to find the debug symbols you are looking for.

If there are no debug symbols for your application, upload them.

Debug symbol tags do not match

Datadog relies on different tags to match debug symbols with stack traces. These tags vary for each type of application:

Application typeTag combination used for matching
JavaScriptservice, version, path
Androidv1.13.0: build_id
Older versions: service, version, variant
iOSuuid
React Nativeservice, version, bundle_name, platform; if multiple source maps match on these fields, the one with the highest build_number is selected
Flutterservice, version, variant, architecture

The RUM Debug Symbols page displays the values of these tags. If you find a mismatch, upload the debug symbols again with a corrected set of tags.

PREVIEWING: antoine.dussault/service-representation-ga-docs-us1