MultiDex support does not work for test APKs [37017515]

Fixed

Bug

[AOSP] FutureRelease

Migrated-Tools-Gradle

Status Update

No update yet.

Description

ku...@gmail.com

created issue #1

Jan 6, 2015 10:52AM

Android Build Tools: 21.1.2
Android SDK version: 21
Android Support Library: 21.0.3
Target API: 21
Minimal API: 10
Use MultiDex: true
Use Tests: true
Use Espresso: true
Use Robolectric: true
Use JaCoCo: true
JaCoCo Library: 0.7.2.201409121644
Coveralls Version: 2.0.1x

STEPS TO REPRODUCE:
1. I try to build simplest library

https://github.com/OleksandrKucherenko/meter
2. in gradle enabled JUnit, Robolectric, Espresso, Mockito, Dagger etc. in total all those things overlap the DEX limit 64k for test APK (androidTestCompile dependencies)
3. I enable option in gradle config - multiDexEnabled true
4. I execute the compilation:
> gradlew :samples:sample-01:assembleDebug :samples:sample-01:assembleDebugTest --info
5. All the times I got the message in output that multi-dex is not enabled
> Trouble writing output: Too many method references: 70023; max is 65536. You may try using --multi-dex option.

EXPECTED RESULTS:
1) Multi dex should work on primary output APK and on test APK!
2) Test APKs should have own configuration section/domain in gradle script

OBSERVED RESULTS:

ADDITIONAL INFORMATION:

This workaround works:
afterEvaluate {
tasks.matching {
it.name.startsWith('dex')
}.each { dx ->
println 'Found Dex tasks: ' +

dx.name

if (dx.additionalParameters == null) {
dx.additionalParameters = []
}
dx.additionalParameters += '--multi-dex' // enable multidex
}
}

ATTACHED FILES:
- build.log - output of the Gradle with --info verbosity level
- build-error.log - error stream/piple of the Gradle execution
- build.gradle - root script
- gralde.properties - build variables
- build.gradle - sampleproject gradle file (with applied workaround!)

build.log

915 KB

View

Download

build-errors.log

139 KB

View

Download

build.gradle

6.1 KB

Download

gradle.properties

2.1 KB

View

Download

build.gradle

17 KB

Download

Comments

ku...@gmail.com <ku...@gmail.com> #2Jan 9, 2015 12:03PM

can you share your android studio version

ku...@gmail.com <ku...@gmail.com> #3Jan 14, 2015 07:01AM

Is this happening with Studio 3.0?

ov...@gmail.com <ov...@gmail.com> #4Mar 9, 2015 09:13AM

Note: This worked for me on Windows 7 Pro 32-bit (with Android Studio 2.3.3). Seems like an issue with adt-branding module (which should contain the "/idea/AndroidStudioApplicationInfo.xml" resource).

ov...@gmail.com <ov...@gmail.com> #5Mar 24, 2015 10:06AM

Hi, also happened on Mac Book Pro 15 retina mi-2015
MacOs Sierra 10.12.6
Android Studio 2.3.3
java version "1.8.0_51"
Java(TM) SE Runtime Environment (build 1.8.0_51-b16)
Java HotSpot(TM) 64-Bit Server VM (build 25.51-b03, mixed mode)

cp...@gmail.com <cp...@gmail.com> #6Jun 23, 2015 09:15PM

Thank you for this feedback. Your feedback helps make sure Android development tools are great! Given your issues has been resolved I am closing this issue.

bm...@gmail.com <bm...@gmail.com> #7Jul 28, 2015 10:22PM

Not sure if this is the same issue, but I'm getting "com.android.dex.DexException: Multiple dex files define Landroid/app/BuildConfig;" when running my instrumentation tests. Regular app runs fine though.

be...@gmail.com <be...@gmail.com> #8Aug 11, 2015 05:44AM

we are experimenting a fancy test setup(calabash+expresso+spoon+wiremock). when putting wiremock stuff into my test apk to run as web server to mock http calls for testing and met same problem I think.

