Conversion to Dalvik format failed with error 1 on external JAR

Question

In my Android application in Eclipse I get the following error      UNEXPECTED TOP-LEVEL EXCEPTION    java lang IllegalArgumentException  already added  Lorg xmlpull v1 XmlPullParser           Conversion to Dalvik format failed with error 1   This error only appears when I add a specific external JAR file to my project  I searched for a long time for the possible solution  but none of the possible solutions work    I even tried to change to Android 1 6 instead of 1 5  the current version I use

User · Answer

-Remove all your libraries from your java Build path  And add it again  - Clean your project   Run it

User · Answer

None of the answers here worked for me either   However  I could fix the error by removing the Android classpath container  in my case Android 4 4  from ALL attached libraries except the main application and then exporting the APK  The library projects won t compile anymore  but the jar file still exists and the APK is getting deployed  I m not sure what s the reason for this behaviour

User · Answer

My problem was in integration of Ant   ProGuard   AdMob SDK library   Debug mode  I was building debug APK using Ant and Added AdMob SDK JAR to libs  directory  Eclipse generated the debug APK normally  but Ant could not  I was getting the following error       apply  UNEXPECTED TOP-LEVEL EXCEPTION      apply  java lang IllegalArgumentException  already added  Lcom google ads AdActivity     apply    at com android dx dex file ClassDefsSection add ClassDefsSection java 123    I also had ProGuard turned on for debug build in my build xml  default is off     lt target name  -debug-obfuscation-check  gt       lt property name  proguard enabled  value  true   gt   lt  target gt    That was the problem  Somehow ProGuard and AdMob SDK do not live together in debug mode  ProGuard did not obfuscate AdActivity class so it appeared in bin proguard obfuscated jar unobfuscated  but the same class exists in the AdMob SDK JAR file  Eclipse was building debug APK without ProGuard  so it worked fine   So my solution was just to turn off ProGuard for debug builds in build xml  I hope it helps somebody

User · Answer

All the solutions above didn t work for me  I m not using any precompiled  jar  I m using the LVL and the Dalvik errors where all related to the market licensing library    The problem got solved by deleting the main project and reimporting  create a new project from existing sources

User · Answer

If you want to solve this problem then you have to change Android SDK1 6 to Android 2 2  After that  clean the project and then build and run  Then you will see that your application is running

User · Answer

What worked for me are the following    Clean the build completely Removed the extraneous android jar file that I found in Project Properties Libraries

User · Answer

In my case the problem is actually with OpenFeint API project  I have added OpenFeint as library project       It is also added into build path  ADT tools 16 gives error with this sceneario   Right click on your project and click build path  configure the build path and then see the image and remove your project OpenFeint from here and all is done

User · Answer

I am using Android 1 6 and had one external JAR file  What worked for me was to remove all libraries  right-click project and select Android Tools -   Fix Project Properties  which added back Android 1 6  and then add back the external JAR file

User · Answer

I am using ADT 7 and the other fixes didn t work  but I still did them    Then I copied proguard cfg from another project and simply pasted it into the older ADT project folder  And wallah  it worked

User · Answer

Google API on dependencies cause this problem  After remove it works well

User · Answer

I found the solution in a differant way    https   stackoverflow com a 14948244 1014288  Thanks to this you can fix no deleting and stuff

User · Answer

I personally managed to fix this by manually editing the project properties file within the Eclipse project   What it was   target android-16 android library reference 1         github  ActionBarSherlock  library android library reference 2       github android-numberpicker library   What I changed it to so the problem went away   target android-16 android library reference 1       github ActionBarSherlock library android library reference 2       github android-numberpicker library   This file was not fixed automatically by using the  Fix Project Properties  tool

User · Answer

Updating Proguard to latest version solved it for me    My proguard path was  C  Program Files  x86  Android android-sdk tools proguard   I downloaded the new version from here and replaced both bin and lib folders   THANK GOD

User · Answer

