Android编译时冲突报错的完美解决方案

最近在项目的整合和接入第三方sdk的过程中多次遇到DexArchiveMergerException/ transformDexArchiveWithExternalLibsDexMergerForDevelop等报错，详细的报错信息如下，一般有如下两种场景，一种是依赖冲突，一种是jar冲突。

场景1：

Caused by: com.android.builder.dexing.DexArchiveMergerException: Error while merging dex archives:
...\app\build\intermediates\transforms\dexBuilder\develop\debug\0.jar,   ...\app\build\intermediates\transforms\dexBuilder\develop\debug\1.jar, ...\app\build\intermediates\transforms\dexBuilder\develop\debug\2.jar,   ...\app\build\intermediates\transforms\dexBuilder\develop\debug\3.jar, ...\app\build\intermediates\transforms\dexBuilder\develop\debug\4.jar,   ...\app\build\intermediates\transforms\dexBuilder\develop\debug\5.jar, ...\app\build\intermediates\transforms\dexBuilder\develop\debug\6.jar,   ...\app\build\intermediates\transforms\dexBuilder\develop\debug\7.jar, ...\app\build\intermediates\transforms\dexBuilder\develop\debug\8.jar,   ...\app\build\intermediates\transforms\dexBuilder\develop\debug\9.jar, ...\app\build\intermediates\transforms\dexBuilder\develop\debug\10.jar,   ...\app\build\intermediates\transforms\dexBuilder\develop\debug\11.jar, ...\app\build\intermediates\transforms\dexBuilder\develop\debug\12.jar,   ...\app\build\intermediates\transforms\dexBuilder\develop\debug\13.jar, ...\app\build\intermediates\transforms\dexBuilder\develop\debug\14.jar,   ...\app\build\intermediates\transforms\dexBuilder\develop\debug\15.jar, ...\app\build\intermediates\transforms\dexBuilder\develop\debug\16.jar,   ...\app\build\intermediates\transforms\dexBuilder\develop\debug\17.jar, ...\app\build\intermediates\transforms\dexBuilder\develop\debug\18.jar,   ...\app\build\intermediates\transforms\dexBuilder\develop\debug\19.jar, ...\app\build\intermediates\transforms\dexBuilder\develop\debug\20.jar,   ...\app\build\intermediates\transforms\dexBuilder\develop\debug\21.jar, ...\app\build\intermediates\transforms\dexBuilder\develop\debug\22.jar,   ...\app\build\intermediates\transforms\dexBuilder\develop\debug\23.jar, ...\app\build\intermediates\transforms\dexBuilder\develop\debug\24.jar,   ...\app\build\intermediates\transforms\dexBuilder\develop\debug\25.jar, ...\app\build\intermediates\transforms\dexBuilder\develop\debug\26.jar,   ...\app\build\intermediates\transforms\dexBuilder\develop\debug\27.jar  
at com.android.builder.dexing.D8DexArchiveMerger.getExceptionToRethrow(D8DexArchiveMerger.java:124)
at com.android.builder.dexing.D8DexArchiveMerger.mergeDexArchives(D8DexArchiveMerger.java: 109)
at com.android.build.gradle.internal.transforms.DexMergerTransformCallable.call(DexMergerTransformCallable.java: 101)
at com.android.build.gradle.internal.transforms.ExternalLibsMergerTransform.transform(ExternalLibsMergerTransform.kt: 123)
at com.android.build.gradle.internal.pipeline.TransformTask$2.call(TransformTask.java: 221)
at com.android.build.gradle.internal.pipeline.TransformTask$2.call(TransformTask.java:217)
at com.android.builder.profile.ThreadRecorder.record(ThreadRecorder.java: 102)
... 122 more
Caused by: com.android.tools.r8.CompilationFailedException: Compilation failed to complete
at com.android.tools.r8.utils.ExceptionUtils.withCompilationHandler(ExceptionUtils.java:76)
at com.android.tools.r8.utils.ExceptionUtils.withD8CompilationHandler(ExceptionUtils.java: 45)
at com.android.tools.r8.D8.run(D8.java: 67)
at com.android.builder.dexing.D8DexArchiveMerger.mergeDexArchives(D8DexArchiveMerger.java: 107)
... 127 more
Caused by: com.android.tools.r8.utils.AbortException
at com.android.tools.r8.utils.Reporter.failIfPendingErrors(Reporter.java: 77)
at com.android.tools.r8.utils.Reporter.fatalError(Reporter.java: 58)
at com.android.tools.r8.utils.ExceptionUtils.withCompilationHandler(ExceptionUtils.java: 67)
... 130 more

场景2：