It fails with "com.android.dex.DexIndexOverflowException: method ID not in [0, 0xffff]: 65536" when with gradle having

androidTestCompile 'com.android.support:support-annotations:22.2.1'
androidTestCompile 'com.android.support.test:runner:0.3'
androidTestCompile 'com.android.support.test:rules:0.3'
androidTestCompile 'com.android.support.test.espresso:espresso-core:2.2'
androidTestCompile 'com.android.support.test.espresso:espresso-contrib:2.2'

androidTestCompile 'com.squareup.spoon:spoon-client:+'
androidTestCompile 'info.cukes:cucumber-android:1.2.2'
androidTestCompile 'info.cukes:cucumber-picocontainer:1.2.2'

// wiremock dependency
androidTestCompile 'com.google.guava:guava:18.0'
androidTestCompile 'org.mortbay.jetty:jetty:6.1.26'

androidTestCompile files('libs/jackson-annotations-2.5.0.jar')
androidTestCompile files('libs/jackson-core-2.5.0.jar')
androidTestCompile files('libs/jackson-databind-2.5.0.jar')
androidTestCompile files('libs/json-path-0.9.0.jar')
androidTestCompile files('libs/json-smart-1.1.1.jar')
androidTestCompile files('libs/jsonassert-1.1.1.jar')
androidTestCompile files('libs/ksoap2-android-assembly-3.0.0-jar-with-dependencies.jar')
androidTestCompile files('libs/log4j-1.2.17.jar')
androidTestCompile files('libs/wiremock-android-1.50.jar')
androidTestCompile files('libs/xmlunit-1.6.jar')

it works if marks everything to app api by change androidTestCompile to compile.

je...@google.com <je...@google.com> Aug 31, 2015 04:42AM

Assigned to xa...@android.com.

ku...@gmail.com <ku...@gmail.com> #9Aug 31, 2015 07:54AM

How to validate that its fixed? Any details?

xa...@android.com <xa...@android.com> #10Sep 8, 2015 12:42AM

Marked as fixed.

Will be fixed in the next 1.4 beta.

[Deleted User] <[Deleted User]> #11Sep 25, 2015 02:36PM

Using 1.4-beta2 seems to work for app tests, but doesn't seem to be working for tests in library projects, at least not for instrumentation tests.

mi...@gmail.com <mi...@gmail.com> #12Jan 11, 2016 11:53PM

Any update on this? Has it been fixed?

br...@gmail.com <br...@gmail.com> #13Oct 27, 2016 11:17PM

You need to add "dx.enableIncremental false" to the suggested workaround if your app has incremental enabled.

Issue 37017515

Description

Issue summary

Comments

ku...@gmail.com <ku...@gmail.com> #2Jan 9, 2015 12:03PM

ku...@gmail.com <ku...@gmail.com> #3Jan 14, 2015 07:01AM

ov...@gmail.com <ov...@gmail.com> #4Mar 9, 2015 09:13AM

ov...@gmail.com <ov...@gmail.com> #5Mar 24, 2015 10:06AM

cp...@gmail.com <cp...@gmail.com> #6Jun 23, 2015 09:15PM

bm...@gmail.com <bm...@gmail.com> #7Jul 28, 2015 10:22PM

be...@gmail.com <be...@gmail.com> #8Aug 11, 2015 05:44AM

je...@google.com <je...@google.com> Aug 31, 2015 04:42AM

ku...@gmail.com <ku...@gmail.com> #9Aug 31, 2015 07:54AM

xa...@android.com <xa...@android.com> #10Sep 8, 2015 12:42AM

[Deleted User] <[Deleted User]> #11Sep 25, 2015 02:36PM

mi...@gmail.com <mi...@gmail.com> #12Jan 11, 2016 11:53PM

br...@gmail.com <br...@gmail.com> #13Oct 27, 2016 11:17PM

Add comment

Issue metadata