I ran into this problem but my solution was twofold  1   I had to add an Android target version under project -  properties -  Android  2   I didn t have all google  third party add-ons   Click in AVD SDK manager under available packages -  third-party add-ons -  Google Inc  I downloaded all of the SDKs and that solved my issue

User · Answer

Just clean the project  If this does not work try the other solutions

User · Answer

This error is due to   having more than one JAR file  If the JAR file has similar class files  then  dx format cannot be parsed    Solution    make and choose the appropriate JAR file  get the latest one

User · Answer

This can also be caused if you have added Android jar file to your build path  perhaps by an accidental quick fix in Eclipse  Remove it with right clicking Project -  build path -  configure build path -  android jar  remove

User · Answer

Another case of android witchcraft   if nothing else works  try increasing your versionCode and versionName by 1 in the manifest   It worked for me

User · Answer

In my case   project- properties- java build path -  in order and export tab -  uncheck android-support-v4 jar

User · Answer

My problem was caused by ADT version 12 0 and ProGuard integration  This bug is well documented and the solution is in the documentation  Solution is in here  ProGuard command line

User · Answer

Hi Previously I had Android SDK Build tools 18 1 1 and Windows XP   then my app was running properly   But I updated My system to Windows 7 and also updated Android SDK Build tools to 19 to have latest configurations   But My project has xercesImpl-2 9 1 jar file so When I started to run my application with new updated configurations I was getting  Conversion to Dalvik format failed with error 1 while parsing org apache xerces impl xpath regex ParserForXMLSchema class   So I went through all the answers which are mentioned to this question but was not able to solve   I wondered for 4 days then I found this link which saved my life  after reading this I came to know that problem is due to xercesImpl-2 9 1 jar with Android SDK Build tools to 19   So I downgraded it to Android SDK Build tools to 18 1 1  And I got rid of this problem   i am posting my answer here so that if anyone would face this issue they can get solve it   It made me frustated  Hope will help others

User · Answer

Here s another scenario  and solution   If you run into this problem recently after updating the ADT for Eclipse    In your app project  check for any linked source folders pointing to your library projects  they have names in the form  LibraryName src    Select all those projects  right-click  choose  Build Path -  Remove from Build Path   Choose  Also unlink the folder from the project   and click  Yes   Clean  rebuild and redeploy the project    It seems the reason is that some previous version of ADT linked Library project source folders to the  child  projects  and the current ADT Dex combination isn t compatible with that solution anymore   EDIT  this is confirmed by an Android Dev Blog entry  specifically this one - see the 8th paragraph onwards

User · Answer

Windows 7 Solution   Confirmed the problem is caused by ProGuard command line in the file  Android SDK Installation Directory  tools proguard bin proguard bat   Edit the following line will solve the problem     call  java exe  -jar   PROGUARD HOME   lib proguard jar      to  call  java exe  -jar   PROGUARD HOME   lib proguard jar  1  2  3  4  5  6  7  8  9

User · Answer

Just for the other people who still have this problem and they have tried the above answers but still getting the error  which was my case   then my solution was to delete the project from Eclipse and re-import it again    This made the Android library to be added again to my referenced libraries  so now I have two Android JAR files referenced  hence I deleted one of them and now it compiles fine   Solution  Delete the project from Eclipse IDE and then re-import it again  then check for the above solutions

User · Answer

I went through the steps in this answer and still did not get a resolution   I kept searching around online and found that you can get this error if you re trying to export an APK while an Android device is connected to the computer     Disconnecting my device followed by closing the project  rebooting the computer  opening the project and cleaning it worked for me all three times this has happened

User · Answer

If you have ADT revision 12   you should update your proguard from 4 4 -  4 6  as described here   Also  you should leave     bin proguard bat file in the orginal form   Just download it from the web  and copy lib folder from downloaded package to the      Android SDK Installation Directory  tools proguard lib

User · Answer

I had the same problem  when i checked i saw that there were 2 classes with the same name  1 in each of the external jar file i had added  i had to then remove 1 of the jar file  Luckily i got another jar file for the 1 i had removed

