Breadcrumbs for Android release builds aren't deobfuscated

[narsaynorath]

Environment

SaaS (https://sentry.io/)

Version

No response

Link

https://sentry.io/organizations/sentry-sdks/issues/3885054835/events/c884e0bb85284cde9035b55d8ac567cc/?project=5428559&referrer=previous-event

DSN

No response

Steps to Reproduce

1. Navigate to page
2. Check the breadcrumbs section

Expected Result

Any values from the android application should be deobfuscated if there is a corresponding ProGuard file

Actual Result

The ui-click view.class values are still obfuscated, showing k.e

[narsaynorath]

Just noticed this while looking into deobfuscating the view hierarchy

[getsantry]

Routing to @getsentry/team-mdx for triage, due by Wednesday, February 1st at 11:37 am (sfo). ⏲️

[hubertdeng123]

Issue opened by a member of Sentry, doesn't need triaging

[timothyzeller]

Also experiencing the same issue as @narsaynorath

[adolfobulfoni-tomtom]

Having the same issue here on our project. 99% of entries for fragments state are not deobfuscated (except for 2 fragments who for weird reasons are deobfuscated). We are using manual FragmentLifecycleIntegration:

options.addIntegration(
                    FragmentLifecycleIntegration(
                        application,
                        enableFragmentLifecycleBreadcrumbs = true,
                        enableAutoFragmentLifecycleTracing = true
                    )
                )

see:

[romtsn]

@hubertdeng123 this should live on the main sentry repo, we cannot do anything from the SDK side here, this is backend stuff.

[hubertdeng123]

@romtsn Got it. I was a bit confused by what's going on here since it seemed like the issue might've fallen through. I'll transfer it back.

[NemanjaBozovic-TomTom]

Any updates on this issue? It's hard to debug fragment events when we cannot see the names.
Thanks

[hubertdeng123]

Looks like this item is backlogged, so unlikely.

[vzukanov]

This issue undermines the premise of lifecycle breadcrumbs. Would be great if Sentry team would allocate some effort towards its resolution.

[romtsn]

there's some work going on to deobfuscate the entire event payload (breadcrumbs, messages, contexts, tags, etc etc) afaik, but no ETA. In the meantime you could exclude fragment names from deobfuscation (not great, I know)

[vzukanov]

Good to know. Thanks for the update.

[Angelodaniel]

Hey Team,
Is there some progress on this?
Adding pro-guard rules is a patch which needs to be reverted once the real solution is in place, something we rather not spend time/effort on. It also would be great if these kinds of issues would be resolved asap as that would give us a higher confidence on using the product, as it shows that if we experience issues they are resolved timely.

[romtsn]

Progress can be tracked in the symbolicator repo.

Just to give some details: proguard processing is currently one of the biggest bottlenecks in our system, and this feature is not as straightforward to implement as it seems, moving proguard processing to a separate service in rust (symbolicator) with lots of memory should enable us to deobfuscate the entire event payload much easier.

maybe @Swatinem or @loewenheim can chime in and give even more details on when this might become possible

[Swatinem]

I would say we are in the final stretch to implement this for "regular" stack traces / frames, and profiles.
We haven’t really done any work yet to support a more generic way to deobfuscate "random class names", like what happens in view_hierarchy and also possibly breadcrumbs.

Once we have rolled this out for stack traces, we will look at extending this further as a followup.

[JustinBis]

Anything new here? Would also love to have this feature. We have a lot of custom breadcrumb logging that occasionally includes class names. Having this done automatically, or even some tag we could apply to a breadcrumb to opt it in to deobfuscation would be great.

[romtsn]

@JustinBis sadly no news, we'll update here when we get to it