Actually there is no magic. Custom scope annotations are just annotations. They can have any name. First function of scopes is a way to tell Dagger compiler which scopes are allowed within scoped component. That’s why using @ActivityScope dependency in non-@ActivityScope component will fire a compilation error. In fact components can declare many scopes (e.g. … Read more
I got this same error because I forgot to expose the objects provided by the modules in the parent component to the other components that are depend on it. Parent component example: @Singleton @Component(modules = {AppModule.class}) public interface AppComponent { AppPref exposeAppPref(); /* my issue was caused by forgot this line, the method name doesn’t … Read more
The error just states that dagger doesn’t have a way to provide said dependency. You will have to add it to your component in some way—and since it is a Fragment—you will have to use a @Module. I am assuming that your AppComponent is created by your Application on start. Your AppComponent has a lifecycle … Read more
I encountered the same situation. One way to ease a bit the injection from a common component in all Activities is the following: 1) Extend the Application class to be able to create the common component and keep a reference to it. public class ApplicationDagger extends Application { private ApplicationComponent component; @Override public void onCreate(){ … Read more
You need to implement your own ViewModelProvider.Factory. There is an example app created by Google demonstrating how to connect Dagger 2 with ViewModels. LINK. You need those 5 things: In ViewModel: @Inject public UserViewModel(UserRepository userRepository, RepoRepository repoRepository) { Define annotation: @Documented @Target({ElementType.METHOD}) @Retention(RetentionPolicy.RUNTIME) @MapKey @interface ViewModelKey { Class<? extends ViewModel> value(); } In ViewModelModule: @Module … Read more
You should put @Singletonto CComponent class declaration. @Singleton @Component(modules = CCModule.class) public interface CComponent { XXX getXXX(); } Explanation is in error message: CComponent is unscoped, @Singleton is a scope. Dagger 2 does not allow unscoped components to use modules with scoped bindings. However, now you will get the following error: AComponent (unscoped) cannot depend … Read more
I’ve just published sample app based on Gradle which integrates Dagger2, retrolambda, butterknife and lombok. You can find it here: https://github.com/mgrzechocinski/dagger2-example. Hope it would help 🙂
@Module public class MainActivityModule { private final Context context; public MainActivityModule (Context context) { this.context = context; } @Provides //scope is not necessary for parameters stored within the module public Context context() { return context; } } @Component(modules={MainActivityModule.class}) @Singleton public interface MainActivityComponent { Context context(); void inject(MainActivity mainActivity); } And then MainActivityComponent mainActivityComponent = DaggerMainActivityComponent.builder() … Read more
This is currently impossible with Dagger 2 (as of v2.0.0) without some workarounds. You can read about it here. More about possible workarounds: How do you override a module/dependency in a unit test with Dagger 2.0? Creating test dependencies when using Dagger2
I just hit this problem this morning. Do you have anything in your build.gradle that adds arguments to the annotationProcessOptions? For example: android { … defaultConfig { … javaCompileOptions { annotationProcessorOptions { arguments = [“room.schemaLocation”: “$projectDir/schemas”.toString()] } } } } If so, try changing from “arguments =” to “arguments +=”, as just using equals overwrites … Read more