Android dex gives a BufferOverflowException when building

Question

When compiling a specific Android project, and only on my Windows machine, I get a java.nio.BufferOverflowException during from dex. The problem occurs both when using Eclipse and when using Ant.

The output when using Ant is:

... [dex] Pre-Dexing C:\MyProject\libs\android-support-v4.jar -> android-support-v4-5f5341d3c1b10a79d7d93f9c1e64421e.jar [dex] Converting compiled files and external libraries into C:\MyProject\bin\classes.dex... [dx] [dx] UNEXPECTED TOP-LEVEL EXCEPTION: [dx] java.nio.BufferOverflowException [dx] at java.nio.Buffer.nextPutIndex(Buffer.java:499) [dx] at java.nio.HeapByteBuffer.putShort(HeapByteBuffer.java:296) [dx] at com.android.dex.Dex$Section.writeShort(Dex.java:818) [dx] at com.android.dex.Dex$Section.writeTypeList(Dex.java:870) [dx] at com.android.dx.merge.DexMerger$3.write(DexMerger.java:437) [dx] at com.android.dx.merge.DexMerger$3.write(DexMerger.java:423) [dx] at com.android.dx.merge.DexMerger$IdMerger.mergeUnsorted(DexMerger.java:317) [dx] at com.android.dx.merge.DexMerger.mergeTypeLists(DexMerger.java:423) [dx] at com.android.dx.merge.DexMerger.mergeDexes(DexMerger.java:163) [dx] at com.android.dx.merge.DexMerger.merge(DexMerger.java:187) [dx] at com.android.dx.command.dexer.Main.mergeLibraryDexBuffers(Main.java:439) [dx] at com.android.dx.command.dexer.Main.runMonoDex(Main.java:287) [dx] at com.android.dx.command.dexer.Main.run(Main.java:230) [dx] at com.android.dx.command.dexer.Main.main(Main.java:199) [dx] at com.android.dx.command.Main.main(Main.java:103) BUILD FAILED C:\Users\Jaap\android-sdks\tools\ant\build.xml:892: The following error occurred while executing this line: C:\Users\Jaap\android-sdks\tools\ant\build.xml:894: The following error occurred while executing this line: C:\Users\Jaap\android-sdks\tools\ant\build.xml:906: The following error occurred while executing this line: C:\Users\Jaap\android-sdks\tools\ant\build.xml:284: null returned: 2

When using Eclipse the message is shorter but similar:

[2013-11-01 14:29:44] APK file is not created for Project: [2013-11-01 14:29:46 - Dex Loader] Unable to execute dex: java.nio.BufferOverflowException. Check the Eclipse log for stack trace. [2013-11-01 14:29:46 - MyProject] Conversion to Dalvik format failed: Unable to execute dex: java.nio.BufferOverflowException. Check the Eclipse log for stack trace.

Like I said, I don't have this problem on my MacBook, even though they are both upgraded to the latest versions of the Android Build tools: 19.0.0.

@SherifelKhatib, just the support library and Google Analytics V2 — beetstra
– beetstra, Commented Nov 1, 2013 at 14:00
Since nobody seemed to have filed an issue on this yet, I have filed one at: code.google.com/p/android/issues/detail?id=61710 — CommonsWare
– CommonsWare, Commented Nov 2, 2013 at 12:40
getting simiar error on Centos x64: !SESSION 2013-11-07 17:07:35.305 eclipse.buildId=v22.3.0-887826 java.version=1.7.0_40 java.vendor=Oracle Corporation BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US Framework arguments: -product com.android.ide.eclipse.adt.package.product Command-line arguments: -os linux -ws gtk -arch x86_64 -product com.android.ide.eclipse.adt.package.product java.nio.BufferOverflowException at java.nio.Buffer.nextPutIndex(Buffer.java:519) — isti_spl
– isti_spl, Commented Nov 7, 2013 at 15:12

Flow · Accepted Answer · 2019-03-16 20:06:42Z

No need to downgrade the build tools back to 18.1.1¹, this issue is fixed with build tools 19.0.1.

If you can't use 19.0.1 for some reason then:

Make sure that the value of android:targetSdkVersion in AndroidManifest.xml matches target=android-<value> in project.properties. If these two values are not the same, building with build tools version 19.0.0 will end in the BufferOverflowException. ^Source

There is also some indication from comments on this post that you need to target at least 19 (android-19). Please leave a comment if this solution also works if your target is < 19.

This is how the fix looks for my project. The related AOSP issue is #61710.

