Google Play 控制台崩溃报告 - 多个 OR

Question

Why the Google Play Console of my Production app crash reports (located in "Android Vitals" / "ANR and Crashes" and then select any crash to see a stack trace) contains a lot of ORs in the Stack Trace?

What does it mean? Which of that 12 methods actually caused the crash? Why the report so unclear?

Is there a way to get exact method name and ideally the line number in the report? (I have added mapping file under "Deobfuscation files").

Answer 1

The reason is that you are using Proguard for minifying and obfuscating your code (so far so good), and Proguard reuses the same method names as much as it can (ie as long as the signature of the methods are different) to minimize the number of letters it has to use. So the minified code contains most likely a dozen of methods with the name "a" in each class, and the stacktrace only gives you the method name, not its signature, so it's unfortunately impossible to know which one of the dozen "a" methods is being called, hence the deobfuscation tool gives you all the possibilities.

You can customise the Proguard configuration to avoid so many conflicts and hence make it easier to debug for you, but that will be at the cost of your app's size.

Edit: Use the -useuniqueclassmembernames flag to avoid these ORs. You can check the ProGuard manual for more details.

Answer 2

I had the same question some time ago:

Strange stacktrace reported by Google Play Console .

In my case i could notice that only one of the functions in each group could be the right one beacause the others where not invoked inside the "above" function.

I think this is a protection method against reverse engineering.