Resolved versions for app (22.0.0) and test app (21.0.3) differ

Asked 11/3, 2015 at 23:12 Answered 9/5, 2018 at 9:56

180

After upgrading to API 22 and support lib revision 22 I'm getting the following warning:

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

Gradle itself is more forgiving, but Android Studio, not so much.

I have no dependencies declared with 21.0.3 ... is one of the dependent libraries using 21.0.3 and Google forgot to update it with the rest of the batch?

My build.gradle with the extras cut out

android {
  compileSdkVersion 22
  buildToolsVersion '22'

  defaultConfig {
    applicationId "com.REDACTED.android"
    minSdkVersion 14
    targetSdkVersion 22
    renderscriptSupportModeEnabled true
    versionName '1.0.0'
    versionCode 100
  }

  buildTypes {
    release {
      minifyEnabled true
      zipAlignEnabled true
      signingConfig signingConfigs.release
    }

    debug {
      minifyEnabled false
      zipAlignEnabled true
      signingConfig signingConfigs.debug
    }
  }

  dependencies {
    provided 'org.projectlombok:lombok:1.16.2'
    googleCompile 'com.google.android.gms:play-services-base:6.5.87'
    compile 'com.android.support:support-v4:22.0.0'
    compile 'com.android.support:appcompat-v7:22.0.0'
    compile 'com.android.support:support-v13:22.0.0'
    compile 'com.android.support:cardview-v7:22.0.0'
    compile 'com.android.support:palette-v7:22.0.0'
    compile 'com.android.support:support-annotations:22.0.0'
    compile 'com.github.chrisbanes.photoview:library:1.2.3'
    compile 'org.apache.commons:commons-lang3:3.3.2'
    compile 'commons-io:commons-io:2.4'
    compile 'commons-codec:commons-codec:1.10'
    compile 'com.jakewharton:butterknife:6.1.0'
    compile 'com.jakewharton:disklrucache:2.0.2'
    compile 'com.squareup:otto:1.3.6'
    compile 'com.squareup.picasso:picasso:2.5.0'
    compile 'com.squareup.retrofit:retrofit:1.9.0'
    compile 'com.squareup.okhttp:okhttp:2.2.0'
    compile 'com.squareup.okhttp:okhttp-urlconnection:2.2.0'
    compile 'com.squareup.okio:okio:1.2.0'
    compile 'com.flaviofaria:kenburnsview:1.0.6'
    compile 'com.edmodo:cropper:1.0.1'
    compile 'com.getbase:floatingactionbutton:1.8.0'
    compile 'com.nispok:snackbar:2.10.2'
    compile 'com.github.ksoichiro:android-observablescrollview:1.5.0'
    compile 'in.srain.cube:grid-view-with-header-footer:1.0.9'
    compile 'de.hdodenhof:circleimageview:1.2.2'
    compile fileTree(dir: 'libs', include: '*.jar')
    // Test Only Dependencies
    androidTestCompile 'com.android.support.test.espresso:espresso-core:2.0'
    androidTestCompile 'com.android.support.test:testing-support-lib:0.1'
    androidTestCompile 'com.android.support.test.espresso:espresso-contrib:2.0'
  }

Update: (Thanks Mark)

Looks like it's espresso-contrib

+--- com.android.support.test:testing-support-lib:0.1 (*)
\--- com.android.support.test.espresso:espresso-contrib:2.0
     +--- com.android.support:recyclerview-v7:21.0.3
     |    +--- com.android.support:support-annotations:21.0.3
     |    \--- com.android.support:support-v4:21.0.3
     |         \--- com.android.support:support-annotations:21.0.3
     +--- com.android.support:support-v4:21.0.3 (*)
     \--- com.android.support.test.espresso:espresso-core:2.0 (*)

Locative answered 11/3, 2015 at 23:12 Comment(8)

The Gradle dependencies task may be able to help you identify the culprit: gradle.org/docs/current/userguide/… – Larine 11/3, 2015 at 23:15

Thanks Mark. It looks like espresso-contrib is the cause... – Locative 11/3, 2015 at 23:39

You can try an exclude to block the 21.0.3 edition of recyclerview-v7, pull in the 22.0.0 edition yourself, and pray that they are sufficiently compatible for espresso-contrib's needs. Personally, I'm amazed that you are maintaining your sanity with that long dependencies list... :-) – Larine 11/3, 2015 at 23:40

Yep. This did the trick. If you put that up as the answer I'll give you the beans :) androidTestCompile ('com.android.support.test.espresso:espresso-contrib:2.0') { exclude module: 'support-annotations' } – Locative 11/3, 2015 at 23:46

