Trying to debug dagger modules in a multimodule project. Let say,

app

gradle module depends on

feature

gradle module. When I define my

featureModule

in the

feature

, it fails to generate provide methods, but it works if I move it to the

app

.

I'm stuck with multi-module setup (

app

gradle module depends on

feature

library module). The general advice that I often see: if you don't want to get lost in dagger — don't bring Components to the library modules. It's easier if you just connect all your dagger modules from libraries in the final

app

module under one Component. That works, up to a point. Let say you need to do some manual injection in one of the libraries. But Component is in the

app

, so you don't have a direct reference. What are my options here?

Hi, I'm trying to import and use an aar(which contains Operations.kt) into a project. The aar uses Dagger2 for its dependencies. When i try to inject it in the project i get the following error. Any help would be highly appreciated

e: error: compiler message file broken: key=compiler.err.Processor: org.jetbrains.kotlin.kapt3.base.ProcessorWrapper@16547060 arguments={0}, {1}, {2}, {3}, {4}, {5}, {6}, {7}
e: error: cannot access Operations
  class file for com.Operations not found
  Consult the following stack trace for details.
  com.sun.tools.javac.code.Symbol$CompletionFailure: class file for com.Operations not found
:app:kaptDebugKotlin FAILED

Is it possible to provide generics types using

@IntoSet

? Like...

@IntoSet fun provideFooBar(): Foo<Bar> ...

and collect it using something like

val mySet: Set<@JvmSuppressWildcards Foo<Bar>>

?

Kapt doesn't generate dagger code in androidTest folder:

// build.gradle.kts
plugins {
    id("kotlin-kapt")
}

dependencies {
    // ...
    kapt(Libs.DAGGER_PROCESSOR) // this works fine
    kaptAndroidTest(Libs.DAGGER_PROCESSOR) // this doesn't work
}


class Test { 

@Module
class DummyModule

@Component(modules = [DummyModule::class])
interface DummyComponent {

}
}

any recommended ways about eagerly creating a dagger provided object? i probably don't want dagger to create it, but in my application i have an

@Inject

field that is never used just so my object gets created - this seems odd though

I'm beginner, can any one guide me to some good list of articles or tutorials for dagger?

Dagger + Kotlin - I’m getting

lateinit property has not been initialized error

. I believe I have done everything but not sure what’s missing!

This is what my code looks like

Why does generated classes in dagger does not count as a source set when it is only a kotlin module? On Android modules makes the generated directory as a sourceset by default

can anyone recommend a resource for getting started with dagger in kotlin (NOT with android, I’m building a web server)?

Hey all. We're starting to land some Kotlin-specific changes into Dagger! Two have already landed which will be in the next release: - Understand qualifier annotations on properties without requiring a use-site target (i.e.,

@Whatever

instead of

@field:Whatever

) - Understand

@Module

on

object

does not require a module instance. We have a few more in the pipeline, but if you have any ideas of small ergonomic improvements like this please file an issue on GitHub.

What is the recommended way of having a DebugComponent that extends MainComponent with some extra modules in debug? Thank you.

@JvmStatic @Provides @Singletonn fun providesHandler( ): SomeHandler = HandlerObject.init() This is the provider, i have inside the some module and that module is sits in the application component and it's singleton. I know that dagger generates all the module providers classes at compile time, as gets the instance dependency through the

get()

overriden method in the class. As all classes required for the DI graph are created at compile time. I was wondering when the actual creation of the object happens, when

get()

is actually called. Does it gets called and object is created when it's requested through

@inject

or happens at compile time and just returns when

@inject

gets called.

why no thermosiphon example? :troll:

Is it ok to use dagger in a library ? I haven't seen much example of it, however, there is a little section about it in Android docs.

You just have to shade it

How would I use dagger-reflect with a pure kotlin module? For the android modules I have set a

Dev

build type where I use dagger reflect and the

Debug

and

Release

build types use the regular dagger.

For a 101 cheatsheet of what code Dagger generates for you, check out this tweet: https://twitter.com/manuelvicnt/status/1207337679144259590

Can one inject functions using Dagger? I replaced an injectable class that was the command pattern with a function. As a class in the command pattern, the app builds. As the function, I get an error at point of injection

[Dagger/MissingBinding]

fun AddUseCase(x: Int): Reader<ReturnValType> = MyReader { ctx -> /* ... */ }

versus

class AddUseCase(ctx: MyContext) {
  fun invoke(x: Int): ReturnValType { /* ... */ }
}

you can always have unscoped providers

Hi guys. Recently I started working on new project and I wanted to start with mudularization right away. So far so good, however, I had a hard time implementing Dagger. Here is the thing. I have :app, :onboarding, :core as features, where :app depends on :onboarding and :*core*. :onboarding depends only on :core. :core doesn’t have any dependency. Regarding Dagger I have the following implementation.

@Module
class CoreModule {

    @Provides
    @AppScope
    fun provideLogger(): Logger {
        ...
    }

    @Provides
    @AppScope
    fun provideApiService(serviceHolder: ServiceHolder, OkHttpClientBuilder: OkHttpClientBuilder): APIService {
        ...
    }
}

