May 12th, 2011, 02:28 PM
Thread Author (OP)
Join Date: Apr 2011
Location: Fort Walton Beach, FL
Device(s): Acer Iconia A500
paperweight // Motorola Bravo (MB520) Froyo test dev. // Pantech Flex (ICS)
Carrier: Not Provided
Thanked 5 Times in 5 Posts
Conversion to Dalvik format, error 1, blah blah...one cause/solution found!
Sorry for the repost on this (I posted this same info at the end of
another thread), but IMHO, this seems like a common-enough problem that I
would really like to make sure this one cause/solution is seen by anyone
looking for it.
B Lyon, in the developers forum, deserves a billion thanks for a
tremendous amount of assistance (first on the developers forum, then via
direct e-mail....we had e-mails flying back and forth like crazy late
last night and early this morning). Anyways, something from our
conversations last night, that I didn't really process until a little
while ago, hit me (like a lead brick).
Ultimately, the problem traced back to a set of error messages indicating
a few redundant classes in jtwitter.jar and android.jar. The were all
under org/json (sound familiar?). I tried removing that part from
jtwitter.jar, but of course, that only made things worse. Then, as I
said, it hit me just a little while ago.
I got out of Eclipse, opened up the .classpath file in vim, and saw what
I hadn't really processed in my brain last night: jtwitter.jar was being
loaded prior to android.jar (Eclipse did that, not me). Anyways, I
reversed the two lines so android.jar was being loaded first, re-started
Eclipse, and dd a "Build All". It built. ZERO errors. :-)
Now I just need to remember (or more like, try all three until I find the
right one) which build method produces an SDK (or is that APK? whatever....)
file. I already know that the Build All didn't, but I seem to recall that it
didn't for the Hello Android app, either. Whatever. It'll take a minute or less
to find that, so no worries there.
So if you're seeing the error about the Conversion to Dalvik format
failing with error 1, check your .classpath file, and your error
messages, and look for dupes, or just something else loading before
android.jar, and you might just have your solution right there.
Hope this helps.....
PS: And this time, I got it right...a new thread, instead of a new reply. :-)
As always, blame it on chemobrain, and 99^ of the time, it's true. Sigh....
Last edited by GTbrewer; May 12th, 2011 at 02:32 PM.