Android Architecture Components: Gradle sync error for dependency version

Question

I'm trying to add ViewModel and LiveData to a Kotlin app. I have the following dependencies added to my module's build.gradle:

implementation "android.arch.lifecycle:extensions:1.1.1"
kapt "android.arch.lifecycle:compiler:1.1.1"
testImplementation "android.arch.core:core-testing:1.1.1"

I'm given the following error:

Android dependency 'android.arch.lifecycle:runtime' has different version for the compile (1.0.0) and runtime (1.1.1) classpath. You should manually set the same version via DependencyResolution

Removing the first line (extensions) fixes the issue, indicating that the error is coming from there, but I can't figure out why.

add ` implementation "android.arch.lifecycle:runtime:1.1.1"` to your dependencies — Arpan Sarkar
– Arpan Sarkar, Commented Apr 25, 2018 at 2:08
Dependency Resolution Force to use a version gist.github.com/cr7pt0gr4ph7/6cd6339eabc2056bc3e7 — Arpan Sarkar
– Arpan Sarkar, Commented Apr 26, 2018 at 11:06

Rubén Viguera · Accepted Answer · 2018-06-13 08:03:30Z

48

As @RedBassett mentions Support libraries depends on this lightweight import (runtime library) as explained at android developers documentation.

This is, android.arch.lifecycle:runtime:1.0.0 is spreading up in the dependency tree as a result of an internal api (transitive) import so in my case I only had to include extensions library as "api" instead of "implementation" so that it will override its version to the highest (1.1.1).

In conclusion, change

implementation "android.arch.lifecycle:extensions:1.1.1"

to

api "android.arch.lifecycle:extensions:1.1.1"

answered Jun 13, 2018 at 8:03

Rubén Viguera

3,6741 gold badge23 silver badges33 bronze badges

Sign up to request clarification or add additional context in comments.

3 Comments

HaydenKai Over a year ago

lifesaver, not sure why this isn't documented some place

dinesharjani Over a year ago

Same here (another lifesaver).

Kirill Karmazin Over a year ago

'api' is less efficient than 'implementation' in terms of build time after changes

sergej shafarenka · Accepted Answer · 2018-04-26 15:52:24Z

24

In your main build.gradle file

allprojects {
    ...

    configurations {
        all {
            resolutionStrategy {
                force "android.arch.lifecycle:runtime:1.1.1"
            }
        }
    }

}

This will enforce version 1.1.1

answered Apr 26, 2018 at 15:52

sergej shafarenka

20.5k7 gold badges72 silver badges89 bronze badges

1 Comment

Brill Pappin Over a year ago

This worked for me. I was unable to figure out where the lower dependency was, as it was most Lilley in an older library.

RedBassett · Accepted Answer · 2018-04-26 14:50:54Z

7

Apparently support-v4 was causing the conflict. In the case of this question, the Gradle dependency task wasn't working correctly, but for anyone else who runs into this issue:

./gradlew :app:dependencies will show the sub-dependencies used by your dependencies. Search the output of this command (changing app for your module name) for the dependency causing the conflict.

answered Apr 26, 2018 at 14:50

RedBassett

3,5973 gold badges36 silver badges61 bronze badges

1 Comment

Brill Pappin Over a year ago

This was the case for me as well, setting the resolutionStrategy above solved the problem.

Sahil Patel · Accepted Answer · 2018-10-13 17:40:33Z

1

@RedBassett is right. However I was still having some problem excluding android.arch.lifecycle related sub dependencies.

In my case the conflict was caused in com.android.support:appcompat-v7:27.1.1.

This is how my gradle dependency looks like after excluding it.

implementation ('com.android.support:appcompat-v7:27.1.1') {
    exclude group: 'android.arch.lifecycle'
}


api "android.arch.lifecycle:runtime:1.1.1"
kapt "android.arch.persistence.room:compiler:1.1.1"

Also, you will have to add this exclude in every imported module.

answered Oct 13, 2018 at 17:40

Sahil Patel

7348 silver badges19 bronze badges

Comments

Adam Johns · Accepted Answer · 2019-03-27 20:07:43Z

0

I searched for all dependencies with ./gradlew :app:dependencies as @RedBassett mentioned. I noticed the incompatible version of android.arch.core:runtime that Gradle was complaining about was stemming from my version of com.android.support:appcompat-v7, so I just updated that version to the latest and everything worked.

answered Mar 27, 2019 at 20:07

Adam Johns

36.6k27 gold badges130 silver badges183 bronze badges

Collectives™ on Stack Overflow

Android Architecture Components: Gradle sync error for dependency version

5 Answers 5

3 Comments

1 Comment

1 Comment

Comments

Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

5 Answers 5

3 Comments

1 Comment

1 Comment

Comments

Comments

Your Answer

Sign up or log in

Post as a guest

Related