多个dex文件定义Lcom / amazonaws / AmazonWebServiceClient;

时间：2015-07-21 08:34:45

标签： android amazon-web-services android-gradle

我正在尝试在我的Android应用中使用Amazon AWS SDK。该应用已经使用C2Call SDK。该应用程序正在运行，但只要我添加AWS gradle库，它就会开始给我多个Dex文件异常。我搜索了它并且知道它与多次定义的单个库有关，但是我不确定它是从日志中找到的。我尝试删除不同的gradle编译选项，每当我添加一个AWS库时，它都会给出Multiple Dex Exception。

这是我的应用程序的gradle文件 - 

apply plugin: 'com.android.application'

android {
    compileSdkVersion 22
    buildToolsVersion "21.1.2"

    defaultConfig {
        applicationId "com.test.test"
        minSdkVersion 14
        targetSdkVersion 22
        versionCode 1
        versionName "1.0"
    }
    buildTypes {
        release {
            minifyEnabled false
            proguardFiles getDefaultProguardFile('proguard-android.txt'), 'proguard-rules.pro'
        }
    }
}
repositories {
    flatDir {
        dirs 'libs'
    }
}

dependencies {
    compile fileTree(dir: 'libs', include: ['*.jar'])
    /*compile 'com.android.support:appcompat-v7:22.2.0'*/
    compile(name: 'lib-c2callsdk', ext: 'aar')
    compile 'com.amazonaws:aws-android-sdk-cognito:2.2.3'
    compile 'com.amazonaws:aws-android-sdk-ses:2.2.3'
    compile 'com.amazonaws:aws-android-sdk-ddb:2.2.3'
}

我也试过添加和删除appcompact。

这是我得到的错误日志 - 

Information:Gradle tasks [:app:assembleDebug]
Warning:Dependency commons-logging:commons-logging:1.1.1 is ignored for debug as it may be conflicting with the internal version provided by Android.
         In case of problem, please repackage it with jarjar to change the class packages
Warning:Dependency commons-logging:commons-logging:1.1.1 is ignored for release as it may be conflicting with the internal version provided by Android.
         In case of problem, please repackage it with jarjar to change the class packages
