From c7f0a09468da24de796ff8c838d13870141dc300 Mon Sep 17 00:00:00 2001 From: Stefano Date: Fri, 14 Jul 2023 10:16:42 +0200 Subject: [PATCH] Android/source context mentions (#7316) * added source context mention to recent Android highlights, proguard and common source context --- .../getting-started-primer/android.mdx | 2 ++ src/platforms/android/enhance-errors/proguard.mdx | 2 ++ .../data-management/debug-files/source-context.mdx | 10 ++++++++++ 3 files changed, 14 insertions(+) diff --git a/src/platform-includes/getting-started-primer/android.mdx b/src/platform-includes/getting-started-primer/android.mdx index e69d45e17c952..a7cd0e442e542 100644 --- a/src/platform-includes/getting-started-primer/android.mdx +++ b/src/platform-includes/getting-started-primer/android.mdx @@ -1,5 +1,7 @@ +We released Source Context, which shows snippets of code around the location of stack frames. + We just released a new Logcat integration, which automatically creates breadcrumbs for your `android.util.Log.*` calls. Using Jetpack Compose? Measure composition and rendering time of your `@Composable` functions using our performance metrics for Jetpack Compose. diff --git a/src/platforms/android/enhance-errors/proguard.mdx b/src/platforms/android/enhance-errors/proguard.mdx index 2e4ef17c8a1b1..2c90c694881d6 100644 --- a/src/platforms/android/enhance-errors/proguard.mdx +++ b/src/platforms/android/enhance-errors/proguard.mdx @@ -10,6 +10,8 @@ If you want to see de-obfuscated stack traces, you'll need to use [ProGuard](htt It works the same either way. A (random) UUID will be or has to be generated and placed into the `AndroidManifest.xml`. The same UUID has to be used to upload the mapping file(s). In case a crash happens in the app, the Sentry Android SDK will send the UUID along with the stacktrace to the Sentry server instance. Sentry will then de-obfuscate the stacktrace by searching for the associated mapping file with the same UUID. +If [Source Context](/platforms/android/enhance-errors/source-context) is enabled, Sentry can show snippets of code (_source context_) around the location of stack frames, which helps to quickly pinpoint problematic code. + Support for Guardsquare's ProGuard and [DexGuard](https://www.guardsquare.com/dexguard) was added in version 3.0.0 of the [Sentry Android Gradle Plugin](/platforms/android/configuration/gradle/). diff --git a/src/platforms/common/data-management/debug-files/source-context.mdx b/src/platforms/common/data-management/debug-files/source-context.mdx index 3e5f18a38019d..72cb99f5b3aac 100644 --- a/src/platforms/common/data-management/debug-files/source-context.mdx +++ b/src/platforms/common/data-management/debug-files/source-context.mdx @@ -71,6 +71,16 @@ For native Android and iOS code, follow the instructions in the [Debug Symbols]( + + + + +For Android, follow the instructions in the [Android Source Context](/platforms/android/enhance-errors/source-context) guide. + + + + + After they've been uploaded you can review and manage source bundles the same as any other debug information file. See [Managing Debug Information Files](../#managing-debug-information-files). Source bundles will be tagged with `sources`, and will carry the same filename as the