添加第三方.aar文件后遭遇Unable to merge dex问题求助

Hey there! As someone coming from a C++ background, let me translate this Android-specific issue into terms you might relate to—this is basically the Java/Kotlin equivalent of having two static libraries that both include different versions of the same dependency, leading to linker conflicts. Let’s tackle your questions one by one.

Is it reasonable for third parties to package Guava into an AAR? #

Absolutely not. This is a bad practice in Android library development, similar to how you wouldn’t statically link a common dependency like Boost into every C++ library you distribute. Here’s why:

• AARs are meant to declare dependencies externally (via build.gradle) so the host app can manage version consistency across all modules.
• Packaging dependencies like Guava directly into the AAR’s classes.jar creates unavoidable version conflicts when other modules (like your base module) depend on a different version of the same library.

Alternative solutions besides asking the third party to fix their AAR #

Since you’ve already tried exclude (which only works for declared dependencies, not bundled code) and preDexLibraries (a hit-or-miss workaround), here are actionable fixes:

1. Manually strip Guava from the conflicting B.aar #

This is like editing a static library to remove embedded dependencies. Here’s how:

• Rename B.aar to B.zip and extract its contents.
• Open the extracted classes.jar file with a zip tool, or use the jar command line tool to delete all Guava-related classes:

  jar -d classes.jar com/google/common/**
  

• Re-zip the modified contents back into a zip file, then rename it back to B.aar.
• Replace the original B.aar in your project with this modified version.

Note: This only works if the third party didn’t modify Guava’s code (most cases use the official unmodified version). If they customized Guava, this might break functionality—test thoroughly!

2. Force your entire project to use a single Guava version #

This is analogous to telling your C++ linker to use a specific version of a library regardless of what individual modules request. Add this rule to your root project’s build.gradle to force all dependencies to use Guava 20.0:

allprojects {
    configurations.all {
        resolutionStrategy {
            // Force all modules to use Guava 20.0, overriding conflicting versions
            force 'com.google.guava:guava:20.0'
        }
    }
}

• After adding this, clean and rebuild your project.
• Important: Test all functionality that uses B.aar—Guava 18 to 20 has mostly backward-compatible changes, but there might be edge cases where the older AAR relies on deprecated/removed APIs.

3. Use R8 to automatically resolve duplicate classes #

If you’re using Android Gradle Plugin (AGP) 3.0 or newer, R8 (the modern successor to ProGuard) can automatically detect and remove duplicate class definitions during the build process. Enable it in your app’s build.gradle even for debug builds to test:

android {
    buildTypes {
        debug {
            minifyEnabled true
            useProguard false
            proguardFiles getDefaultProguardFile('proguard-android-optimize.txt'), 'proguard-rules.pro'
        }
    }
}

• R8 will strip out duplicate Guava classes from the B.aar since your base module already includes the newer version.
• Note: Enabling minification in debug mode might slow down builds slightly and make debugging harder, but it’s a quick way to verify if this fixes the issue before relying on it for release.

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