Lines Matching full:proguard
7 <title>ProGuard Troubleshooting</title>
79 ProGuard may print out some notes and non-fatal warnings:
84 <dd>ProGuard can't find a class or interface that your code is accessing by
90 <dd>ProGuard lists all class casts of dynamically created class instances,
100 <dd>ProGuard lists a number of constructs like
104 myField; }</code>". Otherwise, ProGuard might remove or obfuscate the
115 You may then want to keep the class too. Otherwise, ProGuard will
124 listed classes. ProGuard continues processing as usual, only considering
134 ProGuard continues copying the resource files as usual, skipping any files
143 ProGuard may terminate when it encounters parsing errors or I/O errors, or
178 zipping them up, and running ProGuard again.
186 <code>java.lang.AbstractStringBuilder</code>, which ProGuard ignores by
202 ProGuard again.</dd>
219 class. ProGuard will accept the class definition, but the current
264 class names. ProGuard has to know exactly what you want to keep: an
266 these. Without the proper seed specifications, ProGuard would shrink,
288 Should ProGuard crash while processing your application:
295 reduce the amount of memory that ProGuard needs by removing unnecessary
309 ProGuard in a different thread, e.g. from its GUI.</dd>
313 <dd>ProGuard has encountered an unexpected condition, typically in the
318 that causes ProGuard to crash.</dd>
324 simplest example that causes ProGuard to crash.</dd>
332 If ProGuard seems to run fine, but your processed code doesn't look right,
344 system, you could consider using ProGuard's <a
349 correspond to their package names. ProGuard will read misplaced class
357 <dd>If ProGuard is not keeping the right classes or class members, make sure
359 class is missing, ProGuard won't match the elements that you might be
373 coming up with those names. ProGuard's obfuscation step does remove the
383 If ProGuard seems to run fine, but the external preverifier subsequently
393 ProGuard's <a
398 step of ProGuard. Make sure you are using the latest version. You should
403 which you can find ProGuard to fail.</dd>
409 ProGuard will preverify the class files for Java Micro Edition.
415 If ProGuard runs fine, but your processed application doesn't work, there
434 the missing class dynamically. ProGuard can only detect constant name
446 Since ProGuard isn't detecting this (yet), you have to keep the missing
453 <dd>Your processed code may be unable to find some resource files. ProGuard
493 <code>proguard/wtk/default.pro</code> that's inside the
494 <code>proguard.jar</code>.</dd>
514 <dd>If your code contains empty busy-waiting loops, ProGuard's optimization
527 processed it with ProGuard.</dd>
570 If all of this seems ok, perhaps there's a bug in ProGuard (gasp!). If so,
572 find ProGuard to fail.</dd>
577 result of a bug in the optimization step of ProGuard. Make sure you are
582 simplest example on which ProGuard fails.</dd>
