Android dagger 2.11 : MainModule must be set

I am working in the new Android dagger 2.11 implemtnation; I am getting this error in runtime :

MainModule must be set.

I have one Activity with it’s presenter injected in mainModule + multiple fragments( bottom view tabs)

I added ArticlesFragment as an example.

MainModule.java

@Module public abstract class MainModule {
 @FragmentScoped 
@ContributesAndroidInjector(modules = ArticlesFragment.class) abstract ArticlesFragment articlesFragment(); 

@Provides 
@ActivityScoped static String provideTaskId(MainActivity activity) {     
return activity.getIntent().getStringExtra(""); }  

@ActivityScoped 
@Provides 
public PresenterFactory<MainContract.Presenter> providePresenterFactory() { return MainPresenter::new; }

ActivityBindingModule.java : addded to the appComponent

@ActivityScoped @ContributesAndroidInjector(modules = MainModule.class)
  abstract MainActivity mainActivity();

[liminal]

@alouanemed it’ll work if you just make it static. having an instance method means you have to have an instance of the module. If the provider-method is static then dagger can use it without requiring an instance of the module. So just changing it to @ActivityScoped @Provides public static PresenterFactory<MainContract.Presenter> providePresenterFactory() { return MainPresenter::new; }

should work fine

[vestrel00]

Good to see this issue is resolved. This made me realize that there were only 2 places (1, 2) where I demonstrated how to use @Provides instead of @Binds in abstract module classes. Furthermore, I didn’t at all discuss this in my article, which I’ll now update with these discussions.

Thanks for bringing this up @alouanemed. Good eyes there @liminal!

UPDATE:

Someone asked me the same question. I answered the same issue with more in-depth explanations here: link