User · Answer

None of previously proposed solutions worked for me  In my case  the problem happened when I switched from referencing a library source code folder to using the library JAR file  Initially there was an Android library project listed under the Android application project Properties  Android page  Library section  and the library compared also in project explorer tree as a link to the library source directory   In the first place  I just deleted the directory link from the project tree and I added the JAR library to the build path  but this caused the exception   The correct procedure was  after changing back the build path and putting back the reference to the library source      properly remove the library source directory link by actually removing the reference from application project Properties  Android page adding the library JAR to the application project build path as usual

User · Answer

This error was being caused for me due to several files I had excluded from the build path being deleted  but not removed from the exclusion list   Project -  Properites -  Java Build Path -  Source tab -  project src folder -  double click on Excluded -  Remove any files that no longer exist in the project

User · Answer

This usually happens to me after either eclipse has been running for a long time or after I have built a signed apk successfully    As far as my experience with this is concerned  the fix it I just restart eclipse

User · Answer

Just Project  gt  Clean worked for me

User · Answer

I know it s answered already  but here was my solution   My Android project was from a Subversion repository  and I just did Checkout as a New Project  I had to manually add my libraries  Android and Java  to the build path  otherwise it wouldn t let me compile  Then I would get the above error   I had to make a new Android project  and then manually copy over the changes

User · Answer

None of the answers here helped in my case   For me the problem was that mvn eclipse eclipse was generating a classpath entry that was a project reference to an Android library project  however  it was not showing up in the Eclipse build path settings  This meant that the library classes ended up in the dexer twice  once from the hidden project reference  and once from the linked library JAR   I had to open the  classpath with a text editor and remove the projects element manually  This fixed the issue

User · Answer

I tried each and everything but nothing worked   Interesting thing was if we export android application using proguard we were getting  conversion to dalvik format failed with error 1  error but if we don t use proguard while exporting then APK was successfully created   Finally one of the jar in our android project was having a  class file with more than 1 5 MB size Its size was causing this issue We split that class into many smaller classes and problem went away

User · Answer

None of the listed solutions worked for me    Here s where I was having a problem    I added the jSoup external JAR file to my project s path by first putting it in a source folder called  libs   and then right clicking on it  Build Path -  add to build path  This threw the Dalvik conversion error  It said I had  already included  a class from that JAR file  I looked around the project s directory and found that the place where it was  already included  was in fact the bin directory  I deleted the JAR file from the bin directory and refreshed the project in Eclipse and the error went away

User · Answer

I found something else  Android uses the  libs directory for JAR files  I have seen the  Conversion to Dalvik format failed with error 1  error numerous times  always when I made a mistake in my JAR files    Now I upgraded Roboguice to a newer version  by putting the new JAR file in the  libs directory and switching the class path to the new version  That caused the Dalvik error    When I removed one of the Roboguice JAR files from the  libs folder  the error disappeared  Apparently  Android picks up all JAR files from  libs  regardless of which ones you specify in the Java build path  I don t remember exactly  but I think Android started using  libs by default starting with Android 4 0  Ice Cream Sandwich  ICS

User · Answer

I solved the problem   This is a JAR file conflict   It seems that I have two JAR files on my buildpath that include the same package and classes   smack jar and android maps lib-1 0 2  Deleting this package from one of the JAR files solved the problem

User · Answer

