DexIndexOverflowException issue after updating to latest appcompat and support library

Question

I'm using the below settings through gradle:

compileSdkVersion 21
ANDROID_BUILD_MIN_SDK_VERSION=14
ANDROID_BUILD_TARGET_SDK_VERSION=21
ANDROID_BUILD_TOOLS_VERSION=21.0.2
ANDROID_BUILD_SDK_VERSION=21

I also have the following settings in my gradle file:

compile 'com.android.support:support-annotations:21.0.0'
compile 'com.android.support:appcompat-v7:21.0.0'
compile 'com.android.support:support-v4:21.0.0'

I always get the error UNEXPECTED TOP LEVEL EXCEPTION.
But when I make the 21.0.0 to 20.0.0 it works fine...but i'm not able to access any of the Android API 21 options. Is there something i'm doing wrong here? How do I get it to compile without this exception? I do not have the support jars anywhere else outside of other grade projects (facebook etc.).

Here is the full stack trace:

UNEXPECTED TOP-LEVEL EXCEPTION:
com.android.dex.DexIndexOverflowException: method ID not in [0, 0xffff]: 65536
    at com.android.dx.merge.DexMerger$6.updateIndex(DexMerger.java:502)
    at com.android.dx.merge.DexMerger$IdMerger.mergeSorted(DexMerger.java:283)
    at com.android.dx.merge.DexMerger.mergeMethodIds(DexMerger.java:491)
    at com.android.dx.merge.DexMerger.mergeDexes(DexMerger.java:168)
    at com.android.dx.merge.DexMerger.merge(DexMerger.java:189)
    at com.android.dx.command.dexer.Main.mergeLibraryDexBuffers(Main.java:454)
    at com.android.dx.command.dexer.Main.runMonoDex(Main.java:302)
    at com.android.dx.command.dexer.Main.run(Main.java:245)
    at com.android.dx.command.dexer.Main.main(Main.java:214)
    at com.android.dx.command.Main.main(Main.java:106)

Yep, I'm simply updating my app from API 19 to 21. All libraries from previous version and all the new libraries for 21. — KVISH, Oct 22 '14 at 19:38

score 148 · Accepted Answer · edited Sep 23 '17 at 02:41

148

This message sounds like your project is too large.

You have too many methods. There can only be 65536 methods for dex.

Since the gradle plugin 0.14.0 and the Build Tools 21.1.0 you can use the multidex support.

Just add these lines in the build.gradle:

android {

    defaultConfig {
        ...

        // Enabling multidex support.
        multiDexEnabled true
    }
    ...
}

dependencies {
  compile 'com.android.support:multidex:1.0.1'
}

Also in your Manifest add the MultiDexApplication class from the multidex support library to the application element

<?xml version="1.0" encoding="utf-8"?>
<manifest xmlns:android="http://schemas.android.com/apk/res/android"
    package="com.example.android.multidex.myapplication">
    <application
        ...
        android:name="android.support.multidex.MultiDexApplication"> 
        ...
    </application>
</manifest>

If you are using a own Application class, change the parent class from Application to MultiDexApplication.

edited Sep 23 '17 at 02:41

Graham

7,431
18
59
84

answered Oct 22 '14 at 19:47

Gabriele Mariotti

320,139
94
887
841

`multi-dex` was the reason for that. – KVISH Oct 22 '14 at 21:07
6

Add multiDexEnabled true to the defaultConfig of your build.gradle file – Elhanan Mishraky Jan 11 '15 at 15:51
I don't use build gradle file to build my app. Anyway to overcome this issue.? – Ashokchakravarthi Nagarajan Oct 23 '15 at 06:45
interestingly only adding gradle config worked for me. Was the manifest config optional ? – Abhijit Gujar Oct 09 '16 at 16:05
I had to use the AndroidManifest.xml change in @georgehardcore's answer to get this to work. – The Unknown Dev Feb 11 '17 at 22:11
@KimberlyW you may have just forgotten the forward slash to close the meta data element. Called a self-closing tag. https://www.w3schools.com/xml/xml_elements.asp – josh527 Mar 16 '17 at 21:37
i had to change the tag in the android manifest file to `` to get it to work for me. I'm using a multi-module project....if i didnt i'd get this error: `INSTALL_PARSE_FAILED_MANIFEST_MALFORMED ` – Eric Mar 19 '17 at 07:47
1

Thanks, it was very important and help me a lot. – Weverton Peron Oct 20 '17 at 19:00
You dont have to do anything to your Manifest. Gradle is enough. – Placeable Aug 31 '18 at 12:19

georgehardcore · Answer 2 · 2017-08-22T13:54:36.543

45

1) add dependency to application build.gradle file

