React Native打包生产APK时遇Multiple dex files定义冲突错误

Hey there, let's work through this dex duplicate error you're facing. This issue almost always comes down to duplicate dependencies pulling in the same com.facebook.binaryresource class twice—even though you only added pure JS packages, some of those might have hidden indirect Android dependencies that clash with React Native's built-in Facebook libraries.

Here's a step-by-step fix tailored to your React Native 0.55.4 setup:

1. First, Find the Duplicate Dependency #

Run this command in your project's Android directory to generate a full dependency tree:

./gradlew app:dependencies

Search the output for com.facebook.binaryresource—you’ll spot which libraries are pulling this in twice. Focus on entries outside React Native's core dependencies (like com.facebook.react:react-native:0.55.4), since that’s likely the conflicting third-party package.

2. Exclude the Conflicting Dependency #

Once you’ve identified the culprit, open your app/build.gradle file and modify the dependency declaration to exclude the duplicate Facebook module. For example, if a linked RN package called some-js-package is causing the issue:

implementation(project(':some-js-package')) {
    exclude group: 'com.facebook', module: 'binaryresource'
}

If the dependency comes from a remote Maven package (not a linked RN module), adjust it like this:

implementation('com.example:some-library:1.0.0') {
    exclude group: 'com.facebook', module: 'binaryresource'
}

3. Do a Thorough Cache Cleanup #

You mentioned running gradlew clean, but let’s wipe all stale caches to eliminate any lingering issues:

• Clean Gradle: ./gradlew clean
• Reset React Native's metro cache: react-native start --reset-cache
• Reinstall node modules (in case npm cached a broken dependency):

  rm -rf node_modules && npm install
  

4. Enable MultiDex (Optional but Worth Testing) #

While this error isn’t about hitting the method count limit, enabling MultiDex can sometimes resolve dex merging conflicts in older RN versions. Here’s how:

1. In app/build.gradle, add multiDexEnabled true to your defaultConfig:

   defaultConfig {
       applicationId "com.your.app"
       minSdkVersion 16
       targetSdkVersion 26
       versionCode 1
       versionName "1.0"
       multiDexEnabled true // Add this line
   }
   

2. Add the MultiDex dependency:

   dependencies {
       // ... other dependencies
       implementation 'com.android.support:multidex:1.0.3'
   }
   

3. Update your application class (if you have a custom one) to extend MultiDexApplication, or add this to its attachBaseContext method:

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

5. Verify ProGuard Rules (If Using Obfuscation) #

If you’re using ProGuard in your release build, make sure you’re not accidentally messing with the Facebook classes. Add this line to your proguard-rules.pro file:

-keep class com.facebook.binaryresource.** { *; }

After trying these steps, run ./gradlew assembleRelease again—it should resolve the duplicate dex error.

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