Caused by: java.lang.RuntimeException: com.android.builder.dexing.DexArchiveMergerException: Error while merging dex archives:
C: android\app\build\intermediates\transforms\dexBuilder\develop\debug\0.jar,
C: android\app\build\intermediates\transforms\dexBuilder\develop\debug\1.jar,
C: android\app\build\intermediates\transforms\dexBuilder\develop\debug\2.jar,
C: android\app\build\intermediates\transforms\dexBuilder\develop\debug\3.jar,
C: android\app\build\intermediates\transforms\dexBuilder\develop\debug\4.jar,
C: android\app\build\intermediates\transforms\dexBuilder\develop\debug\5.jar,
C: android\app\build\intermediates\transforms\dexBuilder\develop\debug\6.jar,
C: android\app\build\intermediates\transforms\dexBuilder\develop\debug\7.jar,
C: android\app\build\intermediates\transforms\dexBuilder\develop\debug\8.jar,
C: android\app\build\intermediates\transforms\dexBuilder\develop\debug\9.jar,
C: android\app\build\intermediates\transforms\dexBuilder\develop\debug\10.jar,
C: android\app\build\intermediates\transforms\dexBuilder\develop\debug\11.jar,
C: android\app\build\intermediates\transforms\dexBuilder\develop\debug\12.jar,

1.对于这种因为冲突导致的问题，一般的解决办法是找到冲突的根源，也就是在androidstudio的Terminal中输入如下命令查看依赖数找到冲突的依赖来解决。

gradlew -q app:dependencies

2.然而对于一个大型项目而言，如上方式并不一定可以轻而易举的找到冲突。因此我们可以尝试在app的build.gradle中进行如下配置。

android{
  ...
}

configurations.all {
  resolutionStrategy {
    force 'com.squareup.okhttp3:okhttp:3.11.0'
    force 'com.squareup.okio:okio:1.14.0'
    force 'com.android.support.constraint:constraint-layout:1.1.1'
    force 'com.google.code.gson:gson:2.8.5'
    force 'com.android.support:appcompat-v7:27.1.1'
    ...
   }
}
configurations.all {
  resolutionStrategy {
    failOnVersionConflict()
  }
}

dependencies {
   ...
}

相信resolutionStrategy大部分人都用过，专门为gradle设置编译的策略，ResolutionStrategy接口中提供了一系列策略方法，我们可以查看源码根据需要选择配置。对于一些冲突的场景，特别是集成了一些第三方的sdk后导致项目因为冲突报错无法编译的场景。我们可以选择直接设置failOnVersionConflict()，目的是在编译时假如有冲突发生，则直接编译失败在控制台打印报错信息，具体的可以查看我项目中的报错。

Could not resolve all dependencies for configuration ':app:productDebugRuntimeClasspath'.
A conflict was found between the following modules:
 - com.squareup.okhttp3:okhttp:3.9.1
 - com.squareup.okhttp3:okhttp:3.2.0
 - com.squareup.okhttp3:okhttp:3.8.0
 - com.squareup.okhttp3:okhttp:3.8.1

这样一下子就知道项目中有哪些依赖冲突了，然后将冲突的依赖选择号版本添加到如下的配置中强制指定即可。
configurations.all {
  resolutionStrategy {
    force 'com.squareup.okhttp3:okhttp:3.11.0'
    ...
   }
}

可以有些人会有疑问，我项目多个module中多次引入同一个依赖也没有冲突啊，其实gradle在编译时将所有的依赖都引入了，只不过在我们代码中引用时，gradle默认使用的时最高版本的依赖而已。通过上面的方式可以解决几乎百分之九十的冲突。另外你还会发现这么设置后整个app的大小还会减少不少，因为我们强制指定后，gradle不在将重复的依赖全部引入最终打包到dex中，所以app的体积当然就减少了。

3.通过以上两种方式几乎可以解决百分之九十的冲突，但是还有一种场景的冲突还是无法解决。假如我们项目引入了一个第三方的sdk,他里面引入了一个高德地图及定位功能，我们项目中也引入了高德地图的猎鹰轨迹功能，而猎鹰轨迹功能只能以jar包的形式引用（猎鹰jar包中也引了高德定位功能），这样我们编译项目时，必然会导致冲突，而且这种冲突是无法通过配置gradle来解决的。那该如何是好呢？这个时候就该拿出大杀器了。

对于这种场景我们可以使用jarjar.jar，将第三方比如说高德猎鹰jar等包名进行替换，这样在项目编译打包生成dex文件时就不会因为同名文件导致冲突。

以上就是解决依赖冲突的所有办法，一般的冲突都可以配置gradle进行解决，对于一些疑难杂症只能使用偏方了。