Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Duplicate class dev.chrisbanes.insetter.DataBinderMapperImpl

See original GitHub issue

This library doesn’t appear to be working.

After just adding the library to the project:

implementation "dev.chrisbanes:insetter-dbx:0.2.0"

And then syncing Gradle files + rebuilding the project, we get the following errors:

Duplicate class dev.chrisbanes.insetter.DataBinderMapperImpl found in modules jetified-insetter-dbx-0.2.0-runtime.jar (dev.chrisbanes.insetter:insetter-dbx:0.2.0) and jetified-insetter-dbx-0.2.0-runtime.jar (dev.chrisbanes:insetter-dbx:0.2.0)
Duplicate class dev.chrisbanes.insetter.DataBinderMapperImpl$InnerBrLookup found in modules jetified-insetter-dbx-0.2.0-runtime.jar (dev.chrisbanes.insetter:insetter-dbx:0.2.0) and jetified-insetter-dbx-0.2.0-runtime.jar (dev.chrisbanes:insetter-dbx:0.2.0)
Duplicate class dev.chrisbanes.insetter.DataBinderMapperImpl$InnerLayoutIdLookup found in modules jetified-insetter-dbx-0.2.0-runtime.jar (dev.chrisbanes.insetter:insetter-dbx:0.2.0) and jetified-insetter-dbx-0.2.0-runtime.jar (dev.chrisbanes:insetter-dbx:0.2.0)
Duplicate class dev.chrisbanes.insetter.InsetterBindingAdapters found in modules jetified-insetter-dbx-0.2.0-runtime.jar (dev.chrisbanes.insetter:insetter-dbx:0.2.0) and jetified-insetter-dbx-0.2.0-runtime.jar (dev.chrisbanes:insetter-dbx:0.2.0)
Duplicate class dev.chrisbanes.insetter.InsetterBindingAdapters$1 found in modules jetified-insetter-dbx-0.2.0-runtime.jar (dev.chrisbanes.insetter:insetter-dbx:0.2.0) and jetified-insetter-dbx-0.2.0-runtime.jar (dev.chrisbanes:insetter-dbx:0.2.0)

The external libraries being fetched are the following:

Gradle: dev.chrisbanes.insetter:insetter:0.2.0@aar
Gradle: dev.chrisbanes.insetter:insetter-dbx:0.2.0@aar
Gradle: dev.chrisbanes.insetter:insetter-ktx:0.2.0@aar
Gradle: dev.chrisbanes.insetter:insetter-widgets:0.2.0@aar
Gradle: dev.chrisbanes:insetter:0.2.0@jar
Gradle: dev.chrisbanes:insetter-dbx:0.2.0@aar

Issue Analytics

State:
Created 4 years ago
Comments:17 (7 by maintainers)

Top GitHub Comments

1reaction

cosminstefanxpcommented, Mar 4, 2020

Hey. I’m still getting this issue in 0.2.1. Both dependencies get pulled in:

And I get the duplicate class errors as above.

0reactions

chrisbanescommented, May 5, 2020

My guess would be Jitpack, but I have no control over it AFAICT. It builds the artifacts on demand, when someone requests the artifacts.

You could restrict what artifacts you request from Jitpack using using repository filters:

repositories {
    maven {
         url "https://jitpack.io"
         content {
             includeGroup "com.library.iknowcomesfromjitpack"
         }
    }
}