Android编译报错DexArchiveMergerException：无法合并dex求解决

Hey there, I’ve helped dozens of developers work through this exact dex merging error—let’s break down the most common fixes, tailored to your situation. That error usually pops up when there’s a conflict in your dependencies or your app needs to handle multiple dex files, so let’s start with the simplest solutions first.

1. Enable MultiDex Support #

If your app’s minSdkVersion is below 21, Android can’t natively handle more than one dex file (which happens when your code/dependencies exceed the 65k method limit). Here’s how to fix it:

• Add the MultiDex dependency to your app-level build.gradle:

  // For Android Support libraries
  implementation 'com.android.support:multidex:1.0.3'
  // Or for AndroidX
  implementation 'androidx.multidex:multidex:2.0.1'
  

• Enable MultiDex in your defaultConfig block:

  android {
      defaultConfig {
          // ... other configs
          multiDexEnabled true
      }
  }
  

• If you have a custom Application class, update it to extend MultiDexApplication:

  public class MyApp extends MultiDexApplication {
      // ... your app code
  }
  

  If you can’t extend MultiDexApplication, add this to your attachBaseContext method:

  @Override
  protected void attachBaseContext(Context base) {
      super.attachBaseContext(base);
      MultiDex.install(this);
  }
  

2. Fix Dependency Conflicts #

This is the #1 cause of dex merging failures. Your dependencies might be pulling in duplicate libraries or different versions of the same library (like conflicting Support Library versions).

• First, generate a dependency tree to spot conflicts. Run this in your terminal:

  # Mac/Linux
  ./gradlew app:dependencies
  # Windows
  gradlew.bat app:dependencies
  

• Look for duplicate entries (e.g., multiple versions of com.android.support libraries). For example, if your Espresso dependency is pulling in an older Support Library version, exclude it:

  androidTestImplementation('com.android.support.test.espresso:espresso-core:3.0.1') {
      exclude group: 'com.android.support', module: 'support-annotations'
  }
  

• Critical Rule: Make sure all your Support Library (or AndroidX) dependencies use the same version. If you’re using com.android.support:appcompat-v7:28.0.0, every other Support Library dependency should also be 28.0.0.

3. Clean & Rebuild Your Project #

Sometimes the issue is just cached build files acting up:

• Go to Build > Clean Project in Android Studio
• Then run Build > Rebuild Project
• If that doesn’t work, manually delete the app/build folder and the .gradle/caches directory in your project root, then sync your project again.

4. Update Gradle & SDK Tools #

Outdated Gradle plugins or SDK Build Tools can cause compatibility issues:

• Open your project-level build.gradle and update the Android Gradle plugin to the latest stable version:

  dependencies {
      classpath 'com.android.tools.build:gradle:7.4.2' // Use the latest stable version
  }
  

• Make sure your SDK Build Tools version matches the plugin version (you can check this in File > Project Structure > Modules > app > Properties).

Based on the dependencies you shared (JUnit, test runner, Espresso), double-check that your Espresso version is compatible with your Support Library versions—mismatches here are a common culprit for this error.

内容的提问来源于stack exchange，提问作者user9493136