Warning:Conflict with dependency 'com.android.support:support-annotations'

Question

I have tried almost every trick in the book.

ResolutionStrategy.force
Excluding modules

But nothing seems to work, below is my build.gradle. I'm using Gradle version 1.2.3. Can someone please throw light on what else could be wrong with my code.

The only thing I haven't tried is changing version of Gradle. It's a very basic Espresso Test case. Thanks!

apply plugin: 'com.android.application'
android {
    configurations.all {
        resolutionStrategy.force 'com.android.support:support-annotations:22.1.0'
    }
    compileSdkVersion 22
    buildToolsVersion "21.1.2"

    defaultConfig {
        applicationId "com.example.rasika.job"
        minSdkVersion 16
        targetSdkVersion 22
        versionCode 1
        versionName "1.0"
        testInstrumentationRunner "android.support.test.runner.AndroidUnitRunner"

    }
    buildTypes {
        release {
            minifyEnabled false
            proguardFiles getDefaultProguardFile('proguard-android.txt'), 'proguard-rules.pro'
        }
    }
}
repositories {
    mavenCentral()
}
dependencies {
    compile fileTree(dir: 'libs', include: ['*.jar'])
    compile 'com.android.support:appcompat-v7:22.1.1'

    testCompile 'junit:junit:4.12'

    androidTestCompile 'com.android.support.test:runner:0.3'
    androidTestCompile 'com.android.support.test:rules:0.3'
    androidTestCompile 'com.android.support.test.espresso:espresso-core:2.2'
    androidTestCompile 'com.android.support.test.uiautomator:uiautomator-v18:2.1.1'
    androidTestCompile 'com.android.support.test.espresso:espresso-contrib:2.0'
}

score 52 · Answer 1 · edited May 23 '17 at 12:34

I forked android-topeka google sample and updated appcompat version to 23.1.0, same message:

Warning:Conflict with dependency 'com.android.support:support-annotations'. Resolved versions for app (23.1.0) and test app (23.0.1) differ.

I added:

androidTestCompile 'com.android.support:support-annotations:23.1.0'

Now both resolve to 23.1.0, the warning is gone, and the app and tests still work.

I'm not sure that it's the better solution, so I'm searching for another but found your question.

Update: Read this good explanation by PaulR.

Update2: Confirmed, android-testing google sample does it.

// Testing-only dependencies
// Force usage of support annotations in the test app, since it is internally used by the runner module.
androidTestCompile 'com.android.support:support-annotations:23.0.1'

Update3: Another good response by CommonsWare.

Check your specific versions/conflicts/resolutions using:

./gradlew -q yourmodule:dependencies

Appcompat is 22.1.1 in your case but you are forcing 22.1.0.

Update4: Dependency conflict explained at The Android Build System (Android Dev Summit 2015).

Resolving conflicts between main and test APK

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 ("compile" or "androidTestCompile") that needs it. You can also use Gradle's resolution strategy mechanism. You can inspect the dependency tree by running ./gradlew :app:dependencies and ./gradlew :app:androidDependencies.

Andrew · Answer 2 · 2016-03-02T19:57:59.243

26

I solved the conflict by adding dependency:

androidTestCompile 'com.android.support:support-annotations:23.2.0'

edited Mar 02 '16 at 19:57

answered Dec 27 '15 at 10:32

Andrew

36,676
11
141
113

This worked for me, but not only this library, sometimes other support libraries conflict too. You can add others with androidTestCompile too. Just a reminder for others who has similar problems – Yekmer Simsek Feb 05 '16 at 10:35

Dmitry · Answer 3 · 2016-05-10T16:34:51.433

I had the same issue, solved by this:

// build.gradle
...
android {
    ...
    defaultConfig {
        ...
        testInstrumentationRunner "android.support.test.runner.AndroidJUnitRunner"
    }
}

dependencies {
    ...
    androidTestCompile('com.android.support.test.espresso:espresso-core:2.2') {
        // Necessary if your app targets Marshmallow (since Espresso
        // hasn't moved to Marshmallow yet)
        exclude group: 'com.android.support', module: 'support-annotations'
    }
    androidTestCompile('com.android.support.test:runner:0.3') {
        // Necessary if your app targets Marshmallow (since the test runner
        // hasn't moved to Marshmallow yet)
        exclude group: 'com.android.support', module: 'support-annotations'
    }
}

solution was found here: https://github.com/codepath/android_guides/wiki/UI-Testing-with-Espresso

UPDATE: finally dependencies block in my build.gradle looks like this:

