With the iteration of the project version and the rapid growth of the number of users, more or less bugs will appear in the APP. We usually use umeng, Bugly, TalkingData and other statistical tools to count online bugs. This article focuses on how to locate blog posts with bad code from error logs after code has been obfuscated. Students who have used statistical tools should know that when there is a bug in the online App, we will look for the source of the error code in the error log of the “Error List” of the statistical tool (different statistical tools may have different statistical documents, take Umeng as an example here). Before going online, people will mix up the code and consolidate the application package, so the error log in the error list will appear, and the error log cannot locate the problem. As shown below:
proguardgui.sh
How does Android see obfuscated error logging code