Geek Answers Handbook

Google Analytics Crash and Exception

I set up my Google Analytics, so I see all failed failures and exceptions.

I also use proguard for obfuscation. Thus, these reports are as follows:IllegalStateException (@a:a:457) {AsyncTask #2}

I have several AsyncTasks, but they are all less than 200 lines of code.

I know how to deobfuse the traces I get in the Google Developer Console. I save the trace in a text file and run retrace.jar using my map file through the terminal and see an unbroken trace, letting me know where the exception occurred.

Tried to do the same operation for the GA tracks, and they were not deobfused. Is there a way to de-kill this trace in order to understand where the exception occurs? I hope there is, because otherwise this GA function is completely useless.

+4
source share
1 answer

The only solution I came up with is a trace, like IllegalStateException (@a:a:457) {AsyncTask #2}to check each activity line of 457 and think that there is an IllegalStateException possible.

0
source

More articles:


All Articles