Android-Dagger2问题：无法从Application组件获取依赖到Activity作用域

Hey there! I’ve run into this exact Dagger 2 component dependency issue plenty of times when working on Android apps. Let’s walk through the most common causes of those compilation errors and how to fix them step by step.

1. You Forgot to Expose Dependencies from ApplicationComponent to Child Components #

Dagger doesn’t automatically let child components access all the dependencies from the parent component. You have to explicitly define methods in your ApplicationComponent interface that return the instances you want to share with ActivityComponent.

For example, if your Activity needs an OkHttpClient or AppDatabase that’s provided in ApplicationModule, your ApplicationComponent must expose them:

@Singleton
@Component(modules = ApplicationModule.class)
public interface ApplicationComponent {
    // Expose these dependencies to child components
    OkHttpClient provideOkHttpClient();
    MyAppDatabase provideAppDatabase();
}

If you skip this step, Dagger will throw a compilation error saying it can’t find a provider for those dependencies in ActivityComponent.

2. Scope Conflicts Between Components #

When using dependencies = ApplicationComponent.class for your ActivityComponent, you cannot use the same scope as the parent component. Since ApplicationComponent uses @Singleton, your ActivityComponent needs its own custom scope (like @ActivityScope).

First, define your Activity scope:

@Scope
@Retention(RetentionPolicy.RUNTIME)
public @interface ActivityScope {}

Then apply it to your ActivityComponent:

@ActivityScope
@Component(dependencies = ApplicationComponent.class, modules = ActivityModule.class)
public interface ActivityComponent {
    void inject(MainActivity activity);
}

Using @Singleton for both components will cause Dagger to throw a compilation error, as it doesn’t allow multiple components to share the same scope via dependency linking.

3. You’re Not Passing the ApplicationComponent Instance When Building ActivityComponent #

Another common mistake is forgetting to pass the ApplicationComponent instance when creating your ActivityComponent. Dagger requires you to explicitly provide the parent component via the builder.

In your Activity, make sure you do this:

// Get the ApplicationComponent from your Application class
MyApplication myApp = (MyApplication) getApplicationContext();
ApplicationComponent appComponent = myApp.getApplicationComponent();

// Build ActivityComponent with the parent component
ActivityComponent activityComponent = DaggerActivityComponent.builder()
        .applicationComponent(appComponent)
        .build();

activityComponent.inject(this);

If you call DaggerActivityComponent.create() instead, Dagger will throw an error because it can’t resolve the required ApplicationComponent dependency.

4. Check Module Visibility and Provider Methods #

• Ensure all your @Module classes are public, and their @Provides methods are also public (or package-private if the component is in the same package).
• If your Module is an inner class inside your Application/Activity, make it a static inner class—Dagger can’t instantiate non-static inner classes without an instance of the outer class.
• Don’t duplicate provider methods for dependencies that are already available from the parent component; let Dagger resolve them via the exposed methods in ApplicationComponent.

If you fix these four areas, your Dagger 2 setup should compile successfully. Start with checking the exposed dependencies first—this is the most frequent culprit!

内容的提问来源于stack exchange，提问作者Mohammad Elsayed