compile 'com.android.support:multidex:1.0.2'

2) If you do not override the Application class, edit your manifest file to set android:name in the tag as follows:

<?xml version="1.0" encoding="utf-8"?>
<manifest xmlns:android="http://schemas.android.com/apk/res/android"
    package="com.example.myapp">
    <application
            android:name="android.support.multidex.MultiDexApplication" >
        ...
    </application>
</manifest>

If you do override the Application class, change it to extend MultiDexApplication (if possible) as follows:

public class MyApplication extends MultiDexApplication { ... }

Or if you do override the Application class but it's not possible to change the base class, then you can instead override the attachBaseContext() method and call MultiDex.install(this) to enable multidex:

public class MyApplication extends SomeOtherApplication {
  @Override
  protected void attachBaseContext(Context base) {
     super.attachBaseContext(base);
     MultiDex.install(this);
  }
}

3) Add multidex support to defaultConfig at build.gradle

defaultConfig {
        ...
        minSdkVersion 16
        targetSdkVersion 26
        ...
        // Enabling multidex support.
        multiDexEnabled true
    }
...

edited Aug 22 '17 at 13:54

answered Jun 05 '15 at 07:30

georgehardcore

975
14
12

Perfect! @georgehardcore – benchuk Sep 07 '15 at 13:35
@georgehardcore: i used second point, in my android eclipse project.but still it is showing same error. – Nageswara Rao.CH Oct 05 '15 at 11:13
try to split google-play-services library if you are uisng it. For example, if you use analytics and gcm just plug them as separate modules with base module like: compile 'com.google.android.gms:play-services-base:8.1.0' compile 'com.google.android.gms:play-services-analytics:8.1.0' compile 'com.google.android.gms:play-services-gcm:8.1.0' – georgehardcore Oct 22 '15 at 13:25
@georgehardcore not sure if step #2 would be needed, 'cos it didn't help me on my application. So I skip it and the rest of the steps worked great! – Vu Nguyen Dec 07 '15 at 23:16
For me it worked but without changing Application class to MultiDexApplication in the manifest nor MyApplication class – Amt87 Jun 19 '16 at 10:11

Andrei · Answer 3 · 2016-06-13T03:11:13.017

3

Before messing around with MultiDex

It either solution is too big (use MultiDex) or you compile and include in your project some not needed stuff. I got this issue on my tiny project. Here is what I did to fix it:

I removed this from build.gradle:

dependencies {
    compile fileTree(dir: 'libs', include: ['*.jar'])
}

And I manually removed my build folder from application root. Problem fixed.

edited Jun 13 '16 at 03:11

answered Jun 13 '16 at 02:53

Andrei

42,814
35
154
218

score 2 · Answer 4 · edited Jul 17 '17 at 14:51

2

Follow this guide to workaround 65K limit.

I solved this issue in gradle by setting multiDexEnabled true and extending my application with class MyApp extends MultiDexApplication

edited Jul 17 '17 at 14:51

Jeffin

1,099
12
23

answered Jan 18 '15 at 22:32

Iñaqui

251
4
9

score 0 · Answer 5 · edited Sep 07 '16 at 10:31

0

I simply commented out the compile filetree(include: ['*.jar'], dir: 'libs') in the build.gradle file (as suggested above) and rebuilt the project. Compiled without any errors. I did not need to move any folders.

edited Sep 07 '16 at 10:31

Viral Patel

32,418
18
82
110

answered Sep 07 '16 at 03:57

Earl Allen

29
5

1

Disregard my comment - subsequent rebuilds generated the same original error even when I manually deleted the build folder. – Earl Allen Sep 07 '16 at 04:08

score 0 · Answer 6 · answered Nov 17 '16 at 11:43

First make sure that minification is enabled in app/build.cradle:

buildTypes {
    release {
        minifyEnabled true
        proguardFiles getDefaultProguardFile('proguard-android.txt'), 'proguard-rules.pro'
        signingConfig signingConfigs.config
    }
    debug {
        signingConfig signingConfigs.config
    }
}

If this does not solve the issue, enable multidex build for your app.

score 0 · Answer 7 · edited Jul 17 '17 at 11:58

I faced this issue when i had compiled the entire package of Google Play Services APIs into my app. I solved the issue by using selective API.

For example, to include only the Google Fit and Android Wear APIs, replace the following line in your build.gradle file:

compile 'com.google.android.gms:play-services:11.0.2'

with these lines:

compile 'com.google.android.gms:play-services-fitness:11.0.2'
compile 'com.google.android.gms:play-services-wearable:11.0.2'

Issue is explained in following link.

DexIndexOverflowException issue after updating to latest appcompat and support library

7 Answers7

Before messing around with MultiDex

Linked

Related