android-multidex

I have a project in which I have enabled multidex to avoid 65k limit and also productFlavors (dev API 21 and prod API 19) for customization. Building my Project on API 21 i.e dev flavor is successful but on API 19 i.e. prod flavor, it is continuously giving me exception in app task shrink{component}MultiDexComponents Complete Error log: :app:shrinkProdDebugMultiDexComponents FAILED FAILURE: Build failed with an exception. * What went wrong: Execution failed for task ':app:shrinkProdDebugMultiDexComponents'. > java.io.IOException: Can't read [{Project Path}/app/build/intermediates/multi-dex

Dears, I read in many blog posts that multidex apps startup is slower than normal apps. My app uses a lot of libraries that exceed 64k methods so I use multidex. But when I use proguard in release build, the final apk becomes less than 64k methods So My question is: Can I enable multidex in Android debug build only so I don't have runtime error? and disable multi dex in release build as I don't need it? If yes, how ? If No, Is Android smart enough to speedup startup as it should recognize that app didn't exceed 64k even if it is multi dex app ? Yes, you can. When you declare your buildTypes

I am using Android studio 1.2.2. I've integrated maps 4 work sdk, after this the Build is failing, We are using google play services lib in our project (using only com.google.android.gms.tagmanager.*). Now after integrating googlemaps_sdk_m4b_lib, the build is not getting generated. before to this inte Tried looking for including only the tagmanager piece of google_play_services_lib but which is not available as a dependency. Build fails with the following: :nFarmers:dexDebug AGPBI: {"kind":"SIMPLE","text":"UNEXPECTED TOP-LEVEL ERROR:","position":{},"original":"UNEXPECTED TOP-LEVEL ERROR:"}

I am trying to build Multidex apk in eclipse, and not able to succeed. I tried following steps, for configuring Multidex support in android app: I have added the Multidex library located at /extras/android/support/multidex/ to my project. As my app is having custom application class, I have extended android.support.multidex.MultiDexApplication Class to my application. Still i am not able to build apk. Android developer is also not having any documentation for building Multidex apk in eclipse, its only having documentation for gradle and Android Studio. You have to modify build.gradle to add

Building project and deploying app to the emulator with API level 22 or 25 goes ok, but when i try to build APK or deploy app to my real device with API level 16 i get the following error: Error:Execution failed for task ':app:transformClassesWithDexForDebug'. > com.android.build.api.transform.TransformException: com.android.ide.common.process.ProcessException: java.util.concurrent.ExecutionException: com.android.dex.DexException: Multiple dex files define Lcom/google/android/gms/common/api/zza; My project build.gradle file: buildscript { repositories { jcenter() } dependencies { classpath

My project is a Chat app that uses Parse. After added other dependencies, this problem started appearing: Error:Execution failed for task ':app:dexDebug'. com.android.ide.common.process.ProcessException: org.gradle.process.internal.ExecException: Process 'command '/usr/lib/jvm/java-7-oracle/bin/java'' finished with non-zero exit value 2 Searching here in StackOverflow, some folks told me that it could be the 65K limit from Android. So, to solve I followed the steps below: 1 - Add Multidex DefaultConfig { multiDexEnabled true } and compile 'com.android.support:multidex:1.0.0' https://developer

This question already has an answer here: How to resolve java.util.zip.ZipException? 11 answers I'm trying to use the new multidex option but I get the following error: Execution failed for task ':packageAll[Variant]TestClassesForMultiDex'. > java.util.zip.ZipException: duplicate entry: android/support/multidex/BuildConfig.class I've been able to discover the issue only happens when running the connectedAndroidTests task, and not when simply building the project ( build ). There's an issue for this, and it's resolved in multi-dex library 1.0.1, see: Duplicate BuildConfig classes when using