Android – Google Analytics crash and exception anti aliasing

I have set up Google Analytics, so I see all uncapped crashes and exceptions

I also use Proguard to confuse. So these reports look like this: IllegalStateException (@ A: A: 457) {asynctask #2}

I have some asynctasks, but they have less than 200 lines of code

I know how to de obfuscate traces in Google developer console. I save the trace to a text file, run trace.jar through the terminal using my mapping file, and view the trace without obfuscation, so that I can understand the location of the exception

Try to perform the same operation on the GA trace, but do not anti obfuscate it. Is there a way to anti obfuscate the trace to understand the location of the exception? I hope so, because otherwise this function of GA is completely useless

resolvent:

So far, the only problem I can solve is a trace like IllegalStateException (@ A: A: 457) {asynctask #2} to check line 457 of each activity and think there is IllegalStateException

The content of this article comes from the network collection of netizens. It is used as a learning reference. The copyright belongs to the original author.
THE END
分享
二维码
< <上一篇
下一篇>>