Jetpack Compose source-info stack traces (via Composer.setDiagnosticStackTraceMode(ComposeStackTraceMode.Auto)) are still obfuscated in Sentry for an app using Compose 1.10.1.
Customer reports they are on Sentry Gradle plugin 6.x, KGP 2.3.x, AGP 8.13.2, with includeProguardMapping = true and autoUploadProguardMapping = true (autoInstallation and tracingInstrumentation disabled).
Hypothesis: Compose mapping entries (e.g. m$1349809332) may be missing from the uploaded mapping because merge{Variant}ComposeMapping didn’t run, or uploadSentryProguardMappings{Variant} runs before merge{Variant}ComposeMapping.
Reference: https://developer.android.com/develop/ui/compose/tooling/stacktraces
Jetpack Compose source-info stack traces (via
Composer.setDiagnosticStackTraceMode(ComposeStackTraceMode.Auto)) are still obfuscated in Sentry for an app using Compose 1.10.1.Customer reports they are on Sentry Gradle plugin 6.x, KGP 2.3.x, AGP 8.13.2, with
includeProguardMapping = trueandautoUploadProguardMapping = true(autoInstallation and tracingInstrumentation disabled).Hypothesis: Compose mapping entries (e.g.
m$1349809332) may be missing from the uploaded mapping becausemerge{Variant}ComposeMappingdidn’t run, oruploadSentryProguardMappings{Variant}runs beforemerge{Variant}ComposeMapping.Reference: https://developer.android.com/develop/ui/compose/tooling/stacktraces