Unable to execute dex: Multiple dex files define Lcom/myapp/R$array;

Question

Since updating to ADT 14 I can no longer build my project. It was building fine prior to updating.

The error:

[2011-10-23 16:23:29 - Dex Loader] Unable to execute dex: Multiple dex files define Lcom/myapp/R$array;
[2011-10-23 16:23:29 - myProj] Conversion to Dalvik format failed: Unable to execute dex: Multiple dex files define Lcom/myapp/R$array;

Similar issues have been reported and I have tried the suggestions there including

Restarting Eclipse.
Cleaning the project and rebuild - Disable "Project->Build Automatically" option, then "Clean" and "Build" project, then try to run. reset "Build Automatically" option to On
Re-installing the Android Developer Tools
Re-installing Eclipse (updated to the latest version 3.7.1)
Created a new project importing from the file system
Created a new project from subversion.

were you working on windows or mac .. because I would like to follow the following answers but I am not sure if they are going to work on mac .. thanks — Alison
– Alison, Commented Feb 8, 2014 at 16:33
if you have imported library project and have also imported library JAR in lib folder then you have to remove jar file from your lib folder and also from [ Build Path -> Configure Build Path ] . And it will be worked. — Mehul
– Mehul, Commented Jan 13, 2016 at 3:50
Look at my answer on following link. stackoverflow.com/a/38391449/3702595 — Sattar Hummatli
– Sattar Hummatli, Commented Jul 15, 2016 at 8:35

5 revs, 5 users 43% · Accepted Answer · 2014-08-17 08:52:29Z

460

I had the same problem, quite weird because it was happening only when using Eclipse (but it was OK with Ant). This is how I fixed it:

Right click on the Project Name
Select Build Path -> Configure Build Path
In Java Build Path, go to the tab Order and Export
Uncheck your .jar library

Only sometimes: In Order and Export tab I did not have any jar library there, so I have unchecked Android Private Libraries item. Now my project is running.

edited Aug 17, 2014 at 8:52

community wiki

5 revs, 5 users 43%
Marco Bonifazi

Sign up to request clarification or add additional context in comments.

11 Comments

Chris Feist Over a year ago

In my project, I was including the support library from the sdk directory in my build path, and I had the support library in the "libs" folder for support of ant building. I unchecked one and it fixed my issue.

Tom Pace Over a year ago

Sometime between the last time building and launching, a new library appeared mysteriously in my project: "Android Private Libraries" containing the support library I was already referencing. So this mysterious "multiple dex files define ____" appeared. Checking the Java Build Path and seeing this new item, and unchecking the originally-included support library solved the problem for me.

roy mathew Over a year ago

Thanks a lot. This is the correct solution. I really do not know why eclipse has this much bugs. Now the situation is like only 2 hours I can code and 6 hours I have to find solution to this kinds of unnecessary issues.

Junior Mayhe Over a year ago

In Order and Export tab I did not have any jar library there, so I have unchecked Android Private Libraries item. Now my project is running.

ymerdrengene Over a year ago

In my case I had a dublicate of ´android-support-v4.jar´. When i deleted it, the error went away

|

3 revs · Accepted Answer · 2011-11-08 16:00:26Z

94

My problem was resolved after cleaning up some directories and files left over from the previous versions of the tools. ADT Rev 14 changes where binaries are stored. I deleted the entire bin directory, restarted Eclipse and cleaned the build and forced a rebuild. That seemed to do the trick initially but the problem came back after the next run.

I finally discovered that my bin directory was included in the project build path. I excluded bin from the build path and repeated the steps above. This resolved my problem.

edited Nov 8, 2011 at 16:00

community wiki

3 revs
terry

5 Comments

terry Over a year ago

What the heck Google. This problem keeps coming back even with R15.

terry Over a year ago

I edited the solution above to include the final resolution. Resolved permanently now.

Bill The Ape Over a year ago

