Multiple dex files - Conversion to Dalvik format failed - Unable to execute dex

Question

I have 2 app versions - pro and lite. They are both already on the market at v1.01. I am trying to release v1.1 for both. This update includes SwawrmConnect integration in order to use their global leaderboards.

I should start off by saying I know I am not maintaining my code correctly. I have 2 completely separate apps and that share probably 90% of their code. I maintain them separately because after a week or 2 or 3 of failing to figure out how to do a library and share code, I gave up and just went this way with it.

SwarmConnect is the first jar I have used and had to make a library to two apps (see screenshot of file structure below).

Right now my lite version is working and is ready for release. I am now trying to get my pro version to where it needs to be for release. I am fairly certain all java/xml files are up to date and ready. When I went to run the pro version in the emulator, I get the below error:

[2013-04-18 11:24:41 - Dex Loader] Unable to execute dex: Multiple dex files define Lcom/swarmconnect/loopj/android/http/AsyncHttpResponseHandler;
[2013-04-18 11:24:41 - BibleTriviaPro] Conversion to Dalvik format failed: Unable to execute dex: Multiple dex files define Lcom/swarmconnect/loopj/android/http/AsyncHttpResponseHandler;

Things I've tried:

• Clean/rebuild
• Update Eclipse
• Delete bin and gen folders
• Restart Eclipse
• Plus some other stuff

My file structure:

Could the problem be is I am trying to use SwarmConnect as a library for 2 projects (lite and pro)?

EDIT:

Below is the file structure for the lite version that is working perfectly. Compiles and runs on emulator.

Answer 1

Coincidentally I ran into the same issue just day before yesterday. Here's what I suggest you to do.

First and foremost make sure that you have a backup of all the jars presently residing in the 'Android Dependencies'/'libs' folder.

Now, lets fix the lite version first by following these steps.

1. Remove all jar files except android-support-v4.jar from the 'Android Dependencies' folder under Project Explorer in Eclipse.

2. Similarly remove all Jar files except android-support-v4.jar from the libs folder under Project Explorer in Eclipse.

3. Now Right click on your project-> Select Properties-> Select Java Build Path-> Select Add External JARs. Add all the necessary jar files (just make sure you add a particular jar file only once).

Finally clean the project and build it. Now apply the same sequence of steps to the pro version. That should do it.

UPDATE:- In case you see Eclipse cribbing about some compile time errors after doing all this all you might have to do is to just fix those compile time errors by doing the necessary imports by pressing Ctrl+Shift+O.

[I assume that there's no linkage between the pro and lite versions of the project in terms of source dependencies etc.. what I mean to say basically they are totally independent.]

Hope this helps.

Answer 2

I strongly suspect this is your problem

1. Right click your project
2. Look under the "Android" option
3. In the lower pane look if "Swarm Connect" is present
4. If not, add it (though I really suspect it already is there)
5. Remove Swarm.jar from your libs directory

the reason being: when you add a library project to an Android project in Eclipse, it doesn't show up in your libs directory. I actually tried to add just the .jar file to a project and got told that that was the wrong approach (at least until API 14, I think).

My guess is, in your "non-pro" version you didn't link it in the project options and thus it still compiles correctly. Still, you should link it the way I just described to avoid problems when the library tries to access its own resources.

Answer 3

The above solution didnt work for me,All i had to do was add the jars in the libs folder externally and Uncheck Android private libraries under the order and export tab.

 right click--
             java build path--
                               order and export tab ->Uncheck Android private libraries 
                                   and add jars in the libs folder externally.

do the above steps. Dont know why this is happening.