My problem was with assertj. Tossing that out there in case it helps anyone :) – Volplane 16/4, 2015 at 1:33

Check here for a solution to this issue. – Anyways 13/8, 2015 at 17:25

My same problem was resolved just by simple android studio restart :) – Tocsin 23/4, 2017 at 17:38

Worth try of @LakhwinderSinghDhillon 's comment above to restart studio. It worked for me 2. – Sing 9/3, 2018 at 12:51

287

Step #1 when dealing with this sort of thing is to get comfortable with command-line Gradle.

Step #2 is to run the Gradle dependencies report (e.g., gradle -q app:dependencies from the project root). This will provide the ASCII tree as shown in the update to the question, and it should help you identify what is asking for the conflicting artifact versions.

Step #3 is to decide what needs replacing. You elected to replace just the conflict (support-annotations). Personally, I would have gone with the root of the wrong-version tree (recyclerview-v7), though for all I know that might not be the best course of action in this case.

Step #4 is to add the exclude directive to block what you chose in Step #3:

androidTestCompile ('com.android.support.test.espresso:espresso-contrib:2.0') {
    exclude module: 'support-annotations'
}

Step #5 is to test the heck out of this change. What you are doing is saying that espresso-contrib has to deal with the 22.0.0 edition of support-annotations. That may work. That may not. It depends on the backwards compatibility of the conflict. In this case, support-annotations should be pretty good about it.

Step #6 is to consume the beverage of your choice, one appropriate for your locale and time of day.

Larine answered 11/3, 2015 at 23:53 Comment(13)

I used exclude group: 'com.android.support', module: 'support-annotations' since your version raised a "cannot infer argument types" warning from gradle – Intensity 20/4, 2015 at 16:43

Works... also consider to apply this to com.android.support.test:runner:0.3, com.android.support.test:rules:0.3 and com.android.support.test.espresso:espresso-core:2.2 – Arborescent 31/7, 2015 at 7:48

In Step #4, where are you adding that androidTestCompile directive ? If I try to add that syntax to my app's dependencies block I get some syntax errors. As this is written now, it's a bit tough to tell precisely where you add it. – Deactivate 25/1, 2016 at 17:59

@OYRM: "where are you adding that androidTestCompile directive ?" -- in dependencies. See this sample from Chiu-Ki Chan. – Larine 26/1, 2016 at 10:3

I had been adding to "dependencies" within the Module gradule file, but must have introduced a typo. After triple checking the syntax, the error is cleared and the androidTestCompile method with it's "exclude" argument has worked exactly as you described – Deactivate 26/1, 2016 at 16:36

Yes, in my case it was com.android.support.test:runner:0.5 that had a dependency on com.android.support:support-annotations:23.1.1 which caused this error. – Fingered 22/3, 2016 at 16:44

Step #6 is key here – Halves 11/4, 2016 at 8:15

@Larine My issue was Resolved versions for app (25.3.0) and test app (23.1.1) differ.I didn't use any annotations. how to solve this. – Gunner 21/3, 2017 at 12:27

@Prasad: Follow the instructions in my answer, particularly Step #2. – Larine 21/3, 2017 at 12:35

@Larine Where should I type the command line. in the terminal. I tried it displays "gradle is not internal or external command" – Gunner 21/3, 2017 at 12:40

@Prasad: In your case, try gradlew in your project root directory, instead of gradle. – Larine 21/3, 2017 at 12:40

stupid question: why can't just each library use their own version of a dependency? – Nelidanelie 16/6, 2017 at 11:32

@lxx: because neither Java nor Android resources work that way. In Java, you cannot have N classes with an identical fully-qualified name (e.g., android.support.v4.app.Fragment). In Android, resources are all combined into a single namespace, merging in all the libraries, plus the app's own resources. – Larine 16/6, 2017 at 11:36

146

What I did to solve it was add the below line in to my build.gradle script

androidTestCompile 'com.android.support:support-annotations:xx.x.x'

Replace xx.x.x with whatever version of support-annotations your app is using - this will be shown in your dependencies, or the Gradle sync message as: Resolved version for app (xx.x.x) should there be a problem syncing.

Swift answered 29/4, 2015 at 15:1 Comment(5)

Wow. I do this for upgrading Junit but totally for got I can do it for other dependencies as well. – Fabricant 7/5, 2015 at 22:33

This is indeed how the Google samples do it, a comment reading "Force usage of support annotations in the test app, since it is internally used by the runner module.". – Dipnoan 21/10, 2015 at 13:28

