Android ProGuard error with org.xmlpull.v1.XmlPullParser?

According to the partial log that you provide, the Android runtime class org.xmlpull. V1. XmlPullParser has ended up in your program code.

You should make sure it is not present in bin/classes or in some jar in lib because it is already present in the library jar android. Jar Furthermore, you have 4247 duplicate class definitions. This is probably due to specifying "some -libraryjars" as you mention.

I'm guessing these library jars are already included automatically by the build script, so you shouldn't specify them again.

According to the partial log that you provide, the Android runtime class org.xmlpull. V1. XmlPullParser has ended up in your program code.

You should make sure it is not present in bin/classes or in some jar in lib, because it is already present in the library jar android.jar. Furthermore, you have 4247 duplicate class definitions. This is probably due to specifying "some -libraryjars" as you mention.

I'm guessing these library jars are already included automatically by the build script, so you shouldn't specify them again.

Eric, the reason he (or in any case, I) has the XmlPullParser class in a jar in his libs is so that it would override the Android built-in XmlPullParser class which is deficient for some uses. Due to the way we formulate the proguard. Cfg on Android it's not possible to filter out the built-in one, neither do we want to filter out the better one, AFAIK.It also doesn't seem wise to roll our own Android jars, if that is even possible.

How should we deal with this? Thanks – pjv Jun 13 at 18:12 If your program jars contain better implementations, you really should try to filter out the library versions, with "-libraryjars android. Jar(!org/xmlpull/v1/**)", so ProGuard gets clean input.

If that's not possible, you can specify something like "-dontwarn org.xmlpull. V1. **".

It should work in this case, because ProGuard gives program classes precedence over library classes. – Eric Lafortune Jun 15 at 22:33.

I don't have the solution yet for proguard run via eclipse for android, but if you run proguard manually from the command line, you can put the following in your proguard. Cfg: -basedirectory /home/pjv/workspace/collectionista-repo/collectionista-main -injars /tmp/android_4500371803543847111. Jar -injars libs/joda-time-1.6.Jar(!META-INF/MANIFEST.

MF) -injars libs/FlurryAgent. Jar(!META-INF/MANIFEST. MF) -injars libs/veecheck-2.0.

Jar(!META-INF/MANIFEST. MF) -injars libs/commons-lang-2.4.Jar(!META-INF/MANIFEST. MF,!

META-INF/NOTICE. Txt,! META-INF/LICENSE.

Txt) -injars libs/OIAbout-lib-temporary. Jar(!META-INF/MANIFEST. MF) -injars libs/libGoogleAnalytics.

Jar(!META-INF/MANIFEST. MF) -injars libs/xstream-1.3.1. Jar(!META-INF/MANIFEST.

MF) -injars libs/ZQL_custom. Jar(!META-INF/MANIFEST. MF) -injars libs/xpp3_min-1.1.4c.

Jar(!META-INF/MANIFEST. MF) -injars libs/GoogleAdMobAdsSdk-4.1.0. Jar(!META-INF/MANIFEST.

MF) -injars libs/bugsense-trace. Jar(!META-INF/MANIFEST. MF) -outjars /tmp/android_1348923171424559204.

Jar -libraryjars /opt/android-sdk/android-sdk-linux_x86-1.6_r1/platforms/android-12/android. Jar(!org/xmlpull/v1/XmlPullParser. Class,!

Org/xmlpull/v1/XmlPullParserException. Class) Note how XmlPullParser. Class is filtered from the android API jar.

Don't worry about the warnings related to XmlPullParser just yet. Fix the errors and other warnings first, and if you must, use -ignorewarnings in your proguard.cfg.

In the mean time I moved on to something more elegant. See stackoverflow. Com/questions/6780902/… – pjv Nov 2 at 19:34.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.