Material-dialogs: Failed to resolve non-core modules with 2.0.0 extension modules

[clarklak11]

• [x] I have verified there are no duplicate active or recent bugs, questions, or requests
• [x] I understand that versions below 2.0.0 will no longer be supported for updates.
• [x] I have given my issue a non-generic title.
• [x] I have read over the documentation (before asking questions on how to do something).

---

Include the following:

• Material Dialogs version: 2.0.0-alpha*

    implementation "com.afollestad.material-dialogs:core:2.0.0-alpha05"
    implementation "com.afollestad.material-dialogs:input:2.0.0-alpha05"

Temporary Workaround

Add this to your repositories:

maven { url "https://dl.bintray.com/drummer-aidan/maven/" }

The module repositories

Core / Input / Files / Color

[afollestad]

Does core resolve?

[afollestad]

Have you tried the workaround mentioned at the bottom of the release notes for alpha01? https://github.com/afollestad/material-dialogs/releases/tag/2.0.0-alpha01

Also, alpha04 was released earlier yesterday

[clarklak11]

Yes, core works properly. Also adding the color dependency produce the same error.

[afollestad]

Hmm, was there anything in your build Gradle logs other than failed to resolve?

[LossyDragon]

I get the following. Manually adding the .aar for colors fails to implement too.

https://i.imgur.com/ltVC6Mc.png

[clarklak11]

Adding this to my repositories fix it. Thanks!

maven { url "https://dl.bintray.com/drummer-aidan/maven/" }

[afollestad]

Glad the workaround works! It's very weird that that's required though, I suspect there is an issue with Bintray linking to jCenter for some reason 🤔

[taar1]

It's not working for me either, rolling back to 0.9.6

[afollestad]

@taar1 there's a workaround as mentioned above.

[taar1]

I've seen that and tried it out but it didn't work in my case either.

[afollestad]

@taar1 so you have something similar to this in your app module's build.gradle?

repositories {
    google()
    jcenter()
    maven { url "https://dl.bintray.com/drummer-aidan/maven/" }
}

dependencies {
    ....
}

[afollestad]

@taar1 @KlaartjeD your app needs to use the same version of AndroidX that this lib does. Your app already resolved the dep just fine, now you're dealing with the local build system.

[farislivemaker]

@afollestad i got a "error: failed linking references." issue while adding core, tried using the workaround in repository still same error..

[afollestad]

@farislivemaker if you're using alpha10 your app needs to be using AndroidX instead of the now-legacy Support Library.

[serjooo]

I just tried installing and ran into the same problem; however, I realized later that I was trying to download the wrong version.

How I thought versioning was done initially that the extension modules take the same version number as the core module. However, after taking a glance at the project I realized that the core module was at 2.0.0-beta6 while input was at 2.0.0-beta1. After I picked beta1 everything worked smoothly after that! Maybe this is the same problem everyone is facing without realizing and I thought it might be helpful mentioning it here.

[LossyDragon]

I'm not sure if this is still relevant to this thread since its closed, but I still get Failed to resolve: com.afollestad.material-dialogs:input:2.0.0-rc1 without the temporary workaround. Putting it back works fine. 🤔

[afollestad]

Huh, I tried all of the modules last night from a fresh project and they resolved fine

[serjooo]

I forgot to mention I had kept the workaround while installing. I was mentioning my issue as it wouldn't compile with the workaround as some other developers. However, yes without the workaround the problem still persists on my side as well.

[FilippoVigani]

Facing this as well. Core works fine, but input needs the mentioned workaround to resolve properly.

[Belka1000867]

Facing the same problem with necessity to implement workaround.
What about the problem "Unresolved reference" if my project does not use androidx, which version should I use?

[iballan]

Adding this line to my app level gradle file solved the problem for me!

configurations.all {exclude group: 'com.android.support', module: 'support-v13'}

[rene-dohan]

maven { url "https://dl.bintray.com/drummer-aidan/maven/" } woks...
Its somehow not pushed to jcenter but don't understand why...

[afollestad]

@rene-dohan yeah there appears to be some sort of syncing issue on jCenter's end 😞

[afollestad]

It appears Bintray does not provide support for this sort of thing unless you're an enterprise customer. Ugh.

[afollestad]

I've filed a ticket with jCenter, awaiting a response now.

[afollestad]

jCenter has relinked all of the dependencies from Bintray to jCenter, and have asked to retry now.

[afollestad]

@clarklak11 @rene-dohan @VeegaP @serjooo ^^

[afollestad]

Definitely appears to be fixed on my end