In short, no one really knows why the problem happens, what it means and how to fix it (I don't have any bin directory in the Java Build Path). I avoided updating to R15 for these reasons, staying with R9. But I am still having a similar problem, with no clue in sight. Any tip or help would be greatly appreciated.

Tom Redman Over a year ago

@BillTheApe - agreed. This is beyond frustrating, it's costly.

Bill The Ape Over a year ago

@TRedman I finally managed to solve the problem. Without understanding why. Don't laugh. LOL +1.

user802467 · Accepted Answer · 2014-11-11 01:56:59Z

50

[Solved for me]

Eclipse project properties->Java build path->Order and export

Uncheck Android private libraries.

answered Nov 11, 2014 at 1:56

community wiki

user802467

1 Comment

redux Over a year ago

Didn't help in my case

Roy Weinberg · Accepted Answer · 2012-11-14 22:34:43Z

None of the above helped. It was a simple problem in the end.

I had a project which uses the FacebookSDK and ViewPagerIndicator as library projects. All were built on Android API 16 and those two projects used the android support library vX (X not being 16!)

I added an external JAR to both those projects and pointed it to \extras\android\v4... And also removed the v4 jar I had in their libs folders.

Clean all projects and re-build.

Voilla!

The exact error I was receiving: Unable to execute dex: Multiple dex files define Landroid/support/v4/view/PagerAdapter; Conversion to Dalvik format failed: Unable to execute dex: Multiple dex files define Landroid/support/v4/view/PagerAdapter;

TomSelleck · Accepted Answer · 2012-12-23 17:01:19Z

36

This problem was happening me, I had an external .jar in my libs folder called gson-2.2.2.jar but for some reason there were two of them, gson-2.2.2.jar and gson-2.2.2.jar(1), I simply deleted the latter and my project built fine again.

answered Dec 23, 2012 at 17:01

community wiki

TomSelleck

2 Comments

phyatt Over a year ago

I had a similar issue when there was an old jar file in the libs folder and linked it to a newer jar in the same workspace. When ADT finds multiple definitions for the same symbol it puts an error like this. Deleting the old jar file in the libs folder fixed it for me.

ripopenid Over a year ago

External jar is one of the causes to the problem and happened to be so in my case, too. I just had a leftover jar in my /libs from a prior experiment, resulting in both a Library Project and the .jar that was generated from it. Deleting that jar under /libs solves the problem. +1

4 revs, 3 users 53% · Accepted Answer · 2013-06-05 12:18:45Z

31

Close eclipse.
Delete bin folder inside your project folder.
Start eclipse and clean your project.
Now run and the problem should be gone

edited Jun 5, 2013 at 12:18

community wiki

4 revs, 3 users 53%
Mohit marwal

5 Comments

swiftBoy Over a year ago

Mateus Viccari's answer solved my problem, I removed duplicate libs, and it works like charm..

Mehul Joisar Over a year ago

Worked for me.If manifest file get removed by eclipse from bin directory,add it manually and clean project again.

Magnus Over a year ago

Works for me. Also make sure you don't have the same .jar in two different places (in my case I had it both in a library project and in a project referencing that library project. Seems Eclipse just added it automatically for some reason)

tricknology Over a year ago

For me, I just cleaned the ENTIRE workspace. Simply cleaning the project was not enough. I believe my problem had to do with switching one of the projects to "Library" in the middle of a clean operation

redux Over a year ago

Didn't help in my case

chaqke · Accepted Answer · 2013-02-26 22:30:53Z

As others have mentioned, this occurs when you have multiple copies of the same class in your build path - including bin/ in your classpath is one way to guarantee this problem.

For me, this occurred when I had added android-support-v4.jar to my libs/ folder, and somehow eclipse added a second copy to bin/classes/android-support-v4.jar.

Deleting the extra copy in bin/classes solved the problem - unsure why Eclipse made a copy there.

You can test for this with

grep -r YourOffendingClassName YourApp | grep jar

sonida · Accepted Answer · 2013-02-06 18:18:32Z

23

For me, I just right click on project -> Build path -> configure build path -> Libraries -> remove dependency

after it works.

answered Feb 6, 2013 at 18:18

community wiki

sonida

Comments

2 revs · Accepted Answer · 2014-11-04 19:02:39Z

20

This error can happen if you have two jars that contains the same class names, e.g. I had two library: jsr311-api-1.1.1.jar, and jersey-core-1.17.1.jar, both containing the class javax.ws.rs.ApplicationPath. I removed jsr311-api-1.1.1.jar and it worked fine.

edited Nov 4, 2014 at 19:02

community wiki

2 revs
Mateus Viccari

1 Comment

swiftBoy Over a year ago

This is the perfect solution for me. I added same libs twice. Thanks.

3 revs, 3 users 50% · Accepted Answer · 2013-03-17 16:20:59Z

19

I was getting this error after adding the facebooksdk.jar to a project that already had dependencies on the android-support-v4.jar. Since the facebooksdk.jar already includes its own android-support-v4.jar there were conflicts. Removing the earlier android-support-v4.jar from the projects Properties / Java Build Path / Libraries resolved the issue for me.

edited Mar 17, 2013 at 16:20

community wiki

3 revs, 3 users 50%
user1293131

Comments

3 revs, 2 users 58% · Accepted Answer · 2015-09-07 03:38:03Z

18

Go to Project/properties and Java Build Path and unchecked the Android Private Libraries.

This is also another case for this kind of error

Done

edited Sep 7, 2015 at 3:38

community wiki

3 revs, 2 users 58%
Hiren Patel

Comments

2 revs · Accepted Answer · 2012-12-07 11:41:30Z

15

I removed Android dependencies from build path and it worked.

Edit: ignore that. I had same jar in my maven dependencies and libs folder. I removed the one at the lib folder.

edited Dec 7, 2012 at 11:41

community wiki

2 revs
Osha Mahue

2 Comments

dvs Over a year ago

Removing Android Dependencies from the build path broke my project. Fortunately it was easy to restore by right-clicking project > Android Tools > Fix Project Properties.

Hadi Tok Over a year ago

In some cases removing android dependencies and regenerating it solves some problems. But as in my edit that is not the case.

2 revs · Accepted Answer · 2017-05-23 12:26:17Z

9

You have probably installed r14, this error may have been caused due to the platform tools update, you have to re-install your sdk

edited May 23, 2017 at 12:26

community wiki

2 revs
Reno

3 Comments

terry Over a year ago

I just completely blew away my SDK and installed it fresh from the downloaded zip file and then loaded the Android APIs with the Android SDK Manager. I had high hopes but the problem persists.

Reno Over a year ago

There is a .android hidden folder in windows, you should delete that too.

Alison Over a year ago

the same problem exist

mephju · Accepted Answer · 2011-10-25 10:17:35Z

9

For me this problem only exists as long as there are Android library projects involved in my project. So when I remove all the libraries and do as you said I can run my app again. If there are libraries involved even the bin-removal-trick trick won' work.

I don't get why this bug first appeared today since I'm using ADT 14 for several days now. Well there were other bugs that kept me happy though.

answered Oct 25, 2011 at 10:17

community wiki

mephju

1 Comment

Jasper Over a year ago

Many of the solutions look like some voodoo stuff... :)

