Error Messages within Throwables are not Deobfuscated #932
Description
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