Unable to execute dex: Multiple dex files define Lcom/actionbarsherlock/R$attr

Question

I have created a library project for my app. When I try to add the library to a project, I get the following error when trying to run it:

[2013-02-07 04:51:26 - Dex Loader] Unable to execute dex: Multiple dex files define Lcom/actionbarsherlock/R$attr;
[2013-02-07 04:51:26 - testfromlibrary] Conversion to Dalvik format failed: Unable to execute dex: Multiple dex files define Lcom/actionbarsherlock/R$attr;

I have added the HoloEverywhere library to my library, whereas I have added the ActionBarSherlock library to HoloEverywhere. I am using Eclipse on Windows 7.

Even though I updated the SDK to the latest version, restarted Eclipse, and cleaned the various projects, the error persists.

Does anyone have any idea on how to solve this error? My bin dir is not included to the build path under properties, and I have tried deleting the bin folder altogether.

Thanks!

score 18 · Answer 1 · answered Aug 14 '13 at 17:54

I found that if I went into properties -> Java Build Path -> Order and Export and removed the Android Private Libraries then my project built fine. There was another support v4 jar in there which was conflicting with action bar sherlocks support v4 library

thalespf · Answer 2 · 2013-04-19T16:16:26.193

8

This issue happens to me when I create a library in conjuction with actionbarsherlock. In this case the eclipse create the R from sherlock in my library and in the project using it.

The solution is delete in your library bin folder only the folder actionbarsherlock that contains the R classes. This inst create anymore, and is present only in your project app.

edited Apr 19 '13 at 16:16

answered Apr 07 '13 at 02:49

thalespf

380
2
8

score 5 · Accepted Answer · answered Feb 07 '13 at 21:55

5

I pinpointed the cause of the error to /bin/classes. If I deleted the /classes dir before running the app, the app would compile and run. Of course, when I tried to actually export the app, the /classes dir would come back and along with it the error.

The solution to my problem was to install the latest version of Eclipse. When I export or run the app through the latest installation of Eclipse, the /classes folder does not appear now.

answered Feb 07 '13 at 21:55

Andreas H

131
1
1
5

The solution to my problem was that I deleted the jar files which I copy pasted in project's lib folder. I explicitly imported external jars in build path. – Antesh Sharma May 20 '15 at 19:12

score 3 · Answer 4 · answered Apr 30 '13 at 12:28

3

the issue for me was duplicate class files. i had both the package itself and the jar sdk of the package (in libs folder) in the same project.

answered Apr 30 '13 at 12:28

jony

89
2
5

score 3 · Answer 5 · answered Sep 14 '13 at 22:42

This happened to me after I changed a regular android project to a library project in order to use it for a Free/Paid project split set up.

Running either of the Free/Paid projects will result in OPs error.

Problem was some left over compilation stuff when the base project was a normal project and not a library project. Just clean the workspace and rebuild all projects. Old compilation junk will be removed and everything will be compiled into correct libraries. Try to rerun project which gave the error and everything should be fine now.

score 2 · Answer 6 · answered Jun 18 '13 at 12:30

2

Be sure both projects (the library and the app) don't have the same packagename (within the AndroidManifest)

answered Jun 18 '13 at 12:30

Ton Snoei

2,637
22
23

score 1 · Answer 7 · answered Feb 09 '13 at 13:19

1

I had the same issue today. I deleted the .apk file inside /bin, seemed to fix it.

answered Feb 09 '13 at 13:19

Matthew Shearer

2,715
3
23
32

Hi @Matthew, thanks for the answer. As mentioned earlier, I solved the problem by installing the latest version of Eclipse. – Andreas H Feb 10 '13 at 00:34

score 0 · Answer 8 · answered Oct 25 '13 at 02:54

0

Remove all the libraries from Build Path and import the library project that you want to implement.. This works just fine..

answered Oct 25 '13 at 02:54

user2918326

19
2

score 0 · Answer 9 · answered Aug 08 '14 at 05:01

0

You can use Tattletale

It helps you to identify duplicated classes in your JAR files.

Hope it helps.

answered Aug 08 '14 at 05:01

Jorge E. Hernández

2,800
1
26
50

score 0 · Answer 10 · answered Jan 29 '15 at 22:00

For Android Studio - I removed duplicate .jar imports and it was resolved.

Details: I had an app that had a base /common folder and then two folders that inherited from that - a free and paid version of the app. The issue was caused when I had the /common folder and the /free folder both including the same crashlytics jar file in project structure.

score 0 · Answer 11 · edited May 16 '15 at 16:08

0

For me, the solution was delete every JAR file in the "bin" folder / directory.

edited May 16 '15 at 16:08

Jonas Czech

12,018
6
44
65

answered May 16 '15 at 08:13

Amin SZ

11
1
3

score 0 · Answer 12 · answered May 27 '15 at 15:24

0

If your project is referencing a library project - please check if the library project has the same libs that you are using in your project but different versions. Use same versions everywhere and all should be ok!

answered May 27 '15 at 15:24

Taras

488
6
21

Unable to execute dex: Multiple dex files define Lcom/actionbarsherlock/R$attr

12 Answers12