Rudolf Polzer · Accepted Answer · 2012-05-16 15:43:09Z

8

Deleting the bin folder was not enough, I also deleted the gen folder. Then after two rebuilds the dex error message was gone.

answered May 16, 2012 at 15:43

community wiki

Rudolf Polzer

Comments

2 revs, 2 users 67% · Accepted Answer · 2012-09-29 19:27:52Z

8

Select the project in Project Explorer, right-click and select Properties -> Java Build Path -> Source -> Check the box for Allow output folders for source folders

edited Sep 29, 2012 at 19:27

community wiki

2 revs, 2 users 67%
prasantasing

Comments

Ahsan Zaheer · Accepted Answer · 2013-09-20 11:01:43Z

8

I was basically facing the same issue. I deleted the BIN folder, then removed unused jar files for Order and Import from eclipse. IT WORKED after that

answered Sep 20, 2013 at 11:01

community wiki

Ahsan Zaheer

Comments

Jay · Accepted Answer · 2013-04-05 00:23:01Z

I'm late to this party, but adding my own experience so I can find it again later :)

I ran into this problem after upgrading the android sdk and eclipse ad-ins. No upgrade goes unpunished!

The problem for me was related to library projects, my app references both standard java projects and android library projects. I noticed the Java Build Path settings were including the android library projects src and res folders in the Source list (upvotes to everyone that mention bin in source being issue, src and res was also an issue.)