dependencies {
    ...        
    compile 'com.android.support:appcompat-v7:23.2.1'
    compile 'com.android.support:support-v4:23.2.1'
    compile 'com.android.support:design:23.2.1'
    ...     

    // Necessary if your app targets Marshmallow (since Espresso
    // hasn't moved to Marshmallow yet)
    androidTestCompile('com.android.support.test.espresso:espresso-core:2.2.2') {
        exclude group: 'com.android.support'
    }
    androidTestCompile('com.android.support.test.espresso:espresso-intents:2.2.2') {
        exclude group: 'com.android.support'
    }
    androidTestCompile('com.android.support.test:runner:0.5') {
        exclude group: 'com.android.support'
    }
    androidTestCompile('com.android.support.test:rules:0.5') {
        exclude group: 'com.android.support'
    }
    androidTestCompile('com.android.support.test.espresso:espresso-contrib:2.2.2') {
        exclude group: 'com.android.support'
    }
    androidTestCompile('com.android.support:support-annotations:23.2.1') {
        exclude group: 'com.android.support'
    }
    androidTestCompile('com.android.support.test.uiautomator:uiautomator-v18:2.1.2') {
        exclude group: 'com.android.support'
    }
}

this one should be accepted as the best solution, if we only specify the support-annotation module with version in dependency, we can compile but clean project will fail — http8086, Mar 20 '18 at 03:17

score 7 · Answer 4 · answered Oct 15 '15 at 21:40

This happened to me recently when adding the uiautomator. To fix this issue, you need to figure out which dependency or dependencies is using the outdated module. You can do this by wrapping each androidTestCompile dependency into a block, like so:

androidTestCompile ('com.android.support.test.espresso:espresso-core:2.2') {
    transitive = false;
}

This might break some other things though, so you need to be careful. I was able to pinpoint exactly which two of the dependencies was causing this issue for me, and just adding this blocking mechanism to those.

This in conjunction with `./gradlew -q yourmodule:dependencies` is the cleanest. — Joaquim Ley, Jul 15 '16 at 16:35

score 4 · Answer 5 · answered Jan 09 '17 at 11:33

I solved the conflict by excluding the support-annotation library from both runner and espresso-core dependencies:

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

score 3 · Answer 6 · edited Feb 10 '17 at 01:36

3

Add this to your main build.gradle:

allprojects {
    ...
    configurations.all {
        resolutionStrategy.force 'com.android.support:support-annotations:23.1.1'
    }
    ...
}

edited Feb 10 '17 at 01:36

Martin Zeitler

1
19
155
216

answered Nov 05 '15 at 08:29

Sid

1,224
3
23
48

Why the `allprojects` closure? – IgorGanapolsky Mar 15 '16 at 02:00
This will force all resolutions to be done using the Android SDK 23, thus avoiding any conflicts caused by the presence of different sdk's. – Sid Jul 01 '16 at 15:00

score 3 · Answer 7 · answered Apr 12 '16 at 13:02

3

Add follow codes to your dependency block in build.gradle file

compile 'com.android.support:support-annotations:23.2.1'
testCompile 'com.android.support:support-annotations:23.2.1'
androidTestCompile 'com.android.support:support-annotations:23.2.1'

answered Apr 12 '16 at 13:02

TeeTracker

7,064
8
40
46

score 1 · Answer 8 · answered Oct 24 '15 at 03:29

1

androidTestCompile change to testCompile. And remind dont't change it to compile, just need this dependencies to be compiled into our debug APK or test APK.

answered Oct 24 '15 at 03:29

Rocko

11
3

score 1 · Answer 9 · answered Apr 09 '16 at 14:43

1

For me this worked fine

dependencies {

    androidTestCompile 'com.android.support:support-annotations:23.1.1'
}

answered Apr 09 '16 at 14:43

erluxman

18,155
20
92
126

score 1 · Answer 10 · answered Apr 14 '16 at 11:38

1

I solved the conflict by adding dependency:

compile 'com.android.support:appcompat-v7:23.2.1'
 compile 'com.android.support:design:23.2.1'
...
 androidTestCompile 'com.android.support:support-annotations:23.2.1'

answered Apr 14 '16 at 11:38

ayac3j

81
6

score 0 · Answer 11 · answered Mar 16 '16 at 06:52

In also got into the Problem saying

Could not resolve

com.android.support:support-annotations:23.1.0

and tried to find in other servers ,

But what resolved my problem is adding :

google-service.json

file from

https://developers.google.com/mobile/add

and copy and paste it into

YourAndroidProject/app

Then recompile it and i hope your code will fly

score 0 · Answer 12 · answered Jan 06 '17 at 16:52

0

Use this for resolving conflict

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

answered Jan 06 '17 at 16:52

Rahul Yadav

143
6

Please add some details to your answer, such as an explanation of what is wrong in the OP's approach and why your suggestion addresses it. Is this answer valid only because over a year had passed since the question and things are different now? – Dev-iL Jan 06 '17 at 17:15

score 0 · Answer 13 · answered Jul 25 '17 at 17:49

0

I solved the conflict by adding dependency:

androidTestCompile "com.android.support:support-annotations:26.0.0-beta1"

answered Jul 25 '17 at 17:49

Devix

432
5
16

Warning:Conflict with dependency 'com.android.support:support-annotations'

13 Answers13