Failed to convert dalvik format with error 1 using adt r17

Question

Today I updated the ADT and SDK to the latest version of r17. Now I can’t export my applications anymore every time I try to export an application, I get a conversion to Dalivk format with error 1.

It doesn’t matter if I try to activate with or without proguard via project.properties.

Hope someone can help me.

I cannot publish any magazines because it does not give me any output; (

Error message:

Conversion to dalvik format failed with error 1 

Cheers, Mike

Edit:

Folder structure:

 /ProjectName/src /ProjectName/gen /ProjectName/assets /ProjectName/bin /ProjectName/proguard /ProjectName/res /ProjectName/AndroidManifest.xml /ProjectName/lint.xml /ProjectName/proguard.cfg /ProjectName/project.properties 

There are also Android dependencies:

 /Users/##/ViewPagerIndicator/library/bin/viewpagerlistviewlibrary.jar /Users/##/NineOldAndroids/library/bin/nineolddroidslibrary.jar /Users/##/ActionBarSherlock/ActionBarSherlock v3.0/library/bin/actionbarsherlock.jar /Users/##/GreenDroid/bin/greendroid.jar /Developer/##/annotations.jar /Users/##/ViewPagerIndicator/library/libs/android-support-v4.jar 

And reference libraries:

 /Users/##/Project Librarys/AdMob Ads v4.3.1/GoogleAdMobAdsSdk-4.3.1.jar /Users/##Project Librarys/SwarmLib/Swarm.jar /Users/##/Project Librarys/heyzap-sdk-2.0.7/android-sdk/heyzap-sdk-2.0.7.jar /Users/##/Project Librarys/google-gson-2.1/gson-2.1.jar /Users/##/Project Librarys/Acra v4.2.3/build/acra-4.2.3.jar 

EDIT

I tried to delete all the libraries and add them again. I tried to put external libraries in the libs folder and not add them through the properties. No difference ^^

Answer 1

Upgrading to ADT r20 resolved everything

Answer 2

Take a look at this: http://android.foxykeep.com/dev/how-to-fix-the-classdefnotfounderror-with-adt-17

He decided both “conversion to dalwick” and “class not found” for me. I just need to restart Eclipse after the changes the link suggested.

Answer 3

In ADT 17, they changed both how ADT handles dependencies and the updated proguard (up to version 4.7), and also created and divided proguard.cfg into "global" proguard-android.txt and proguard-project.txt .

I followed the link sent by @leocadiotine ( http://android.foxykeep.com/dev/how-to-fix-the-classdefnotfounderror-with-adt-17 ), which basically says to remove all banks from your path builds (and don’t re-add them ... ADT turns them on automatically now).

I also updated my proguard to use the global defaults for Android, and then added that my proguard design specification requires a new proguard-android.txt (replacing proguard.cfg ). Then just added

 proguard.config=${sdk.dir}/tools/proguard/proguard-android.txt:proguard-project.txt 

to my project.properties . (For more details see http://tools.android.com/recent/proguardimprovements .

It did it for me. Hope this helps.

Answer 4

I faced the same problem at work, several members of my team upgraded to version ADT v17.

ADT v17 now uses every jar file located in the libs directory, including files not specified in the java project build path. We relied on the fact that not all banks were loaded because my team left the old unused jar files in the libs directory (since we developed a new version of jar, we left the old one in the libs directory). Of course, several versions of the same jar are currently used, so this causes the java.lang.IllegalArgumentException: error already added.

Simply removing all of the specified cans from the project construction path was not a solution; this will destroy other developers not using ADT v17. The best solution was to move all outdated banks from the libs directory (which we should have done first: P).