The warning:can& #39 that occurs when Eclipse packs an Android project with proguard.cfg; t find referenced class problem resolution

Warning:can ' t find superclass or interface
Warning:can ' t find referenced class

The solution to these two problems:

1. Use the "-libraryjars package path" To specify the third-party jar package that you have introduced in your project.
2. If you still have an error, make sure that the class for the error is not used in your project, use the "-dontwarn class name to express" mask warning.

Finished? But I also want to ask: the first step is done after the error, and this class in my project really practical, can not use "-dontwarn." Shielding warning AH??

The solution is as follows:

In fact, the reference to the class is not found in the third-party package, and very often we just have to disrupt their own code, the third-party package of the code is not to be disrupted. Hehe, this is called "just sweep your own door snow." Don't care for others to frost on the tiles. "

we are able to use
-dontwarn com.xx.bbb.**
-keep class com.xx.bbb.** {*;}
to maintain classes in a third-party library without mess,-dontwarn and-keep are used together, meaningKeep com.xx.bbb.** All the classes and all the methods in this package without confusion, and then call Proguard do not warn you that you cannot find a reference to the class com.xx.bbb.** the package.
after the configuration is ready. Packing again, everything ok! And the program can execute correctly

The warning:can& #39 that occurs when Eclipse packs an Android project with proguard.cfg; t find referenced class problem resolution