:app:preBuild UP-TO-DATE
:app:preDebugBuild UP-TO-DATE
:app:checkDebugManifest
:app:preReleaseBuild UP-TO-DATE
:app:prepareLibC2callsdkLibrary UP-TO-DATE
:app:prepareDebugDependencies
:app:compileDebugAidl UP-TO-DATE
:app:compileDebugRenderscript UP-TO-DATE
:app:generateDebugBuildConfig UP-TO-DATE
:app:generateDebugAssets UP-TO-DATE
:app:mergeDebugAssets UP-TO-DATE
:app:generateDebugResValues UP-TO-DATE
:app:generateDebugResources UP-TO-DATE
:app:mergeDebugResources UP-TO-DATE
:app:processDebugManifest UP-TO-DATE
:app:processDebugResources UP-TO-DATE
:app:generateDebugSources UP-TO-DATE
:app:processDebugJavaRes UP-TO-DATE
:app:compileDebugJava
:app:compileDebugNdk UP-TO-DATE
:app:compileDebugSources
:app:preDexDebug
warning: Ignoring InnerClasses attribute for an anonymous inner class
(org.apache.commons.logging.LogFactory$1) that doesn't come with an
associated EnclosingMethod attribute. This class was probably produced by a
compiler that did not target the modern .class file format. The recommended
solution is to recompile the class from source, using an up-to-date compiler
and without specifying any "-target" type options. The consequence of ignoring
this warning is that reflective operations on this class will incorrectly
indicate that it is *not* an inner class.
warning: Ignoring InnerClasses attribute for an anonymous inner class
(org.apache.commons.logging.LogFactory$2) that doesn't come with an
associated EnclosingMethod attribute. This class was probably produced by a
compiler that did not target the modern .class file format. The recommended
solution is to recompile the class from source, using an up-to-date compiler
and without specifying any "-target" type options. The consequence of ignoring
this warning is that reflective operations on this class will incorrectly
indicate that it is *not* an inner class.
warning: Ignoring InnerClasses attribute for an anonymous inner class
(org.apache.commons.logging.LogFactory$3) that doesn't come with an
associated EnclosingMethod attribute. This class was probably produced by a
compiler that did not target the modern .class file format. The recommended
solution is to recompile the class from source, using an up-to-date compiler
and without specifying any "-target" type options. The consequence of ignoring
this warning is that reflective operations on this class will incorrectly
indicate that it is *not* an inner class.
warning: Ignoring InnerClasses attribute for an anonymous inner class
(org.apache.commons.logging.LogFactory$4) that doesn't come with an
associated EnclosingMethod attribute. This class was probably produced by a
compiler that did not target the modern .class file format. The recommended
solution is to recompile the class from source, using an up-to-date compiler
and without specifying any "-target" type options. The consequence of ignoring
this warning is that reflective operations on this class will incorrectly
indicate that it is *not* an inner class.
warning: Ignoring InnerClasses attribute for an anonymous inner class
(org.apache.commons.logging.LogFactory$5) that doesn't come with an
associated EnclosingMethod attribute. This class was probably produced by a
compiler that did not target the modern .class file format. The recommended
solution is to recompile the class from source, using an up-to-date compiler
and without specifying any "-target" type options. The consequence of ignoring
this warning is that reflective operations on this class will incorrectly
indicate that it is *not* an inner class.
warning: Ignoring InnerClasses attribute for an anonymous inner class
(org.apache.commons.logging.LogFactory$6) that doesn't come with an
associated EnclosingMethod attribute. This class was probably produced by a
compiler that did not target the modern .class file format. The recommended
solution is to recompile the class from source, using an up-to-date compiler
and without specifying any "-target" type options. The consequence of ignoring
this warning is that reflective operations on this class will incorrectly
indicate that it is *not* an inner class.
warning: Ignoring InnerClasses attribute for an anonymous inner class
(org.apache.commons.logging.impl.LogFactoryImpl$1) that doesn't come with an
associated EnclosingMethod attribute. This class was probably produced by a
compiler that did not target the modern .class file format. The recommended
solution is to recompile the class from source, using an up-to-date compiler
and without specifying any "-target" type options. The consequence of ignoring
this warning is that reflective operations on this class will incorrectly
indicate that it is *not* an inner class.
warning: Ignoring InnerClasses attribute for an anonymous inner class
(org.apache.commons.logging.impl.LogFactoryImpl$2) that doesn't come with an
associated EnclosingMethod attribute. This class was probably produced by a
compiler that did not target the modern .class file format. The recommended
solution is to recompile the class from source, using an up-to-date compiler
and without specifying any "-target" type options. The consequence of ignoring
this warning is that reflective operations on this class will incorrectly
indicate that it is *not* an inner class.
warning: Ignoring InnerClasses attribute for an anonymous inner class
(org.apache.commons.logging.impl.LogFactoryImpl$3) that doesn't come with an
associated EnclosingMethod attribute. This class was probably produced by a
compiler that did not target the modern .class file format. The recommended
solution is to recompile the class from source, using an up-to-date compiler
and without specifying any "-target" type options. The consequence of ignoring
this warning is that reflective operations on this class will incorrectly
indicate that it is *not* an inner class.
warning: Ignoring InnerClasses attribute for an anonymous inner class
(org.apache.commons.logging.impl.SimpleLog$1) that doesn't come with an
associated EnclosingMethod attribute. This class was probably produced by a
compiler that did not target the modern .class file format. The recommended
solution is to recompile the class from source, using an up-to-date compiler
and without specifying any "-target" type options. The consequence of ignoring
this warning is that reflective operations on this class will incorrectly
indicate that it is *not* an inner class.
warning: Ignoring InnerClasses attribute for an anonymous inner class
(org.apache.commons.logging.impl.WeakHashtable$1) that doesn't come with an
associated EnclosingMethod attribute. This class was probably produced by a
compiler that did not target the modern .class file format. The recommended
solution is to recompile the class from source, using an up-to-date compiler
and without specifying any "-target" type options. The consequence of ignoring
this warning is that reflective operations on this class will incorrectly
indicate that it is *not* an inner class.
warning: Ignoring InnerClasses attribute for an anonymous inner class
(com.amazonaws.services.s3.model.a.d) that doesn't come with an
associated EnclosingMethod attribute. This class was probably produced by a
compiler that did not target the modern .class file format. The recommended
solution is to recompile the class from source, using an up-to-date compiler
and without specifying any "-target" type options. The consequence of ignoring
this warning is that reflective operations on this class will incorrectly
indicate that it is *not* an inner class.
:app:dexDebug
UNEXPECTED TOP-LEVEL EXCEPTION:
com.android.dex.DexException: Multiple dex files define Lcom/amazonaws/AmazonWebServiceClient;
    at com.android.dx.merge.DexMerger.readSortableTypes(DexMerger.java:596)
    at com.android.dx.merge.DexMerger.getSortedTypes(DexMerger.java:554)
    at com.android.dx.merge.DexMerger.mergeClassDefs(DexMerger.java:535)
    at com.android.dx.merge.DexMerger.mergeDexes(DexMerger.java:171)
    at com.android.dx.merge.DexMerger.merge(DexMerger.java:189)
    at com.android.dx.command.dexer.Main.mergeLibraryDexBuffers(Main.java:454)
    at com.android.dx.command.dexer.Main.runMonoDex(Main.java:303)
    at com.android.dx.command.dexer.Main.run(Main.java:246)
    at com.android.dx.command.dexer.Main.main(Main.java:215)
    at com.android.dx.command.Main.main(Main.java:106)
