How to debug android proguard?

Question

For example, when proguard is opened and the compilation passes, but an error occurs after installation, how to locate the cause of the error?

The reported ones are all things like a.c.b that cannot be located.

Answer 1

I checked the generated mapping.txt one by one. I usually don’t confuse the names of key classes such as Activity and Service. When an error is reported, I can locate the corresponding class, and then find the corresponding obfuscated class according to the confused name. kind.
For example, the error message received is void com.company.app.util.c.a(java.lang.String, java.lang.String). You need to search for com.company.app.util.c in mapping. Then find a void method that ends with "->a", and you can roughly determine which method caused the error. I usually find this and roughly infer where the error is caused, and try to fix it and see what happens next. Does the version still have this error? If so, continue to fix it.