Dagger2 and objectbox are used simultaneously, indicating that DaggerActivity cannot be found

[mclmdream]

buildscript {
dependencies {
classpath "io.objectbox:objectbox-gradle-plugin:4.0.2"
}
}

plugins {
// id 'com.android.application' version '7.1.2' apply false
id 'com.android.application' version '8.0.0' apply false
id 'org.jetbrains.kotlin.android' version '1.9.0' apply false
}

plugins {
id 'com.android.application'
id 'org.jetbrains.kotlin.android'
id 'io.objectbox'
}

[greenrobot-team]

Thanks for reporting. Can you please share a more complete build script that also shows how Dagger is used? Is there any relevant log output when building the app? Otherwise, this is rather hard for me to reproduce.

Note: I labeled this issue with "more info required" so it will auto-close in a few days if there are no follow-up comments.

[mclmdream]

'com.google.dagger:dagger:2.51.1',
  'com.google.dagger:dagger-compiler:2.51.1',

@ActivityScope
@Component(dependencies = DnetComponent.class,
        modules = {ActivityModule.class,
                DBaseActivityModule.class,

        })
public interface ActivityComponent {
    Activity getBaseActivity();
}



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


@Module
public class ActivityModule {
    private Activity mActivity;

    public ActivityModule(Activity mActivity) {
        this.mActivity = mActivity;
    }

    @Provides
    @ActivityScope
    public BaseActivity provideActivity() {
        return mActivity;
    }

}

DaggerActivityComponent.builder()， Unable to find DaggerActivityComponent，thanks

[greenrobot-team]

Tried this with our Android app Java example and it works just fine.

It looks like you are using Kotlin though. IIRC in that case make sure that all Dagger related classes are written in Kotlin as well and then use kapt instead of annotationProcessor. But that's not related to ObjectBox.

If you still think this is related to ObjectBox, please share a full example that I can use to verify.

[github-actions]

Without additional information, we are unfortunately not sure how to resolve this issue. Therefore this issue has been automatically closed. Feel free to comment with additional details and we can re-open this issue.