HasActivityInjector can not be resolved in android dagger 2

Question

I was trying to implement HasActivityInjector in my android application but it's showing me HasActivityInjector cann't be resolved. Below dependencies and plugin I have used in my project-

apply plugin: 'kotlin-kapt'

and

implementation 'com.google.dagger:dagger:2.16'
kapt 'com.google.dagger:dagger-compiler:2.16'

Here is the code I am trying -

class RanoBoilerplateApplication : Application(), HasActivityInjector{
    @Inject
    lateinit var activityDispatchingAndroidInjector:
            DispatchingAndroidInjector<Activity>

    override fun onCreate() {
        super.onCreate()

        DaggerAppComponent.builder()
                .application(this)
                .build()
                .inject(this)
    }

    override fun activityInjector(): AndroidInjector<Activity> =
            activityDispatchingAndroidInjector
}

I don't know what other dependencies I must have to include to work that, help me if anyone have done this before.

Find the latest Dagger 2 version here.

Happy coding :-)

@UmangBurman, I am already using the latest one dependency only. — Bajrang Hudda, Oct 23 '18 at 12:39
@rekire, Of course I am Importing the mentioned class, by the way I am using Android stdio, and it's cool enough to import it self or easy by Alt+Enter — Bajrang Hudda, Oct 23 '18 at 12:40

mbonnin · Answer 1 · 2019-08-21T10:00:28.927

89

In case anyone comes here after updating to 2.24, this was removed: https://github.com/google/dagger/commit/3bd8f707cb28fd0c5f3abb4f87658566f8b52c10.

You can use HasAndroidInjector instead.

edited Aug 21 '19 at 10:00

answered Aug 21 '19 at 09:45

mbonnin

6,893
3
39
55

As it is of any type. So, we can use the same to inject Worker as well. is it? – Usman Rana Jan 30 '20 at 05:34
Lol, or when you tried using `HasAndroidInjector` below `2.24` ... D: – A1m Mar 24 '20 at 02:19

Subhan Ali · Answer 2 · 2019-11-26T06:05:42.100

It's pretty late to answer but it might be useful for someone who is new to dagger world!

Its been replaced with HasAndroidInjector in order to avoid boilerplate of implementing multiple Dagger Interfaces like HasActivityInjector, HasServiceInjector etc, in your Application class. Now you only need to implement HasAndroidInjector like below:

class DaggerExampleApplication : Application(), HasAndroidInjector{

       @Inject lateinit var androidInjector : DispatchingAndroidInjector<Any>

       override fun androidInjector(): AndroidInjector<Any> = androidInjector
       override fun onCreate() {
         super.onCreate()
         //Your code
       }        
}

I'm glad, you found it useful. :) – Subhan Ali Oct 05 '20 at 08:42 — Subhan Ali, Oct 05 '20 at 08:42

score 13 · Answer 3 · answered Feb 03 '20 at 19:19

In addition to @mbonnin and @Subhan's answer, starting version 2.24, Has{Activity,Fragment,Service,ContentProvider,BroadcastReceiver} are removed. If you still want to support this old implementation, use version 2.23 which supports both HasAndroidInjector and Has{Activity,Fragment,Service,ContentProvider,BroadcastReceiver}.

here's what it should look like on version 2.24

Application

class ExampleApp: Application(), HasAndroidInjector {

    @Inject
    lateinit var androidInjector: DispatchingAndroidInjector<Any>

    override fun androidInjector(): AndroidInjector<Any> = androidInjector

/..../

Activity

class ExampleActivity: AppCompatActivity(), HasAndroidInjector {

    @Inject
    lateinit var androidInjector: DispatchingAndroidInjector<Any>

    override fun androidInjector(): AndroidInjector<Any> = androidInjector

/..../

Fragment

class MoreFragment: Fragment(), HasAndroidInjector {

    @Inject
    lateinit var androidInjector: DispatchingAndroidInjector<Any>

    override fun androidInjector(): AndroidInjector<Any> = androidInjector

/..../

Demigod · Answer 4 · 2018-10-23T13:42:57.997

6

My dependencies looks like this:

//Dagger
implementation "com.google.dagger:dagger:${libs.dagger}"
implementation "com.google.dagger:dagger-android:${libs.dagger}"
implementation "com.google.dagger:dagger-android-support:${libs.dagger}"
kapt "com.google.dagger:dagger-compiler:${libs.dagger}"
kapt "com.google.dagger:dagger-android-processor:${libs.dagger}"

The support one is needed if you're using appcompat. And the ${libs.dagger} refers to the needed dagger version (e.g. 2.16). Read more about dependencies here.

edited Oct 23 '18 at 13:42

answered Oct 23 '18 at 12:22

Demigod

5,073
3
31
49

could you briefly explain which dependency for what? – Bajrang Hudda Oct 23 '18 at 12:45
@BajrangHudda, briefly - the 1st and 4th is min required for dagger to work (dagger classes + annotation processor), the 2nd and 5th are the one needed to work with `Android` (and the 3rd one if you have appcompat). – Demigod Oct 23 '18 at 13:45

score 2 · Answer 5 · answered Oct 23 '18 at 13:07

2

HasActivityInjector was introduced in new dagger android support module.Include following dependency in your build.gradle file.

kapt "com.google.dagger:dagger-android-processor:2.18"
implementation "com.google.dagger:dagger-android-support:2.18"

answered Oct 23 '18 at 13:07

Vipul

27,808
7
60
75

score 1 · Answer 6 · answered May 25 '21 at 12:48

1

Could have been late late answer but new Dagger2 dependencies carries DaggerAppCompatActivity and DaggerFragment classes which are useful for injecting activities and fragments by itself. So, we no longer need HasActivityInjector, autoInjection methods or something like them.

answered May 25 '21 at 12:48

Amrah Aziz

81
6

We still might depend on some our legacy project or external library which force us to extend their own ```Fragment``` and ```Activity``` classes. Interfaces bring more flexibility to this. – Joe Dow Dec 29 '22 at 14:03

HasActivityInjector can not be resolved in android dagger 2

6 Answers6

Linked