This was the best answer for me. Note: Must update to '23.1.1': androidTestCompile 'com.android.support:support-annotations:23.1.1' – Esplanade 12/2, 2016 at 2:38

Thanks, in my case the line was already there, but explicitly stated a conflicting version, updated to required one and everything worked like a charm. – Burtie 5/4, 2017 at 12:13

how to add this to the build.gradle? – Haematinic 1/5, 2018 at 10:37

Actually it's a bug of new update version of Espresso Contrib, you can refer this workaround : android-testing/build.gradle

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

Divers answered 29/4, 2015 at 7:33 Comment(5)

This was my problem. Ticket is here. – Praenomen 13/5, 2015 at 18:28

This creates a warning, @RenanNery's solution is better – Vendee 18/8, 2015 at 13:2

That doesn't work. I still get the conflict error because of androidTestCompile 'com.android.support.test:runner:0.5' – Fingered 22/3, 2016 at 17:3

@Divers - Link broken – Cherenkov 7/3, 2017 at 12:32

This worked for me. I put this block in the "android { testOptions { <here> } }" – Babbitt 10/5, 2017 at 3:38

Please refer https://github.com/JakeWharton/u2020/blob/05a57bf43b9b61f16d32cbe8717af77cd608b0fb/build.gradle#L136-L140

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

This solved my issue.

Alternatively you can run gradlew on windows and ./gradlew for mac/linux this will download your dependency when needed

Knorr answered 23/5, 2016 at 12:5 Comment(1)

This also helped me today (2018-11-10), but with version 26.1.0, to avoid a conflict with version 27.1.1. – Scapula 10/11, 2018 at 15:10

I also ran into this problem as well as other conflicts involving appcompat and the solution I found was adding test compiles and setting them to the sdk you are currently using. In my case it's 25, so it looks like this:

androidTestCompile 'com.android.support:support-annotations:25.+'
androidTestCompile 'com.android.support:appcompat-v7:25.+'
androidTestCompile 'com.android.support:support-v4:25.+'
androidTestCompile 'com.android.support:recyclerview-v7:25.+'
androidTestCompile 'com.android.support:design:25.+'

Furthermore, as you can see I added the design dependency, which is related to Android Material Design.

Hope it helps =)

Flub answered 3/2, 2017 at 19:52 Comment(0)

for sdkversion 25

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

Parenthesize answered 25/2, 2017 at 17:53 Comment(0)

you can run gradlew on windows and ./gradlew for mac/linux this will download your dependency when needed.

You can check if one of the library has dependency on the support annotation or any library with is named in error and try to excluded it in gradle something like below

compile("org.apache.maven:maven-ant-tasks:${mavenAntTaskVer}‌") { exclude group: 'junit' }

Error:Conflict with dependency 'junit:junit'. Resolved versions for app (3.8.1) and test app (4.12) differ. See g.co/androidstudio/app-test-app-conflict for details.

this was the error i was getting so I used above gradle line to fix the issue

Knorr answered 14/7, 2016 at 6:19 Comment(1)

This seems a really good way to solve problem like this. And in addition, try to run this ./gradlew :app:dependencies command line under your project root directory, it's will make a tree about your project's dependencies, and have a check carefully, then you'll find where the conflict from. – Agon 11/4, 2017 at 5:51

Simply delete these lines in your build.gradle file:

androidTestImplementation 'com.android.support.test:runner:1.0.2'
androidTestImplementation 'com.android.support.test.espresso:espresso-core:3.0.2'

Infantilism answered 9/5, 2018 at 9:56 Comment(1)

It does not work that way. It causes more errors to the project – Hokum 6/6, 2018 at 8:30

This is common issue in instrumentation test as stated here and can be resolved simply by adding the dependencies for androidTestCompile inside the build.gradle. In my case conflict arised in appcompat, recyclerview and design dependencies. And resolved by adding following lines

    androidTestCompile 'com.android.support:appcompat-v7:23.4.0'
    androidTestCompile 'com.android.support:recyclerview-v7:23.4.0'
    androidTestCompile 'com.android.support:design:23.4.0'

Stenography answered 29/3, 2017 at 14:2 Comment(0)

I was having the same problem with 26.0.0 and 27.1.1 and actually just upgrading the former to the later make it work.

Debrahdebrecen answered 27/4, 2018 at 20:24 Comment(0)

Hot tags

Godot Unity Godot Help Programming Godot 4.X GUI GDScript 3D 2D Physics CSharp Godot 3.X VR XR Projects C++

Recommended topics

Hot tags