I ran into this problem because the Android-Maven-plugin in Eclipse was apparently not recognizing transitive references and references referenced twice from a couple of projects  including an Android library project   and including them more than once  I had to use hocus-pocus to get everything included only once  even though Maven is supposed to take care of all this   For example  I had a core library globalmentor-core  that was also used by globalmentor-google and globalmentor-android  the latter of which is an Android library   In the globalmentor-android pom xml I had to mark the dependency as  provided  as well as excluded from other libraries in which it was transitively included        lt dependency gt           lt groupId gt com globalmentor lt  groupId gt           lt artifactId gt globalmentor-core lt  artifactId gt           lt version gt 1 0-SNAPSHOT lt  version gt           lt  -- android-maven-plugin can t seem to automatically keep this from being              included twice  it must therefore be included manually  either explicitly              or transitively  in dependent projects -- gt           lt scope gt provided lt  scope gt       lt  dependency gt    Then in the final application pom xml I had to use the right trickery to allow only one inclusion path---as well as not explicitly including the core library        lt  -- android-maven-plugin can t seem to automatically keep this from being         included twice -- gt       lt  --  lt dependency gt  -- gt       lt  --  lt groupId gt com globalmentor lt  groupId gt  -- gt       lt  --  lt artifactId gt globalmentor-core lt  artifactId gt  -- gt       lt  --  lt version gt 1 0-SNAPSHOT lt  version gt  -- gt       lt  --  lt  dependency gt  -- gt        lt dependency gt           lt groupId gt com globalmentor lt  groupId gt           lt artifactId gt globalmentor-google lt  artifactId gt           lt version gt 1 0-SNAPSHOT lt  version gt           lt exclusions gt               lt  -- android-maven-plugin can t seem to automatically keep this from                 being included twice -- gt               lt exclusion gt                   lt groupId gt com globalmentor lt  groupId gt                   lt artifactId gt globalmentor-core lt  artifactId gt               lt  exclusion gt           lt  exclusions gt       lt  dependency gt        lt dependency gt           lt groupId gt com globalmentor lt  groupId gt           lt artifactId gt globalmentor-android lt  artifactId gt           lt version gt 1 0-SNAPSHOT lt  version gt       lt  dependency gt

User · Answer

My own and only solution that I found today after four hours of testing all the solutions  is a combination of many solutions provided here    Delete project from Eclipse Delete files in  bin and  gen from project folder Remove references to libraries into  classpath file in root project folder Restart Eclipse with command line   eclipse -clean Import project Right click on project - select Properties   Java Build Path   Libraries and remove everything else than Android XX Y Finally clean project  wait for automatic Building or Build it Launch and now it works  At least for me      I tried every step at a time and many combinations  but only the succession of all steps at once made it  I hope I won t face this again

User · Answer

For me  an extra JAR reference had appeared in my build path  I deleted this  and it works now

User · Answer

Often for me  cleaning the project DOES NOT fix this problem   But closing the project in Eclipse and then re-opening it does seem to fix it in those cases

User · Answer

EDIT  new solution    It looks like the previous solution is only a bypass  I managed to finally fix the problem permanently  In my case there was a mismatch in android-support-v4 files in my project and in the Facebook project that is referenced in my project   I found this error by performing Lint Check  Android Tools   Run Lint  Check for Common Errors    My previous solution   I ve tried any possible solution on this site - nothing helped     Finally I ve found an answer here  https   groups google com forum   topic actionbarsherlock drzI7pEvKd4  Easy steps      Go to Project -  uncheck Build Automatically      Go to Project -  Clean      clean both the library project and your   app project      Export your app as a signed APK while Build Automatically is still   disabled

User · Answer

In general  it seems that this problem comes when there are unnecessary JAR files in build path   I faced this problem while working on IntelliJ IDEA  For me it happened because I added JUnit and Mockito libraries which were being compiled at runtime  This needed to be set to  testing  in module properties

User · Answer

Go to Project and then uncheck  Build Automatically  Then try to export the project and the error is gone

User · Answer

I had this problem with Eclipse neon and JDK 1 8  After changing to JDK 1 7 the problem was solved

User · Answer

i am also faced this problem when i am add same jar file with different versions  i simply remove old version jar an clean the project it works fine for me

User · Answer

This answer is basically what many people try to say  but many people may not understand  So         Another reason can be if you have a JAR file located somewhere in   your project folder and then added it as a Java Path Library  It does   not show up under the Package Explorer  so you don t notice it  but it   does get counted twice  causing the dreaded Dalvik error   answered   Jan 2  12 at 6 23 Rashmi B   Meaning   If you have for instance these two libraries   jar  in your lib folder    and then these two folders are also added to your build path    means that they are counted twice  thus giving you the error   Solution    Remove these libraries from your build path AND remove  Android Dependencies  as well   Clean all projects Export you project Enjoy