So the solution was:

Remove all referenced Android libraries source and project references from the Java Build Path section of the settings in both Source list and Project list
Make sure pure java dependencies are listed in Project list, and Checked in the Order and Export tab so the classes are included in the apk
Make sure all Android library dependencies are listed on the Android section of project properties, in the library section below the checked SDK versions.

It was along way to piece all that together from the other solutions! Phew!

Well stated! I came to identical conclusions after a lot of work. I just wanted to add that it if any of your library projects include other library projects or pure-Java dependencies, that they must all be added the same way, otherwise this error will arise. If you follow the rules above for all your projects, you shouldn't have any problems.
One more thing... it appears that if you don't need to export the Android Private Libraries of a project or library project, don't. If more than one project or library project exports it, you'll get the multiple dex files error.

Jake1164 · Accepted Answer · 2011-10-29 01:16:49Z

6

I ran into this when I upgraded from adt 14 to 15 and to get it to work I ended up just deleting the .eclipse folder (along with my settings) and re-installing the adt 15.

answered Oct 29, 2011 at 1:16

community wiki

Jake1164

Comments

5 revs, 2 users 82% · Accepted Answer · 2011-12-04 20:42:34Z

6

After reading Terrys response about deleting the bin directory and Larrys about the the location of the ANT directory:

I moved the files located in my projects BIN directory to the BIN/CLASSES and im up and running.

Edit 1 Then failed on second run...doh

Edit 2 So closed Eclipse moved files back to original location and its all working... um what? I don't pretend to know why this worked. Will update if any changes.

Edit 3 I have noted from my backups that there were indeed duplicate files in the BIN directory and BIN/CLASSES.

So the answer is: don't have files in both locations. At least for me that's what worked.

edited Dec 4, 2011 at 20:42

community wiki

5 revs, 2 users 82%
HostMyBus

2 Comments

Brock Adams Over a year ago

Try to reduce answers to: Helpful conclusion followed by supporting facts. Avoid history narrative AMAP; People tend to flag that, thinking it's "not an answer".

HostMyBus Over a year ago

cheers for that, any help to making my ramblings clearer is appreciated

Truncarlos · Accepted Answer · 2012-11-27 12:30:41Z

6

Modify your eclipse.ini file and set the maximum memory parameter to

-Xmx1024m

Then restart your computer.

It worked for me.

answered Nov 27, 2012 at 12:30

community wiki

Truncarlos

1 Comment

Sierisimo Over a year ago

Nothing related, giving more memory doesn't solve the dependency problems

jp093121 · Accepted Answer · 2013-04-29 04:24:09Z

found a solution i believe??

    [2013-04-28 23:56:09 - Dex Loader] Unable to execute dex: Multiple dex files define Lcom/coremedia/iso/AbstractBoxParser$1;

Where it says : "Lcom/coremedia/iso/AbstractBoxParser$1" that just happen to be the location of the library I imported that was causing the issue. Looked for com.codemedia.iso.AbstractBoxParser$1.class and .AbstractBoxParser.class.... took that jar, unpackaged it, removed both of those files, then repackaged as a .zip, added to library, cleaned and worked! no more conflict for me! (also no updates or additional downloads)

Dediqated · Accepted Answer · 2013-09-10 07:22:38Z

6

I had two different versions of Cordova .jar-files in my libs folder, I deleted the one I wasn't even using and it worked right away. Weird because I didn't notice that before and it worked before and then suddenly stopped working...

answered Sep 10, 2013 at 7:22

