@dawidhyzy Neither. It was what @christiangruber mentioned. There was a github issue as well with the same problem. Thanks both!

if you are using gradle make sure you are using kapt and not apt or annotationProcessor. and the obvious, did you put

@Component

on it?

you are in control of ViewHolder creation in your adapter so you should use constructor injection

So has anyone created a custom scope while using dagger android components?

Oops, you're right, thanks, I was running the build with intellij and it didn't give me dagger error that I was missing a

@Provides

, only when I ran in terminal, I saw it, now everything works! Your 'did you see `kaptGenerateStubs`' question made me look there ... 😊

Thanks @gildor! Now I'm having another error:

java.lang.NoClassDefFoundError: javax/inject/Provider

, when running?

Could I ask another question @gildor? Given:

@Provides @Singleton fun provideOdooClient(xmlRpcCoroutineClient: XmlRpcCoroutineClient): OdooClient =
			OdooClientImpl(
					xmlRpcCoroutineClient,
					System.getenv("ODOO_HOST"),
					System.getenv("ODOO_PORT")?.toInt(),
					System.getenv("ODOO_DB")
			)

	@Provides @Named("isOdooClientReady") fun provideOdooClientStatus(odooClient: OdooClient): Deferred<Boolean> =
			odooClient.login(
					System.getenv("ODOO_USER"),
					System.getenv("ODOO_PASS")
			)

And (in main verticle):

@Inject @Named("isOdooClientReady") lateinit var isOdooClientReady: Deferred<Boolean>

Is there any reason I should be getting