User · Answer

If you are using Leadbolt ads SDK in you app and you are combining both  Notification ads  and  Display Ads  you need to use pubxappCom jar instead of pubxapp jar for notification ads  or you get this error   Happy coding

User · Answer

None of these answers worked for me  My problem is caused by JUnit and hamcrest  See also java lang IllegalArgumentException  already added  Lorg hamcrest BaseDescription  Conversion to Dalvik format failed with error 1

User · Answer

In my case the issue was originated after updating Eclipse and ADT in March 2011  In my project I am using a JAR which was producing issues to rebuild and none of the former solutions worked  It took me some days to try all   search up amp down with no satisfying solution  Apparently there was a double reference to the  jar file   Finally I     removed any references from the libraries  deleted the physical file form within the application  got the  jar  located in a different directory outside of the project  using  Add External Jars  performed a project  clean   update references into the module calling the jar with  ctrl   shift  O   and it did finally compile

User · Answer

I ve dealt with this problem when using Sherlock ActionBar library in my project  You could do the following step  it s work for me    Right click to your project  select properties  A dialog will show up  select  Java build path  on the left menu  Remove  Android dependencies  and  Android private libraries  on the right panel then click OK Clean your project  select menu Project --  Clean  Right click your project  select Android Tools -  Fix project properties Clean project once again  Restart your computer Open eclipse and Export apk   Hope that will help you

User · Answer

You can solve this issue easily  with Eclipse Android Developer Tools  Build  v22 0 1-685705  by turn off menu    Project     Build Automatically  while exporting  un signed Android application  After that  don t forget to turn it on again

User · Answer

Nothing worked for me here  i had to change my proguard file to add this line   -keep class  mycode             which keeps any code thats not my package

User · Answer

For NewRelic users   If you have integrated the newrelic jar in your app  this happens when the newrelic version is outOf date     Solution      Update the newrelic jar to the latest version  On eclipse  its just right click on the project and update newrelic  Or you can download the new version directly

User · Answer

it s better to include all   jar files in the  lib  directory of the  project folders tree  and in this way   you ll not need to define the build path by going to the properties of the project   lib  is already a build path

User · Answer

I cleaned my main App Project AND the Android Library Project which it uses  Solved the issue

User · Answer

Go to Project    Properties    Java Build Path    Libraries and remove all except the  Android X Y   in my case Android 1 5   click OK  Go to Project    Clean    Clean projects selected below    select your project and click OK  That should work   It is also possible that you have a JAR file located somewhere in your project folders  I had copied the Admob JAR file into my src folder  and THEN added it as a Java Path Library  It does not show up under the Package Explorer  so you don t notice it  but it does get counted twice  causing the dreaded Dalvik error 1   Another possible reason could be package name conflicts  Suppose you have a package com abc xyz and a class named A java inside this package  and another library project  which is added to the dependency of this project  which contains the same com abc xyz A java  then you will be getting the exact same error  This means  you have multiple references to the same file A java and can t properly build it   In other ways this may be occurred if you accidentally or knowingly edit  add any thing in the class path file manually  In certain cases we may add android jar path manually to classpath file for generating java doc On removing the that after javadoc generated code will works fine Please check this too if any one still occurs

User · Answer

I had the same problem and none of these solutions worked  Finally  I saw in the console that the error was due to duplicated class  one in the existing project  one in the added jar file     java lang IllegalArgumentException  already added  package MyClassclass   2011-01-19 14 54 05 -       Dx1 error  aborting  2011-01-19 14 54 05 -      Conversion to Dalvik format failed with error 1   So check if you are adding jar with duplicated classes in your project  If yes  try removing one of them   It worked for me

User · Answer

