Error Messages within Throwables are not Deobfuscated

[EmmettWilson]

Description

On a proguarded application we upload the mapping.txt. The stack trace of crashes is correctly unobfuscated. Sometimes the last line of the stacktrace will contain a cause message from the throwable that still contains class, method or field references that remain obfuscated in the dashboard.

Example Stacktrace from Bugsnag Dashboard:

 java.lang.NullPointerException: Attempt to read from field 'dxyzptlk.D6.z dxyzptlk.G4.q.j' on a null object reference
... more properly unobfuscated stacktrace redacted...
Handler.java:883android.os.Handler.handleCallback	
Handler.java:100android.os.Handler.dispatchMessage	
Looper.java:214android.os.Looper.loop	
ActivityThread.java:7356android.app.ActivityThread.main	
Method.java:-2java.lang.reflect.Method.invoke	
RuntimeInit.java:492com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run	
ZygoteInit.java:930com.android.internal.os.ZygoteInit.main

Environment

• Android version: Multiple
• Bugsnag version: 4.22.3
• Emulator or physical device: Both

[johnkiely1]

Hi @EmmettWilson.

We are currently unable to de obfuscate references such as this when it is contained in the error message itself as there is not enough information from the message alone to correctly identify a mapping for it. This is something we would like to be able to do so figuring out a way to achieve this is on our roadmap. However as of right now we have no definite timeframe for this but will keep you posted on any updates.