Error:Conflict with dependency 'com.google.code.findbugs:jsr305'

问题:

I created a new project in Android Studio 2.2 Preview 1 with Android App and Backend module with Google Messaging. This is the app file

    apply plugin: 'com.android.application'  android {     compileSdkVersion 23     buildToolsVersion "23.0.3"     defaultConfig {         applicationId "com.xxx.xxx"         minSdkVersion 15         targetSdkVersion 23         versionCode 1         versionName "1.0"         testInstrumentationRunner "android.support.test.runner.AndroidJUnitRunner"     }     buildTypes {         release {             minifyEnabled false             proguardFiles getDefaultProguardFile('proguard-android.txt'), 'proguard-rules.pro'         }     } }  dependencies {     compile fileTree(dir: 'libs', include: ['*.jar'])     compile 'com.android.support:appcompat-v7:23.4.0'     compile 'com.android.support.constraint:constraint-layout:1.0.0-alpha1'     compile 'com.google.android.gms:play-services-gcm:9.0.0'     testCompile 'junit:junit:4.12'     androidTestCompile 'com.android.support.test.espresso:espresso-core:2.2.2'     androidTestCompile 'com.android.support.test:runner:0.5'     androidTestCompile 'com.android.support:support-annotations:23.4.0'     compile project(path: ':backend', configuration: 'android-endpoints') } 

But its giving

Error:Conflict with dependency 'com.google.code.findbugs:jsr305'. Resolved versions for app (1.3.9) and test app (2.0.1) differ. See http://g.co/androidstudio/app-test-app-conflict for details.

I am new to android and not able to find what is this error.

回答1:

In your app's build.gradle add the following:

android {     configurations.all {         resolutionStrategy.force 'com.google.code.findbugs:jsr305:1.3.9'     } } 

Enforces Gradle to only compile the version number you state for all dependencies, no matter which version number the dependencies have stated.

回答2:

This is due to espresso. You can add the following to your apps build.grade to mitigate this.

androidTestCompile('com.android.support.test.espresso:espresso-core:2.2.2') {   exclude group: 'com.google.code.findbugs' } 

回答3:

METHOD 1: I deleted the androidTestCompile on espresso-core line which was automatically included in a new project. Then my Android Studio compiles clean.

The androidTestCompile is in "build.gradle (Module:app)":

dependencies {     ...     androidTestCompile('com.android.support.test.espresso:espresso-core:2.2.2', {         exclude group: 'com.android.support', module: 'support-annotations'     })     ... } 

I don't know whether this deletion will have any problem down the road, but it surely works for my current project now.

METHOD 2: Adding an exclude on findbugs works too:

dependencies {     ...     androidTestCompile('com.android.support.test.espresso:espresso-core:2.2.2', {         exclude group: 'com.android.support', module: 'support-annotations'         exclude group: 'com.google.code.findbugs'     })     ... } 

METHOD 3: Forcing compiling with a specific version:

(In the following I force it to compile with the higher version.)

dependencies {     ...     androidTestCompile 'com.google.code.findbugs:jsr305:3.0.0'     ... } 

回答4:

From Gradle Plugin User Guide:

When instrumentation tests are run, both the main APK and test APK share the same classpath. Gradle build will fail if the main APK and the test APK use the same library (e.g. Guava) but in different versions. If gradle didn't catch that, your app could behave differently during tests and during normal run (including crashing in one of the cases).

To make the build succeed, just make sure both APKs use the same version. If the error is about an indirect dependency (a library you didn't mention in your build.gradle), just add a dependency for the newer version to the configuration

Add this line to your build.gradle dependencies to use newer version for both APKs:

compile('com.google.code.findbugs:jsr305:2.0.1')

For future reference, you can check your Gradle Console and it will provide a helpful link next to the error to help with any gradle build errors.

回答5:

When I added module: 'jsr305' as an additional exclude statement, it all worked out fine for me.

 androidTestCompile('com.android.support.test.espresso:espresso-core:2.2.2', { exclude group: 'com.android.support', module: 'support-annotations' exclude module: 'jsr305' 

})

回答6:

The problem, as stated in your logs, is 2 dependencies trying to use different versions of 3rd dependency. Add one of the following to the app-gradle file:

androidTestCompile 'com.google.code.findbugs:jsr305:2.0.1' androidTestCompile 'com.google.code.findbugs:jsr305:1.3.9' 

回答7:

The reason why this happen is that diff dependency use same lib of diff version.
So, there are 3 steps or (1 step) to solve this problem.

1st

Add

configurations.all {     resolutionStrategy.force 'com.google.code.findbugs:jsr305:2.0.1' } 

to your build.gradle file in android {...}

2nd

Open terminal in android studio
run ./gradlew -q app:dependencies command.

3rd

Click Clean Project from menu bar of android studio in Build list.
It will rebuild the project, and then remove code in 1st step.

Maybe you need just exec 2nd step. I can't rollback when error occurs. Have a try.

回答8:

Add this this to dependencies to force using latest version of findbugs library:

compile 'com.google.code.findbugs:jsr305:2.0.1' 

回答9:

1. The accepted answer is one way of fixing the issue, because it will just apply some strategy for the problematic dependency (com.google.code.findbugs:jsr305) and it will resolve the problem around the project, using some version of this dependency. Basically it will align the versions of this library inside the whole project.

2. There is an answer from @Santhosh (and couple of other people) who suggests to exclude the same dependency for espresso, which should work by the same way, but if the project has some other dependencies who depend on the same library (com.google.code.findbugs:jsr305), again we will have the same issue. So in order to use this approach you will need to exclude the same group from all project dependencies, who depend on com.google.code.findbugs:jsr305. I personally found that Espresso Contrib and Espresso Intents also use com.google.code.findbugs:jsr305.

I hope this thoughts will help somebody to realise what exactly is happening here and how things work (not just copy paste some code) :).

回答10:

delete espresso dependencies in gradle file works for me.

delete those lines in app gradle file:

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

回答11:

i was trying to use airbnb deeplink dispatch and got this error. i had to also exlude the findbugs group from the annotationProcessor.

//airBnb     compile ('com.airbnb:deeplinkdispatch:3.1.1'){         exclude group:'com.google.code.findbugs'     }     annotationProcessor ('com.airbnb:deeplinkdispatch-processor:3.1.1'){         exclude group:'com.google.code.findbugs'     } 

文章来源: Error:Conflict with dependency 'com.google.code.findbugs:jsr305'