@Component(
    modules = [
        AndroidSupportInjectionModule::class,
        CoreModule::class,
        MainActivityModule::class
    ]
)
@AppScope
interface AppComponent: AndroidInjector<MainApplication> {
    @Component.Factory
    interface Factory {
        fun create(@BindsInstance applicationContext: Context): AppComponent
    }
}

@Module
abstract class MainActivityModule {
    @ContributesAndroidInjector(modules = [OnBoardingModule::class])
    @ActivityScope
    abstract fun mainActivity(): MainActivity
}

@Module
abstract class OnBoardingModule {
    @ContributesAndroidInjector(modules = [SignInModule::class])
    abstract fun signInFragment(): SignInFragment
}

Am I breaking rules doing it like this?

Hey everyone, A quick question regarding ViewModel injection using dagger. So as per my understanding we have generic factory class that Implements ViewProvder.factory interface and is responsible for creating ViewModel instance when demanded from Activity/Fragment. And whatever dependencies required by that ViewModel is fulfilled by dagger itself. But what if there is a dependency say Bundle that I would like to pass to my ViewModel during it's construction. So is that possible by doing some tweaks within custom ViewModelFactory.

In case anyone is bored, I'm posting a question on 😒tackoverflow: about dagger [1], I'm missing something but I'm not able to find it.. [1] : https://stackoverflow.com/questions/60627262/lateinit-property-androidinjector-has-not-been-initialized-dagger-2

Recently working on a project and followed modularization with clean architecture. db-module -> all db related stuff and dagger provider, the class with @Module annotated api-module -> all api related i/o's and dagger provider domain-module-> dependent on above 2 using

impl

not

api

as i dont want to trigger app-module build if any change in above to modules. And it has use cases and Dagger @Module class with above @Modules added (data and api) Something like this

@Module(includes = [ApiModule::class, DatabaseModule::class])
object AppModule

app-module -> the ui layer, dependent on domain module using

impl

not api, and this module has Dagger components. Problem starts when dagger kicks in, whe dagger builds the graph it generated all the factories in the generated folder for providers in the sepecific modules like for ApiModule in its own and DatabaseModule in it's own and they are only exposed in domain layer and domain layer in app layer by impl. After compilation dagger throws AppComponent not found. The issue i found was it was not able to reach the generated factor classes from app-layer as app-layer is dependent on domain and domain on data and api-layer using

impl

not

api

and changin to

api

fixed by issue. But, i dont want to go this way, because if any changes in the outer layers (data and api) the build will also be trigerred for app-layer if exposed by api. I am thinking of keeping the all providers classes in the domain-layer. I think it will work. Am I breaking any rules or there is a better way to do it.

I've read a lot that you can do the same thing that AAC ViewModels give you if you just use Dagger. So you don't need VMs! No one ever seems to give an example of how this works even though I would assume there's only really 1 technique to get it done? I feel like I understand the Activity lifecycle fairly well, but I don't understand how Dagger would know how to scope something like my MessagingActivity across config changes. To go even further, maybe your Activity is open in split screen, and then you have another app that shares into your app in the other split screen. Essentially giving you two messaging activities. At this point, I would assume that you would have two distinct Scopes from dagger since you have two distinct instances of your MessagingActivity. How would I tell dagger to scope to a single instance of an activity where it will also know to "stay alive" and "outlive" the activity during config change? That's the big benefit of a AAC VM and I don't know where to start.

I updated from dagger 2.21 to dagger 2.27 and now I see errors when compiling

error: Dagger does not support injection into Kotlin objects

I'm admittedly someone still very new to dagger and so I'm not sure if I'm violating some overarching DI rules with trying to inject my moshi instance into my "util object". Can someone point me in the right direction of a solution? I suppose I can write extension methods instead of having this java util that was converted to a kotlin object?

Has anyone figured out a solution for the

@JvmSuppressWildCard

problem when injecting generic classes through Dagger? It is becoming too ugly for me 😞

internal class SalesSectionReader @Inject constructor(
    private val sectionsLocalDataSource: SectionsDataSource,
    private val saleEntityToSaleSectionSaleMapper: Mapper<@JvmSuppressWildcards SaleEntity, @JvmSuppressWildcards SaleSection.Sale>,
    private val blogEntityToBlogSectionMapper: Mapper<@JvmSuppressWildcards BlogEntity, @JvmSuppressWildcards SaleSection.Blog>,
    private val tagEntityToSaleSectionTagMapper: Mapper<@JvmSuppressWildcards TagEntity, @JvmSuppressWildcards SaleSection.Tag>
) : StoreListReader<AllSectionsKey, SaleSection>

I'm learning Dagger and the biggest motivator behind learning it is to test deterministic responses from my backend. I'm following the typical Android arch guide, so yeah (I know I'm a bad person for using AAC VMs) Activity + Fragments + AAC VMs and a Repository. My "issue" is that it seems like I could just use Dagger to swap out Repository and FakeRepository and that would work... but it looks like I could also just use MockWebServer so I could mock the entire server interaction, as well as failures, etc etc. Does anyone have advice on to what route to go? My thinking that having a Repository and FakeRepository isn't actually all that helpful anymore and that MockWebServer from okhttp would actually be a ton better. In that case though... I don't think I would need Dagger at all? I'd love to be able to run my app in mock server mode though. Any advice would be appreciated. TLDR Which layer is the right one to fake stuff? VMs? Repository/FakeRepository? or real server and MockWebServer? Leaning MockWebServer