CODEWITHSUNDEEP
androidandroid-gradle-pluginandroid-support-libraryandroid-library
Anthony
Anthony

Reputation: 7828

Android support library incompatiblity

I have a jcenter library ToggleButtons I develop that I import into my app. After switching to support 26.1.0 in my app, I receive this error:

All com.android.support libraries must use the exact same version specification (mixing versions can lead to runtime crashes). Found versions 26.1.0, 25.3.1

ToggleButtons:

com.android.support:cardview-v7:25.3.1

Main app:

com.android.support:design:26.1.0

I'm using other libraries such as Glide that reference even earlier versions of the support library (I haven't upgraded to 4 yet), but those don't have an issue. Have I designed the library improperly somehow?

Upvotes: 2

Views: 860

Answers (2)

Eugen Pechanec
Eugen Pechanec

Reputation: 38223

Here's what your app depends on:

+ design:26.1.0
  + appcompat-v7:26.1.0
    + support-v4:26.1.0
  + recyclerview-v7:26.1.0
    + support-v4:26.1.0

Here's what the library depends on:

+ cardview-v7:25.3.1 (i.e. at least 25.3.1)

Here's what it means:

  1. Card view library doesn't have any (runtime) dependency on other support libraries so technically in this case it's safe to use different versions. However this may change at any time.
  2. More importantly your own code does not define cardview-v7 as a dependency so there's no way for gradle to know it should pull updated version as well.

The easiest fix then is just defining the dependency in your build.gradle:

def supportLibraryVersion = '26.0.1'
compile "com.android.support:cardview-v7:$supportLibraryVersion"

No force, nothing special. Upgrading a dependency is not a problem. Only downgrading is.

I still don't understand why Glide doesn't throw this error when they're using support 25.

As hinted above, Glide uses at least support-v4 25.x.x. And because a newer version of support-v4 is already requested by your own module, the dependency gets silently upgraded.

Upvotes: 1

Fabio
Fabio

Reputation: 2824

This was always a recommendation, now they're making it generate errors.

You absolutely can't run an app with both versions, because that would cause duplicated classes errors. That means you must pick one of those manually now, while previously gradle would automatically choose one for you.

I'd suggest you use the higher number, since doing the opposite risks missing new features/assets that either library or app really depends on.

You can add this between your android and dependencies blocks in your application / library module's build.gradle for each conflict you must manually solve:

def supportLibraryVersion = '26.0.1'


configurations.all {
    resolutionStrategy {
        force "com.android.support:cardview-v7:$supportLibraryVersion"
    }
}

I guess you get the idea of how it works.

Edit: As noted by @eugen-pechanec the best practice is having all your support libraries with same version throughout all your projects modules. Also, it's best to use the same numbers on build tools (in module's build.gradle, inside android block).

Upvotes: 1

Related Questions