[Dagger/MissingBinding] LoginUI cannot be provided without an @Inject constructor or an @Provides-annotated method. This type supp

相关文章推荐

好帅的扁豆 · 关于我省传统文化与现代元素结合路径的研究报告· 10 月前 ·

帅气的柑橘 · 国家知识产权局工作通报面对疫情，复审和无效审 ...· 11 月前 ·

喝醉的便当 · 海外就医中介机构排名· 11 月前 ·

眉毛粗的滑板 · 故障存储段18792941725073428 ...· 1 年前 ·

不敢表白的紫菜 · 摄影工作室装修需要注意什么功能区块应该如何划 ...· 2 年前 ·

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement . We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account [Dagger/MissingBinding] LoginUI cannot be provided without an @Inject constructor or an @Provides-annotated method. This type supports members injection but cannot be implicitly provided. #2044 [Dagger/MissingBinding] LoginUI cannot be provided without an @Inject constructor or an @Provides-annotated method. This type supports members injection but cannot be implicitly provided. #2044 alanban opened this issue Aug 13, 2020 · 4 comments

Hi Everybody
i have issues when i Migrating project to AndroidX , and i add Kotlin in my project
when i use Kapt and run project i got this exception

[Dagger/MissingBinding] LoginUI cannot be provided without an @Inject constructor or an @Provides-annotated method. This type supports members injection but cannot be implicitly provided.

here is my code

MyApplicationComponent

@Component(modules = {AndroidInjectionModule.class, ActivityModule.class, FragmentModule.class, ......})
@AccountCore
@Singleton
public interface MyApplicationComponent extends AndroidInjector<App> {
    AccountComponent.Builder getAccountComponent();
    SprintComponent.Builder getSprintComponent();
    void inject(App app);
ActivityModule
@Module(includes = {AccountViewModule.class,.......})
public abstract class ActivityModule {
AccountViewModule
@Module(includes = {xxxx.class, xxx.class})
public abstract class AccountViewModule {
     @Binds
    abstract LoginPresenter provideLoginPresenter(LoginPresenterImpl presenter);
    @ContributesAndroidInjector()
    public abstract LoginUI provideLoginUI();
    @Binds
    public abstract AccountView.LoginView provideLoginView(LoginUI loginUI);
LoginUI
public class LoginUI extends DaggerActivity {
    @Inject
    LoginPresenter accountPresenter;
LoginPresenterImpl
public class LoginPresenterImpl extends AccountPresenter implements LoginPresenter {
    @Inject
    AccountClient accountClient;
    @Inject
    AccountView.LoginView loginView;
    @Inject
    AccountModel accountModel;
        buildToolsVersion = "29.0.2"
        supportVersion = "29.0.2"
        compileSdkVersion = 28
        minSdkVersion = 18
        targetSdkVersion = 28
        lifecycleVersion = "1.1.1"
        daggerVersion = "2.28.3"
        rxJavaVersion = "1.2.1"
        okHttpVertion = "3.9.1"
        retrofitVersion = "2.1.0"
        kotlin_version = "1.3.72"
        gradle_version = "3.1.4"
        glide_version = "4.11.0"
thanks in Advanced
          This seems like the dagger-android-processor is not running. Can you confirm that you have added the following dependency:
  kapt com.google.dagger:dagger-android-processor:<VERSION>
This seems like the dagger-android-processor is not running. Can you confirm that you have added the following dependency:
  kapt com.google.dagger:dagger-android-processor:<VERSION>
@bcorso Thank you for reply

I already added processor

here is my code
    implementation 'com.google.dagger:dagger:' + daggerVersion
    implementation 'com.google.dagger:dagger-android:' + daggerVersion
    implementation 'com.google.dagger:dagger-android-support:' + daggerVersion
    kapt 'com.google.dagger:dagger-android-processor:' + daggerVersion
    kapt 'com.google.dagger:dagger-compiler:' + daggerVersion
          It's difficult to say without having a real example to debug, but one issue I see is that the @Binds is in the same module as the ContributesAndroidInjector, as shown below.
@Module
public abstract class AccountViewModule {
  @ContributesAndroidInjector()
  abstract LoginUI provideLoginUI();
  @Binds abstract AccountView.LoginView provideLoginView(LoginUI loginUI);
However, I think these need to be in separate modules because the @ContributesAndroidInjector needs to be put into the application's component, whereas the @Binds needs to be put into the activity's component. For example:
// This should be installed into the Application's @Component.modules
@Module
abstract class LoginUiInjectorModule {
  @ContributesAndroidInjector(modules = LoginUiModule.class)
  abstract LoginUI provideLoginUI();
// This should be installed into the LoginUI @ContributesAndroidInjector.modules
@Module
abstract class LoginUiModule {
  @Binds abstract AccountView.LoginView provideLoginView(LoginUI loginUI);
It's difficult to say without having a real example to debug, but one issue I see is that the @Binds is in the same module as the ContributesAndroidInjector, as shown below.
@Module
public abstract class AccountViewModule {
  @ContributesAndroidInjector()
  abstract LoginUI provideLoginUI();
  @Binds abstract AccountView.LoginView provideLoginView(LoginUI loginUI);
However, I think these need to be in separate modules because the @ContributesAndroidInjector needs to be put into the application's component, whereas the @Binds needs to be put into the activity's component. For example:
// This should be installed into the Application's @Component.modules
@Module
abstract class LoginUiInjectorModule {
  @ContributesAndroidInjector(modules = LoginUiModule.class)
  abstract LoginUI provideLoginUI();
// This should be installed into the LoginUI @ContributesAndroidInjector.modules
@Module
abstract class LoginUiModule {
  @Binds abstract AccountView.LoginView provideLoginView(LoginUI loginUI);
Thank you very much @bcorso