Question regarding the usage of

@Singleton

and

@Inject

inside the code instead of

Module

? I have a personal opinion of creating

Modules

and defining all my dependencies there instead of marking classes with the above annotations? Reason being: 1. It help me understand the dependencies and configurations from a single file i.e

Module

. 2. It avoid mixing code with configuration(annotations). What are your opinion on this? I don’t prefer the following code:

@Module
class BookingDatabaseModule {

    @Provides
    fun provideBookingDao(database: BookingDatabase) = database.bookingDao()
}

Following is my preferred way of doing it:

@Module
class BookingDatabaseModule {

    @Provides
    @Singleton
    fun provideDatabase(context: Context) = BookingDatabase.newInstance(context)
    
    @Provides
    fun provideBookingDao(database: BookingDatabase) = database.bookingDao()
}

What are your opinions?

Is it possible to remove the ambiguity to provide a ListProcessor just by providing two distinct lists?

Since Dagger 2 supports incremental kapt, is there any benefit to using dagger-reflect?

This message was deleted.

I need two global OkHttp instances in my app. I'm a dagger noob, but I inherited a project that already has the single okhttp instance, but encountering problems when I try to add a second one. What's the defacto way to have two objects of the same type in the same scope?

Hello! I'm facing this error whenever I want to create UI tests with Espresso using Dagger

java.lang.RuntimeException: android.app.Application does not implement dagger.android.HasAndroidInjector

Any idea, why? It only happens with UI tests, the app runs and everything is injected correctly.

Does anyone have a new about changes related to Dagger-Android?

Is it possible to @binds two different interfaces to the same instance and inject both to the same class?

I've posted a question some days ago and I'm still looking for a proper solution, the thing is that I'm trying to create a TestAppComponent because when creating UI tests and doing the call it's not using the mockWebServer is doing the real call, any help is appreciate: https://stackoverflow.com/questions/61539234/dagger2-not-injecting-instance-on-test

I appreciate help on this ^

Can anyone vouch for speeding up dagger via this snippet in gradle? The snippet seems to: Enable fastInit Disable formatGeneratedSource Enable incremental compilation (I'm using dagger 2.21 so incap isn't enabled automatically) https://github.com/google/dagger/issues/1120#issuecomment-493512366

