This message was deleted.

I don't use

dagger-android

but maybe I can have a stab. The

NoSuchElementException

I've seen in the past using guava and doing a

find()

. The dagger-android thing works most using multibinding if anything has gone in from all the articles I've read on it...so perhaps that is the

AndroidMap

. Putting those two things together are you missing a binding that later you are trying to inject? I know Dagger 2.17 focussed a lot on error messaging. Perhaps upgrade to latest to see if you can get more out of the stack as to what binding it can't find in the multimap. And failing that debug info the generated code and see if you can see what binding it is trying to find

@chi I solved this problem by adding

buildscript {
    dependencies {
        classpath("com.android.tools.build.jetifier:jetifier-processor:1.0.0-beta02")
    }
}

to Project

build.gradle.kts