dagger

Build error after update from Kotling 1.3.21 to 1.3.30: AppComponent.java:16: error: [Dagger/MissingBinding] java.util.Map<java.lang.Class<? extends androidx.lifecycle.ViewModel>, javax.inject.Provider<androidx.lifecycle.ViewModel>> cannot be provided without an @Provides-annotated method. Reproduced on two different projects with similar dependencies on Kotlin, Dagger and Architecture components. I suspect it somehow related to the recent kapt updates in kotlin 1.3.30: https://blog.jetbrains.com/kotlin/2019/04/kotlin-1-3-30-released/ Tried to disable/enable the kapt options from the article,

I have a simple Android activity with a single dependency. I inject the dependency into the activity's onCreate like this: Dagger_HelloComponent.builder() .helloModule(new HelloModule(this)) .build() .initialize(this); In my ActivityUnitTestCase I want to override the dependency with a Mockito mock. I assume I need to use a test-specific module which provides the mock, but I can't figure out how to add this module to the object graph. In Dagger 1.x this is apparently done with something like this : @Before public void setUp() { ObjectGraph.create(new TestModule()).inject(this); } What's the

Dagger 1's plus() method is something I used quite often in previous applications, so I understand situations where you might want to have a subcomponent with full access to the parent graphs bindings. In what situation would it be beneficial to use a component dependency instead of a subcomponent dependency and why? Praveer Gupta Component dependencies - Use this when you want to keep two components independent. Subcomponents - Use this when you want to keep two components coupled. I will use the below example to explain Component dependencies and Subcomponents . Some points worth noticing