ProGuard outputs the following files after it runs.
运行混淆器之后输出的文件有。
What am I doing wrong in ProGuard configuration to remove log lines?
我在做什么错在混淆器配置删除日志行吗？
Building in debug mode does not invoke ProGuard, because it makes debugging more cumbersome.
而在调试模式中构建则不会调用混淆器，因为那样调试会更加繁重。
You can fix errors when proguard strips away your code by adding a -keep line in the proguard.cfg file.
你可以在proguard. cfg文件中添加- keep这一行来修复这些错误。
If it is, ProGuard automatically processes the application's bytecode before packaging everything into an.apk file.
如果被设置了，混淆器在把所有东西打包成。apk文件之前，自动地对应用程序字节码进行混淆处理。
Caution: Every time you run a build in release mode, these files are overwritten with the latest files generated by ProGuard.
注意：每次在发布模式下构建时，这些文件都会被最新的文件覆盖。
The Troubleshooting section of the ProGuard Manual Outlines other common problems you might encounter when your code gets stripped away.
在混淆器手册问题解决方案部分，介绍了代码在混淆过程中你可能碰到的其他常见问题。
However, many situations are hard for ProGuard to analyze correctly and it might remove code that it thinks is not used, but your application actually needs. Some examples include.
但是，对于混淆器来说，大多数情况做出正确的分析是困难的，并且它或许会删除在它看来是无用的，但对于程序来说却确实需要的代码。
Fortunately, whenever ProGuard runs, it outputs a
幸运的是，每当混淆器运行时候，它都会输出到文件
There are many options and considerations when using the -keep option, so it is highly recommended that you read the ProGuard Manual for more information about customizing your configuration file.
Keep设置有很多可选项和注意地方，所以为了获得更多关于配置信息，强烈推荐你阅读混淆器用户手册。
There are many options and considerations when using the -keep option, so it is highly recommended that you read the ProGuard Manual for more information about customizing your configuration file.
Keep设置有很多可选项和注意地方，所以为了获得更多关于配置信息，强烈推荐你阅读混淆器用户手册。
应用推荐