^{1 If you really need to downgrade, you don't need to uninstall build tools 19.0.0, simply install 18.1.1 and add sdk.buildtools=18.1.1 to the local.properties file.}

This didn't work for me. Verified all project.properties and targetSdk. I am using the latest version of IntelliJ IDEA 13 Cardea. Fortunately, uninstalling build-tools 19.0.0 did fix the build.
For me to make it work, I also had to set the target SDK to the latest version (19).
And also make sure the target sdk version is downloaded with your sdk manager (this is my problem's cause).
I had target 10 in both AndroidManifest.xml and project.properties. Tried restarting Eclipse and cleaning, but did not help. Then I set target to 19 in config.properties and it worked. Have not tried downgrading build tools. (Target 15 did not work)
Setting targetSdkVersion in manifest and target in properties, to 19 worked for me

starball · Accepted Answer · 2022-12-26 23:53:31Z

83

Try what van said:

Right click your project → android tools → android support library.

edited Dec 26, 2022 at 23:53

starball♦

59.6k53 gold badges314 silver badges1k bronze badges

answered Nov 6, 2013 at 3:53

Lolo Me

8315 silver badges3 bronze badges

1 Comment

Christopher Over a year ago

Thank you for this solution, just two clicks and the problem was solved!!!!! (although in my menu, it was "add support library")

Flow · Accepted Answer · 2013-11-22 10:28:56Z

57

Same problem here. Reverted to build tools 18.1.1, restarted Eclipse and that fixed it.

edited Nov 22, 2013 at 10:28

Flow

24.1k15 gold badges106 silver badges159 bronze badges

answered Nov 1, 2013 at 14:46

Stefano

7146 silver badges3 bronze badges

7 Comments

beetstra Over a year ago

Yep, that fixed it. Had to manually delete the old 19.0.0 directory though.

NickT Over a year ago

This fixed it for me also, though I reverted to 18.0.1

Jon Over a year ago

I used this answer and I didn't have to revert back: stackoverflow.com/questions/19727915/…

James Wald Over a year ago

I verified all project.properties and targetSdk. I am using the latest version of IntelliJ IDEA 13 Cardea and played with the project's SDK version as well. Uninstalling build-tools 19.0.0 was the only way to fix the build for my project.

Darren Over a year ago

Thanks. Reverting to build tools 18.1.1 and deleting 19 fixed this for me. I thought I was going crazy

|

mrrrk · Accepted Answer · 2013-11-18 14:01:25Z

50

I was able to get my problem project to build by adding this extra line:

sdk.build.tools=18.1.1

...to my project.properties file, which is present in the root of the project folder. All other approaches seemed to fail for me.

answered Nov 18, 2013 at 14:01

mrrrk

2,34922 silver badges17 bronze badges

4 Comments

saurav Over a year ago

i think this is also one of the reason behind the problem. I never used version 19 in my target sdk and still the problem was coming. Probably the sdk build tools was set to 19 which had to be reverted back

Flow Over a year ago

The used target does not determine the used buildtools version.

speedynomads Over a year ago

I added the latest support library and added this line to the project properties and my problem was fixed... thanks

Yoni Samlan Over a year ago

I'm surprised this worked; it's in the AOSP source as sdk.buildtools, not sdk.build.tools, and that was the name that worked for me.

Peter Mortensen · Accepted Answer · 2013-12-21 07:20:37Z

7

Right click on project >> Properties >> Android >> API Level 18 worked for me. But before I did that I did right click on project >> Android Tools >> Add Support Library and restarted Eclipse. You may have to play around with your selected API level.

edited Dec 21, 2013 at 7:20

Peter Mortensen

31.4k22 gold badges110 silver badges134 bronze badges

answered Nov 10, 2013 at 13:57

learner

11.9k27 gold badges101 silver badges180 bronze badges

2 Comments

Jayesh Over a year ago

What about API level below 18 ? How can we run application below API level 18 ?

user914425 Over a year ago

I had to add project->Android Tools->Add Support Library and it install ADT 19.0.1 Support Library. After that it generates apk fine.

Peter Mortensen · Accepted Answer · 2013-12-21 07:22:40Z

7

After the installation of the new SDK, there is a new folder, "Android Dependencies", under your project file. If you right click and remove it from the build path, you will again be able to build your project.

edited Dec 21, 2013 at 7:22

Peter Mortensen

31.4k22 gold badges110 silver badges134 bronze badges

answered Nov 12, 2013 at 7:38

Mahendra Liya

13.3k14 gold badges94 silver badges115 bronze badges

2 Comments

Salsero69 Over a year ago

I noticed that this folder would cause a duplicate JAR issue. But deleting it didn't resolve my problem.

Mahendra Liya Over a year ago

@Salsero69 Are you using a library project as a reference in your actual project?

Harshid Vasoya · Accepted Answer · 2013-12-03 07:15:48Z

Update

right click your project > android tools > android support library

Clean your project and try to built.

Peter Mortensen · Accepted Answer · 2013-12-21 07:21:54Z

I had the same problem after updating to Revision 19. Just do not forget to update ADT, https://dl-ssl.google.com/android/eclipse/. After this, I was able to build project with the latest revision.

Zsolt Boldizsar · Accepted Answer · 2013-12-06 08:31:47Z

3

I fixed this problem without downloading the support library or reverting the build tools to 18.1.1. I simply changed the API level to 16+ and the problem vanished. Hope it will help.

answered Dec 6, 2013 at 8:31

Zsolt Boldizsar

2,5822 gold badges29 silver badges39 bronze badges

2 Comments

Peter Mortensen Over a year ago

How did you change the API level to 16?

Zsolt Boldizsar Over a year ago

I simply right clicked my project, and selected Android from the list. It should show up a list of installed android API versions, select the one which has 16 as API level(4.1.2).

Jacob Tabak · Accepted Answer · 2013-12-20 19:32:21Z

None of the other solutions here worked for me after upgrading to Android Studio 0.4.0 and Gradle 1.9.

I resolved the problem by downloading Build Tools 19.0.1 and updating the following line in my build.gradle files:

buildToolsVersion '19.0.0'

to

buildToolsVersion '19.0.1'

Yes, this issue seems fixed in 19.0.1. Also worked fine with "ant debug".

Adí · Accepted Answer · 2013-12-10 20:23:47Z

2

For the ones facing issue with IntelliJ IDEA 13, uninstall Build Tools 19.

answered Dec 10, 2013 at 20:23

Adí

85412 silver badges27 bronze badges

Comments

Arif Amirani · Accepted Answer · 2014-03-02 17:10:19Z

Had the same issue with target version 19 on both project.properties and AndroidManifest.xml with Ant.

Fixed it by:

Uninstalled Android SDK Build-Tools 19.0.1
Installed Android SDK Build-Tools 19.0.2

I think @Al-Kathiri-Khalid is spot on. The issue is only due to missing support for the API level in Build Tools.

Jim Vitek · Accepted Answer · 2013-11-04 20:01:12Z

I had the same problem, though my project did not use the support library. Adding libs/android-support-v4.jar to the project worked around the problem without needing to revert the build tools back from v19.

Peter Mortensen · Accepted Answer · 2014-01-31 22:53:39Z

I solved this problem. Just make this change in the project properties file:

target=android-18 sdk.build.tools=18.1.1

And in the manifest file:

uses-sdk android:minSdkVersion="8" android:targetSdkVersion="18"

harikrishnan · Accepted Answer · 2013-11-13 11:29:05Z

Add the Library file in project.. Project->right click->Properties->android->Library-> click Add and select the Library Project and give apply and ok.. then, clean the project and run again.. if you want restart the eclipse..

And also, sometimes, need to update Android SDK build tools..

Chinciusan Marian · Accepted Answer · 2013-12-10 15:26:05Z

What worked for me was this: I opened the project.properties file from the root of my project and changed target=android-8 to target=android-17

alkathirikhalid · Accepted Answer · 2013-12-20 09:56:08Z

java.nio.BufferOverflowException during from dex error This means you don't have the supporting API for that level hence the build fails, there are a number of ways you can fix this.

Check your manifest file uses-sdk android:minSdkVersion="4" and android:targetSdkVersion="14"

Any of the below will fix the problem:-

Download the required API level (This might take time) and run your application again
Quick dirty fix change your Project target in project.properties to your new target target=android-4
Quick clean fix, change the SdkVersion in your manifest and Clean your project to add the changes to your project.properties (My favorite)

Peter Mortensen · Accepted Answer · 2013-12-21 07:19:29Z

I removed the previous Android SDK and Eclipse. I installed the ADT bundle and it works...

This fixed the problem of BufferOverflow on Dex that started after I got API 19. I was previously using Eclipse with Android SDK installed as an add-on package.

Junaid · Accepted Answer · 2014-06-21 19:30:47Z

Right click on Project>>Properties>>Android and select API Level greater than 15

OR

Add google-play-services_lib to your project by right clicking on project and selecting Project>>Properties>>Android>>Add

Collectives™ on Stack Overflow

Android dex gives a BufferOverflowException when building

19 Answers 19

14 Comments

1 Comment

7 Comments

4 Comments

2 Comments

2 Comments

Comments

Comments

2 Comments

1 Comment

Comments

Comments

Comments

Comments

Comments

Comments

Comments

1 Comment

Comments

Linked

Hot Network Questions

Collectives™ on Stack Overflow

19 Answers 19

14 Comments

1 Comment

7 Comments

4 Comments

2 Comments

2 Comments

Comments

Comments

2 Comments

1 Comment

Comments

Comments

Comments

Comments

Comments

Comments

Comments

1 Comment

Comments

Linked

Related