Google Analytics Proguard Validation

Question

How do I restore an Android Proguard app with a crash message in Google Analytics. A few examples:

Note: when crash reports are executed by the user using the Google App Console, I can use retrace OK with the mapping.txt file.

Examples (due to glitches and exceptions to Google Analytics behavior)

• RuntimeException (@a:a:-1) {main}

• IllegalStateException (@f:a:-1) {main}

• NullPointerException (@MainActivity:M:-1) {main}

• NullPointerException (@a:l:-1) {main}

• NullPointerException (@al:run:-1) {main}

Answer 1

I just started collecting statistics and came across it myself. From the exception that happened to me in non-obfuscation apk, the syntax is as follows:

 exception-name (@class-name:method-name:line-number) {thread-name} 

• class-name: If this is confusing, you usually get stuck because the package name is not reported. Sometimes you can find a class, for example, in your "alpha", because most packages do not have many classes (search "-> al").
• method-name: if the class name is not confused (some class names must be excluded from obfuscation for the application to work), you can try to find the method in the mappings.txt file. Often there are several methods with the same display (but different call signatures). Since you cannot distinguish between them, then you will have to check them all to see if they could throw an exception.
• Line Number: This is useless since it is confusing (-1).

Conclusion: with standard reports, most of the time you will not be able to find out what caused the exception. It seems there is an opportunity to configure your own parser, perhaps you can enable the full stack stack. I have not tried this yet, but found a description in.