Lines Matching full:some
14 few problems. The following sections discuss some common issues and solutions:
79 ProGuard may print out some notes and non-fatal warnings:
125 the first definitions. The warning may be an indication of some problem
136 some problem though, so it's advisable to remove the duplicates. A
144 some more serious warnings:
161 some public classes, even though they are only package visible. This
175 class files are most likely inconsistent. Possibly, some class file didn't
176 get recompiled properly, or some class file was left behind after its
199 inconsistent. Possibly, some class file didn't get recompiled properly, or
200 some class file was left behind after its source file was removed. Try
244 <dd>There is a conflict between some new program code and the mapping file, in
249 initial obfuscation step. For instance, some new class may have been added
338 <dd>If you are working on Windows and it looks like some classes have
358 you are using fully qualified class names. If the package name of some
445 <code>myClass.getMethod</code>, trying to find some method dynamically.
453 <dd>Your processed code may be unable to find some resource files. ProGuard
498 <dd>If your midlet runs in an emulator and on some devices, but not on some
500 some older Motorola and Nokia phones, you might try specifying the <a
520 possible for some reason, you'll have to switch off optimization using the
544 <dd>You are probably compiling or running some code that has been obfuscated
553 <dd>You are probably processing some code that has been obfuscated before with