Error:Execution failed for task ':app:dexDebug'.
> com.android.ide.common.process.ProcessException: org.gradle.process.internal.ExecException: Process 'command 'C:\Program Files\Java\jdk1.7.0_75\bin\java.exe'' finished with non-zero exit value 2
Information:BUILD FAILED
Information:Total time: 25.398 secs
Information:1 error
Information:2 warnings
Information:See complete output in console

如果我只选择其中一个AWS库（例如cognito），则会在没有这些长警告的情况下提供相同的异常。

知道我在这里做错了什么，我怎么才能找到确切的问题？

更新：

我已尝试将以下内容放入应用程序的gradle中 - 

dependencies {
    compile fileTree(dir: 'libs', include: ['*.jar'])
    /*compile 'com.android.support:appcompat-v7:22.2.0'*/
    compile(name: 'lib-c2callsdk', ext: 'aar'){
        exclude group:'gson'
        exclude group:'commons-logging'
    }
    compile ('com.amazonaws:aws-android-sdk-core:2.+'){
        exclude group:'gson'
        exclude group:'commons-logging'
    }
    /*compile 'com.amazonaws:aws-android-sdk-cognito:2.+'
    compile 'com.amazonaws:aws-android-sdk-ses:2.+'
    compile 'com.amazonaws:aws-android-sdk-ddb:2.+'*/
    /*compile 'com.google.code.gson:gson:2.3'*/
}

现在错误减少到了这个 - 

Information:Gradle tasks [:app:assembleDebug]
:app:preBuild UP-TO-DATE
:app:preDebugBuild UP-TO-DATE
:app:checkDebugManifest
:app:preReleaseBuild UP-TO-DATE
:app:prepareLibC2callsdkLibrary UP-TO-DATE
:app:prepareDebugDependencies
:app:compileDebugAidl UP-TO-DATE
:app:compileDebugRenderscript UP-TO-DATE
:app:generateDebugBuildConfig UP-TO-DATE
:app:generateDebugAssets UP-TO-DATE
:app:mergeDebugAssets UP-TO-DATE
:app:generateDebugResValues UP-TO-DATE
:app:generateDebugResources UP-TO-DATE
:app:mergeDebugResources UP-TO-DATE
:app:processDebugManifest UP-TO-DATE
:app:processDebugResources UP-TO-DATE
:app:generateDebugSources UP-TO-DATE
:app:processDebugJavaRes UP-TO-DATE
:app:compileDebugJava UP-TO-DATE
:app:compileDebugNdk UP-TO-DATE
:app:compileDebugSources UP-TO-DATE
:app:preDexDebug UP-TO-DATE
:app:dexDebug
UNEXPECTED TOP-LEVEL EXCEPTION:
com.android.dex.DexException: Multiple dex files define Lcom/amazonaws/AmazonWebServiceClient;
    at com.android.dx.merge.DexMerger.readSortableTypes(DexMerger.java:596)
    at com.android.dx.merge.DexMerger.getSortedTypes(DexMerger.java:554)
    at com.android.dx.merge.DexMerger.mergeClassDefs(DexMerger.java:535)
    at com.android.dx.merge.DexMerger.mergeDexes(DexMerger.java:171)
    at com.android.dx.merge.DexMerger.merge(DexMerger.java:189)
    at com.android.dx.command.dexer.Main.mergeLibraryDexBuffers(Main.java:454)
    at com.android.dx.command.dexer.Main.runMonoDex(Main.java:303)
    at com.android.dx.command.dexer.Main.run(Main.java:246)
    at com.android.dx.command.dexer.Main.main(Main.java:215)
    at com.android.dx.command.Main.main(Main.java:106)