Reposting this question from March that didn't get any replies (except from Jake). Don't want to keep bothering one person. Can anyone chime in? I'm still learning dagger (did a big deep dive this past week) and I have a better grasp on it and components and subcomponents, etc, but I still don't understand the comments from people that say "If you use Dagger, you don't need AAC ViewModels". I would love to kill off AAC VM completely because I think the factory you need to create in order to pass in an argument is overkill and it seems like a properly scoped component would just be simpler in this case. (note: I also understand that this "hilt" thing is coming out soon, but I still would find this answer beneficial, even from a curiosity point of view. I'm trying to prevent someone from answering "Just wait till June 3rd")

It appears 2.28 with an alpha for hilt was released but no changelog 👀

I have a really basic dagger setup in my android app. I basically just followed the dagger guide/tutorial and now I went to add dagger-reflect by Jake Wharton, but now my basic setup won't compile because the

builder()

method isn't available on MyAppComponent. Anyone have any ideas? The readme doesn't say that I need to change anything. Opened an issue here as well https://github.com/JakeWharton/dagger-reflect/issues/191 EDIT 1: I did find this issue (https://github.com/JakeWharton/dagger-reflect/issues/145) which seems similar, but it doesn't really have a solution? The last semi-helpful response there is to use

@Component.Factory

but I'm not sure how that helps. Android Dagger guide doesn't talk about that at all, which just makes it weird that dagger reflect doesn't work with a "typical"/basic dagger setup. EDIT 2: Also found this https://github.com/JakeWharton/dagger-reflect/issues/4 where Jake says "in general you should refactor to 

@BindsInstance

 and stateless modules." Maybe that's my solution? But how do I move my simple setup to "BindsInstance and stateless modules". That's going wayy over my head. In the same comment JW seems to mention that Builder() should also already work? Sorry for being a dagger noob here

Is there a way to make a property in an object to be injected from dagger as a lateinit property?

I have my appComponent that takes in an argument when I call

.create()

which is the url that my networkModule needs. java

public interface AppComponent {
    @Component.Factory
    interface Factory {
        AppComponent create(@BindsInstance @Named("url") String url);
    }
}

This is my networkModule. kotlin

@Module
class NetworkModule @Inject constructor(@Named("url") val url: String) {...}

I get this dagger error:

error: @Component.Factory method is missing parameters for required modules or components: [com.myapp.internal.NetworkModule]

Ideas? Looks like my BindsInstance should satisfy my networkModule.

Wrt Hilt: how does the

@InstallIn

work inside gradle submodules? Would you need a sub component per module? I couldn’t find anything in the official doc regarding this.

Is there a way to access the Fragment args when using Hilt? I tried something like this:

@InstallIn(FragmentComponent::class)
@Module
object MyFragmentModule {

    @Provides
    @FragmentScope
    internal fun providesViewModel(
        fragment: MyFragment,
        anotherDependency: Dependency
    ) = MyViewModel(
        fragment.requireArguments().getString("argument"),
        anotherDependency
    )
}

@AndroidEntryPoint
class MyFragment : Fragment() {
    // ...
}

However, this does not appear to work as it shows the following error when building:

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

Am I doing something wrong? This worked fine without Hilt when using Dagger Android.

Hi! First thing, amazing work with Hilt 😉 Just two questions: • There are some situations in which you need to manually recreate the application dependencies graph and then inject the application again. Is there a way to do it with Hilt? ApplicationComponent is managed by the framework so it seems not. I mean, there’s a way to disable the automatic component creation and app injection in the @HiltAndroidApp and do it manually? • Let’s say I want to maintain the old dagger android way for the activities that I already have. How do I have to deal with AndroidSupportInjectionModule? It’s autogenerated so no way to add @InstallIn(ApplicationComponent::class) Side note: https://codelabs.developers.google.com/codelabs/android-dagger-to-hilt/index.html?index=..%2F..index#4 seems outdated

Hi guys, I was wondering how to add

FragmentFactory

with Hilt. It seems that

Hilt

works almost the same way as

dagger-android

(please correct me if im wrong) and so, using

FragmentFactory

is really hard. Can anyone guide me please.

What exactly is the difference between

ActivityRetainedComponent

vs

ActivityComponent

??

I'm wondering if anyone has started facing

bindsMethod does not represent a type element

issues when started migrating to Hilt? It never popped up before 😕

Caused by: java.lang.IllegalArgumentException: bindsDateFormatter(com.example.date.SalesDateFormatter) does not represent a type element
        at dagger.shaded.auto.common.MoreElements$CastingElementVisitor.defaultAction(MoreElements.java:395)
        at dagger.shaded.auto.common.MoreElements$CastingElementVisitor.defaultAction(MoreElements.java:386)
        at com.sun.tools.javac.code.Symbol$MethodSymbol.accept(Symbol.java:1644)
        at dagger.shaded.auto.common.MoreElements.asType(MoreElements.java:128)
        at dagger.internal.codegen.validation.TypeCheckingProcessingStep.lambda$process$0(TypeCheckingProcessingStep.java:51)
        at com.google.common.collect.RegularImmutableMap.forEach(RegularImmutableMap.java:185)
        at dagger.internal.codegen.validation.TypeCheckingProcessingStep.process(TypeCheckingProcessingStep.java:48)
        at dagger.internal.codegen.ModuleProcessingStep.process(ModuleProcessingStep.java:104)
        at dagger.internal.codegen.ModuleProcessingStep.process(ModuleProcessingStep.java:59)

And it is just bound using a simple

@Binds

@Binds
    abstract fun bindsDateFormatter(it: SalesDateFormatter): DateFormatter

hi guys! i'm trying to migrate from Koin to Hilt what is the best way to inject fields into the BaseViewModel? i have such structure: MyViewModel extends BaseViewModel extends ViewModel is it possible to inject directly into the fields/properties of BaseViewModel?

Example of how to make AssistedInject work with Hilt at the moment https://twitter.com/manuelvicnt/status/1273699171078475780

One of the downsides of a single binding key space is that it can be extra work to place restrictions on code usage (e.g. if one feature shouldn't use bindings from another feature). For this we generally recommend using qualifier annotations that are restricted visibility or using an SPI plugin to enforce separation of code.

I can’t find any info about this SPI plugin. Can anyone point me where I can read about this?

I have a module containing

@Provides
    @Singleton
    fun providesMessageCenter(): MessageCenter = MessageCenter()

for me, this seems to be quite unnecessary and I guess I could annotate the

MessageCenter

class directly instead to get it into the graph. Whats the best way of doing this (or is the best way to keep it as it is?)

Hello people, in hilt is there a way to differentiate modules to be installed in specific entrypoints only?

is it possible to inject ViewModel into another ViewModel with Hilt?

I am trying to inject singleton Media Player instance to use in my 3 View Pager fragments. The injection seem works, I can use instance of Media Player in different fragments, but it is not singleton. The key thing is when I play music in a fragment, switch to another view pager fragment -> play music there -> it should stop the current music and play the one I choose.

@Provides
    @Singleton
    fun provideMediaPlayer(): MediaPlayer {
        return MediaPlayer.create(applicationContext, R.raw.sample)
    }

//AppComponent
@Component(modules = [AppModule::class])
@Singleton
interface AppComponent {
    fun inject(activity: MainMusicActivity)

    fun inject(fragment: FeaturedFragment)

    fun inject(fragment: MyMusicFragment)
}

This is inject in fragment, I try both @Inject and @Inject set

@Inject
    lateinit var mediaPlayer: MediaPlayer

My question is am I using dagger correctly? Or is there any better way for getting singleton instance of media player with these view pager fragments