[DOCS-8873] Guide about deobfuscating stack traces in RUM #25351
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
github-actions
bot
added
Images
MaelNamNam
requested changes
Sep 20, 2024
content/en/real_user_monitoring/mobile_and_tv_monitoring/troubleshooting/android.md
Outdated
Show resolved
Hide resolved
content/en/real_user_monitoring/mobile_and_tv_monitoring/troubleshooting/flutter.md
Outdated
Show resolved
Hide resolved
content/en/real_user_monitoring/mobile_and_tv_monitoring/troubleshooting/reactnative.md
Outdated
Show resolved
Hide resolved
content/en/real_user_monitoring/mobile_and_tv_monitoring/troubleshooting/ios.md
Outdated
Show resolved
Hide resolved
Co-authored-by: Maël Lilensten <[email protected]>
alai97
approved these changes
Sep 23, 2024
| @@ -84,6 +84,10 @@ private class YourCustomDelegateURLSessionDelegate: NSObject, URLSessionTaskDele | |||
| * implement `URLSessionDataDelegate` and forward: | |||
| * [`urlSession(_:dataTask:didReceive:)`][6] | |||
|
|
|||
| ## "Deobfuscation failed" warning | |||
|
|
|||
| A warning appears when symbolication fails for a stack trace. If the stack trace is not symbolicated to begin with, you can ignore this warning. Otherwise, use the [RUM Debug Symbols page][7] to view all your uploaded dSYMs. See [Investigate Obfuscated Stack Traces with RUM Debug Symbols][8]. | |||
There was a problem hiding this comment.
Just confirming that we are intentionally using symbolication instead of deobfuscation here, feel free to disregard the comment if we are!
Suggested change
| A warning appears when symbolication fails for a stack trace. If the stack trace is not symbolicated to begin with, you can ignore this warning. Otherwise, use the [RUM Debug Symbols page][7] to view all your uploaded dSYMs. See [Investigate Obfuscated Stack Traces with RUM Debug Symbols][8]. | |
| A warning appears when deobfuscation fails for a stack trace. If the stack trace is not deobfuscation to begin with, you can ignore this warning. Otherwise, use the [RUM Debug Symbols page][7] to view all your uploaded dSYMs. See [Investigate Obfuscated Stack Traces with RUM Debug Symbols][8]. |
There was a problem hiding this comment.
They mean the same thing, but "deobfuscation" term is more closely associated with Android, while "symbolication" is with iOS. Will refine the suggestion here.
cy-moi
approved these changes
Sep 26, 2024
rtrieu
reviewed
Oct 1, 2024
content/en/real_user_monitoring/mobile_and_tv_monitoring/troubleshooting/ios.md
Outdated
Show resolved
Hide resolved
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What does this PR do? What is the motivation?
Adds a guide and some mentions of it.
Merge instructions
Additional notes