Error:Execution failed for task ':app:dexDebug'.
> com.android.ide.common.process.ProcessException: org.gradle.process.internal.ExecException: Process 'command 'C:\Program Files\Java\jdk1.7.0_75\bin\java.exe'' finished with non-zero exit value 2
Information:BUILD FAILED
Information:Total time: 2.804 secs
Information:1 error
Information:0 warnings
Information:See complete output in console

3 个答案:

答案 0 :(得分：4)

错误说com.amazonaws.AmazonWebServiceClient定义了多次。您可能在项目中引用了几个AWS Android SDK副本，其中一个来自Maven。请你仔细检查libs文件夹下是否有另一个？我不熟悉c2call。不确定其中是否存在与AWS SDK冲突的内容。检查的一种方法是解压缩jar并搜索特定的类。这是一个例子：

unzip -l *.jar | grep AmazonWebServiceClient

至于警告，请随意忽略它。 AWS Android SDK依赖于使用JDK 1.5编译的apache-commons-logging 1.1.1。 Android并不喜欢它，但可以忍受它。

答案 1 :(得分：1)

以下是我为解决问题所做的工作（以帮助那些可能需要未来步骤的人） -

  1. 将AAR文件扩展名更改为zip并将其解压缩。
  2. 打开Extracted文件夹以查找classes.jar
  3. 下载JarJar.jar

  4. 创建一个规则文件，您可以在其中提及需要重构的包或类。这是我的规则文件 - 

    rule com.amazonaws.services.s3.a.* com.jarjar.@0
rule com.amazonaws.services.s3.model.a.* com.jarjar.@0
rule com.amazonaws.services.s3.model.* com.jarjar.@0
rule com.amazonaws.services.s3.* com.jarjar.@0
rule com.amazonaws.sdk.* com.jarjar.@0
rule com.amazonaws.regions.* com.jarjar.@0
rule com.amazonaws.javax.xml.stream.xerces.impl.msg.* com.jarjar.@0
rule com.amazonaws.http.* com.jarjar.@0
rule com.amazonaws.e.* com.jarjar.@0
rule com.amazonaws.d.* com.jarjar.@0
rule com.amazonaws.c.* com.jarjar.@0
rule com.amazonaws.b.* com.jarjar.@0
rule com.amazonaws.a.* com.jarjar.@0
rule com.amazonaws.auth.* com.jarjar.@0
rule com.amazonaws.* com.jarjar.@0
rule com.amazon.device.messaging.development.* com.jarjar.@0
rule com.amazon.device.messaging.* com.jarjar.@0
rule com.amazon.* com.jarjar.@0
rule com.google.gson.stream.* com.jarjar.@0
rule com.google.gson.reflect.* com.jarjar.@0
rule com.google.gson.internal.bind.* com.jarjar.@0
rule com.google.gson.internal.* com.jarjar.@0
rule com.google.gson.annotations.* com.jarjar.@0
rule com.google.gson.* com.jarjar.@0

  5. 运行jarjar.jar。这是一个示例命令 - 

    java -jar "D:\Android\Dev Tools\jarjar-1.4.jar" process jarjarrules.txt lib-c2callsdk\classes.jar classes.jar

  6. 复制生成的classes.jar并将副本转换为zip。提取它以验证重构。

  7. 现在复制生成的classes.jar，并在提取的库文件夹中将旧的classes.jar替换为它。
  8. 将文件夹压缩为zip（记住在根目录上有classes.jar。
  9. 将拉链重命名为aar扩展名。
  10. 在项目中使用新的aar库。
    11. PS：当然，感谢Yangfan建议的解决方案。

答案 2 :(得分：0)

我正在使用AWS重新认知库进行图像识别

使用

时遇到了同样的问题 
implementation 'com.amazonaws:aws-android-sdk-core:2.4.4

在android studio中，我通过替换依赖项解决了问题  jar file dependencies { implementation 'com.android.support:appcompat-v7:26.1.0' implementation 'com.android.support.constraint:constraint-layout:1.0.2' implementation 'com.amazonaws:aws-android-sdk-core:2.2.+' implementation files('yourJarFileLocation/AmazonRekognition/lib/aws-android-sdk-rekognition-2.6.9.jar') 

{{1}}

}

接下来只需清理，重建，运行。它工作

相关问题
最新问题