ModelComponent.java:10: error: kotlinx.coroutines.experimental.Deferred<java.lang.Boolean> cannot be provided without an @Provides- or @Produces-annotated method.
    public abstract void inject(@org.jetbrains.annotations.NotNull()

?

How can I deal with generated code that refers to classes that do not exists after I switch branch in git besides manually running clean?

Hi! Our team is having issues with

kapt

tasks running for long minutes. We only use

kapt

for Dagger. Is there any known issues, that I couldn't find with my hours of googling on the topic? We use parallel task execution for many modules (of an Android app), and the result is still 10 minutes, which is made up mostly from dexing and

kapt

. We tried upgrading every library including Dagger, and the issue persists. Do you have any suggestions?

Hello! How are you guys setting up kotlin + dagger2? Is there a way to make IntelliJ automatically run kapt as part of building (Ctrl+F9)? I am trying to use Dagger 2 in a Kotlin / maven project Here is what I tried: (1) setup add dagger-compiler as a dependency. "Settings > Build, Execution, Deployment > Compiler > Annotation Processors" for my maven module has "Enable annotation processing" checked and "Obtain processors from project classpath" So I quickly realized that option (1) obviously won't work if I write my dagger components and modules in kotlin code. So I tried (2) setup the kotlin maven plugin to run kapt with dagger2:

<plugin>
                <artifactId>kotlin-maven-plugin</artifactId>
                <groupId>org.jetbrains.kotlin</groupId>

                <executions>
                    <execution>
                        <id>kapt</id>
                        <phase>compile</phase>
                        <goals>
                            <goal>kapt</goal>
                        </goals>
                        <configuration>
                            <sourceDirs>
                                <sourceDir>src/main/kotlin</sourceDir>
                                <sourceDir>src/main/java</sourceDir>
                            </sourceDirs>
                            <annotationProcessorPaths>
                                <!-- Specify your annotation processors here. -->
                                <annotationProcessorPath>
                                    <groupId>com.google.dagger</groupId>
                                    <artifactId>dagger-compiler</artifactId>
                                    <version>2.16</version>
                                </annotationProcessorPath>
                            </annotationProcessorPaths>
                        </configuration>
                    </execution>
                </executions>
            </plugin>

This works from maven, but IntelliJ is completely clueless. By this, I mean that no additional files are generated in my target directory when I press Ctrl+F9 (or choose to rebuild the module). There is only a "classes" directory there. (3) as a quick test I also tried a small gradle project. The only way I could get it to work was to delegate compile to gradle (Settings > Build, Execution, Deployment > Build Tools > Gradle > Runner -> enable: "Delegate build/run actions to gradle") But this means it's gradle that compiles & runs kapt, not IntelliJ. So now I'm out of ideas. Is there a way to make IntelliJ automatically run kapt as part of building (Ctrl+F9)? Or is basically dagger 2 useless on a maven + Kotlin project? If I have to do "mvn clean package" every time I change a class, that makes dagger 2 useless for me (and for anyone that cares about development productivity). Also, if you use gradle + dagger 2 + kotlin and you delegate build/run actions to gradle, doesn't this make the whole compilation unbearably slow? Especially given the fact that apparently kapt cannot run in gradle incremental mode (https://youtrack.jetbrains.com/issue/KT-11978).

I ran into this a long while ago when I was in a mixed java/kotlin project and don't think kotlin's compiler will emit bytecode without at least the wildcard generic. you might need to do the module in java to work around it or more appropriate would probably be to modify all the injection sites to match what the kotlin module exposes. If you were a peer on my team I would say something like lets follow effective java and

Don’t use raw types

C:\neuber\adt-bundle-windows-x86_64-20140702\sdk\wHome\app\src\main\java\neuberfran\com\whome\core\dagger\AppInjector.kt: (10, 9): Unresolved reference: DaggerAppComponent

This message was deleted.

So the Dagger implementation was in this code base before I got here (third day in the code base), and the app was building and deploying successfully. I added DataBinding to an

Activity

refactor, and now am running into these issues where the DataBinding is failing. After a lot of debugging, I discovered that if I remove:

implementation 'com.google.dagger:dagger-android:$project.daggerVersion'

it successfully builds the DataBinding components (while failing on the Android-Dagger specific ones, obviously.) It is worth noting that DataBinding builds fine with the standard Dagger 2 include

implementation "com.google.dagger:dagger:$project.daggerVersion"

, it is only the Android specific module that is failing me I'm not receiving large blocks of errors, but I appreciate that suggestion either way.

Does anyone have a convinient way to disable code formatting only for debug build in android?

Is there a preference between @Named qualifier or custom qualifiers when dealing with different dependencies of same type?

I personally prefer custom qualifier to get autofill and avoid any string typo with @Named

Hey @Sam - nah. It's a proper "high end" optimisation even for those Java users. I looked it up a while back and end up just doing the older style for my Kotlin modules and moved on. Be good to know if I was wrong on this point though? I think our time would be better spent turning things lazy if they need be and obvs not doing anything slow in the provisioning blocks.

Better way of handling direct bindings with kotlin is to just declare another abstract module which will hold only

@Binds

bindings and then just include it via

submodules

, so you don't have to do

@JvmStatic

nonsense.

I'm running into a issue where Dagger multibinding into a map fails compilation when i use Class as a key but works fine with String as a key for the map. With Class key, Dagger claims "cannot be provided without an @Provides-annotated method". Any pointers?

If you use Dagger with Kotlin, please upvote the addition of 'Incremental Annotation Processing' to

kapt

, lack of which is currently preventing Kotlin projects benefiting from the latest incremental features in both Gradle and Dagger2: https://youtrack.jetbrains.com/issue/KT-23880

afterEvaluate {
        extensions.findByName('kapt')?.arguments{
            arg("dagger.formatGeneratedSource","disabled")
            arg("dagger.gradle.incremental","enabled")
        }
    }

gradle is giving warning

The following options were not recognized by any processor: '[dagger.gradle.incremental, kapt.kotlin.generated, dagger.formatGeneratedSource]'

class DetailViewModelFactory(private val id: Int) : ViewModelProvider.Factory {
    private val movieRepository: MovieRepository = Injector.getAppComponent().getMovieRepository()

I was wondering if this piece of code could be rewritten in primary and secondary constructor form where

MovieRepository

injected via Dagger 2. (Code:- https://github.com/sudhirkhanger/Genius)

What exactly do you mean by "component-to-component deps"?

whats the best way to go about constructor injection in kotlin?

Has anyone implemented dagger in modular projects? Something like feature wise modular architecture.

If I have a constructor with default values how can I make it so dagger doesn't try and inject those fields?

Hi. I wanted to implement dynamic features with instant support in my app. It is almost working except di with dagger. in my app module i do not have access to my activity in the feature module. so i can not do the following in my dagger FragmentsModules.kt

@ContributesAndroidInjector(modules = [FooFragmentModule::class])
abstract fun bindFooFragment(): FooFragment -> FooFragment can not be accessed

Does someone have an solution for this issue?

kapt {

    arguments {
        arg('dagger.gradle.incremental')
        arg('dagger.formatGeneratedSource', 'disabled')
        arg('dagger.fastInit', 'enabled')
    }
}

Should I place it in all gradle modules that uses dagger ?