community wiki

Dediqated

Comments

Larry Borsato · Accepted Answer · 2011-10-28 17:54:44Z

5

The ADT R14 update changes where the classes go to the bin/classes directory (see http://tools.android.com/recent/buildchangesinrevision14). If you are using ANT, you should change the path for your classes from bin to bin/classes. This worked for me.

answered Oct 28, 2011 at 17:54

community wiki

Larry Borsato

1 Comment

terry Over a year ago

I am using Eclipse. Do you know where you change the class path in Eclipse?

2 revs · Accepted Answer · 2012-03-30 00:21:05Z

Solution for me:

BACK UP YOUR CODE!
Navigate to your project workspace (not your project) and run the following commands:

dev1:workspace$ cd ~/Documents/workspace/.metadata/.plugins/ dev1:workspace$ rm -rf org.eclipse.core.resources
Navigate to your Eclipse directory and type this command:

dev1:eclipse$ ./eclipse clear
Eclipse will start with an empty workspace - don't worry your projects are still there. Simple create new project from existing resource and things should be gravy.

The exact error I was receiving: [2012-02-07 14:15:53 - Dex Loader] Unable to execute dex: Multiple dex files define Landroid/support/v4/view/PagerAdapter; [2012-02-07 14:15:53 - ProjectCloud] Conversion to Dalvik format failed: Unable to execute dex: Multiple dex files define Landroid/support/v4/view/PagerAdapter;

Jared Rummler · Accepted Answer · 2013-02-08 23:42:19Z

5

I have several library projects with the same package name specified in the AndroidManifest (so no duplicate field names are generated by R.java). I had to remove any permissions and activities from the AndroidManifest.xml for all library projects to remove the error so Manifest.java wasn't created multiple times. Hopefully this can help someone.

answered Feb 8, 2013 at 23:42

community wiki

Jared Rummler

Comments

JPB · Accepted Answer · 2011-11-18 21:26:59Z

4

After trying all the other suggestions with no luck, I deleted all the contents of my projects 'bin' directory, then ran eclipse again and it worked.

answered Nov 18, 2011 at 21:26

community wiki

JPB

Comments

PacificSky · Accepted Answer · 2013-01-28 18:59:35Z

4

I converted a non-library project to a library project, but it had a previously built jar file in the libs folder. Removing this jar file caused this error to go away.

answered Jan 28, 2013 at 18:59

community wiki

PacificSky

Comments

Navi · Accepted Answer · 2013-01-31 15:02:34Z

4

I was facing the same issue then i saw while pushing my app some jar files which were loaded twice hence multiple dex error .Just go to your project properties -> Java Build Path and try unchecking jar which is being loaded twice.

answered Jan 31, 2013 at 15:02

community wiki

Navi

Comments

AbuQauod · Accepted Answer · 2013-04-28 09:04:53Z

4

[Solved for me]

by removing the duplicate library "JAR file" then remove BuildConfig.java file, Clean project and its work.

answered Apr 28, 2013 at 9:04

community wiki

AbuQauod

Collectives™ on Stack Overflow

Unable to execute dex: Multiple dex files define Lcom/myapp/R$array;

54 Answers 54

11 Comments

5 Comments

1 Comment

Comments

2 Comments

5 Comments

Comments

Comments

1 Comment

Comments

Comments

2 Comments

3 Comments

1 Comment

Comments

Comments

Comments

2 Comments

Comments

2 Comments

1 Comment

Comments

Comments

1 Comment

Comments

Comments

Comments

Comments

Comments

Comments

Linked

Hot Network Questions

Collectives™ on Stack Overflow

54 Answers 54

11 Comments

5 Comments

1 Comment

Comments

2 Comments

5 Comments

Comments

Comments

1 Comment

Comments

Comments

2 Comments

3 Comments

1 Comment

Comments

Comments

Comments

2 Comments

Comments

2 Comments

1 Comment

Comments

Comments

1 Comment

Comments

Comments

Comments

Comments

Comments

Comments

Linked

Related