Unable to collect stack traces for crashes in ODEX files

[creasexul]

Integration

sentry-android

Build System

Gradle

AGP Version

7.2.2

Proguard

Enabled

Version

7.13.0

Steps to Reproduce

When a crash occurs in optimized DEX (ODEX) files, Sentry is unable to collect the corresponding stack trace information. This significantly impacts our ability to debug crashes in release builds where ART optimization is enabled.

Expected Result

1. Full stack trace should be collected, including methods from ODEX files
2. Proper symbolication of method names and line numbers
3. Ability to map optimized code back to original source code

Actual Result

When a crash occurs in ODEX-optimized code:

1. The crash is reported to Sentry
2. The stack trace is either missing or incomplete
3. Method names and line numbers from ODEX files are not properly symbolicated

Only I can get like this:

Exception Type: Unknown (SIGSEGV)

Application Specific Information:
Segfault

Thread 0 Crashed:
0   base.odex                       0x75dbe64b30        <unknown> + 506200476464

[stefanosiano]

hi @creasexul
would you mind sharing a link to an event in Sentry with this problem?
If you don't want to publicly expose it, you can send it to stefano.siano@sentry.io

[markushi]

@creasexul Did you have time to provide a link by any chance?