I had the same problem  when I tried to export my project  Nothing to see in the console   For me the solution was upgrading proguard to the lastest version  hopes this helpes someone

User · Answer

Ran into this problem myself today  Cleaning and rebuild did not fix the problem  Deleting and reimporting the project didn t help either   I finally traced it back to a bad additions to my  class file  I think this was added by the plugin tools when I was trying to fix another problem  removing it got rid of the  Conversion to Dalvik format failed with error 1  build error    lt classpathentry kind  lib  path  C  dev repository android-sdk-windows platforms android-3 android jar  gt       lt attributes gt           lt attribute name  javadoc location  value  file  C  dev repository android-sdk-windows docs reference   gt       lt  attributes gt       lt accessrules gt           lt accessrule kind  nonaccessible  pattern  com android internal      gt       lt  accessrules gt

User · Answer

I was using ADT r14 and when ever i tried adding any library project  I got this error  For me what worked was simply updating the ADT to the latest version  It solved the problem instantly  I tried almost all the workarounds given on stackoverflow but nothing else really worked for me

User · Answer

In my case im having an exteranl jar added So I moved the external jar position to top of android reference in Project Prop--- Java buildPath--- Project references

User · Answer

The error should be finally fixed as of ADT 17 Tools r17 preview releases  At least some instances of it  if not all

User · Answer

For me the problem was that I had set the wrong compiler compliance level  1 8 instead of 1 7    This answer solved it      In the Project SDK section  when you add an Android SDK you should   provide the Java SDK and all my Android SDKs uses Java 8 as SDK so it   create the class files with the wrong version even if the Project   level is 1 7  i don t know why  i supposed that everything was choosed   by Project level   Now i changed the SDK  the java version  1 x 0    part

User · Answer

I had the same error  and tried everything above but nothing helped me   My projects are attached to GIT source control system  and I realized that there are some GIT related task while exporting to Andorid application  Then I commited all changes to the GIT repository and error dissapear   So  if you are using GIT for source control and nothing above help you  try to commit all changes to the GIT repository  and eventually push to upstream  and try export again

User · Answer

I have just installed newest eclipse with newest API and newest SDKs and tools but  years later  this error does not get old  I waste a day to figure it out  Tried everything  In vain  Because this message is very generic and a lot of different problems will raise it  So  solutions pointed by some will not work for others   A good first approach is to go to Window   Preferences   Android   Build and UNCHECK  Skip packaging and dexing      This way you will have more clues on your specific error when you are building  not only exporting   In my case  I got an  Dx unsupported class file version      This error I did not see reported here  Well  based on this I discovered that some old jars I use were compiled with 1 6 and others with 1 7  So I changed default IDE compiler compliance level to 1 6  Window   Preferences   Java   Compiler   and after complete clean and rebuild of every dependence I had  I finally could generate my APK

User · Answer

Nothing helped me  but the suggested solution here worked like a charm   i e  adding the line -optimizations  code allocation variable to proguard-project txt

User · Answer

In my case  unplugging my phone from the USB was all it took to fix this error

User · Answer

I had the exact same error with a project containing protobuf lite  Protocol Buffers by Google  in its classpath  I guess the reason was the protobuf-lite jar that was in my classpath and project-folder was built in my previous machine  When I downloaded Maven and re-built the protobuf-lite jar file then added it anew as a user-library to my project everything worked fine

User · Answer

In most cases this problem is caused by a buggy or corrupted version of Proguard  that for some strange reason often will be installed from official Android SDK manager  Don t edit Proguard bat file to avoid further problems  if you get this issue  download the latest stable version of Proguard from official site and replace all proguard files in  android-sdk tools proguard   with the latest proguard files extracted from the downloaded archive   Make no sense remove all external libraries dependencies  if a developer add a library to his project most likely the library is needed

User · Answer

Simply cleaning the project has worked for me every time this error has come up

[android] "Conversion to Dalvik format failed with error 1" on external JAR

Examples related to android

Examples related to dalvik

Examples related to android-sdk-1.6