Hey! In efforts to providing a single instance of

Retrofit

for my application, I'm using the

Singleton

scope in my network module which is then included in the

ApplicationComponent

with the same

Singleton

scope. But in order to do that I've to add network dependencies to my

app

module too. Is it possible to keep my retrofit instance singleton across application without adding network dependencies in my app module?

Hi everyone, just wanted to check what do you think, is Hilt safe for production?

Hey everyone, You can check out my project where I used dagger hilt with dynamic feature modules

Hi everyone, Let’s say I start an activity with some bundled data that I’d need way back in the repository. How can I provide that data using Hilt instead of passing it through several ${place_arch_pattern}-components? How do you solve problems like that?

Learning more about dagger and I want to sanity check how plausible this sounds. I really want to simplify my app with dependencies and components/scopes. I think I want to have 3 scopes defined. 1. Application scope 2. Logged In User scope 3. Logged Out User scope So in my head I'll have 3 components ApplicationComponent, LoggedInComponent, and LoggedOutComponent. How does that sound at a high level? I feel like it will solve 90% of my problems for me and it'll give me a chance to learn about scopes/components, provides/modules, and how to actually wire that up into my fragments/activities/all other classes.

Is there any alternatives ways to provides a

viewModelScope

? Moved to this issue instead with more details and examples: https://github.com/google/dagger/issues/2004

What is it called when my Component exposes some type via a field? Aka, instead of using field injection in Android, I can do X instead. I want to call them provision methods... but that sounds weird? Is that what people say when talking on a team? https://dagger.dev/api/latest/dagger/Component.html#provision-methods

How to provide arguments like this

Callback

in Fragment using HILT

class PostAdapter @Inject constructor(
    @ApplicationContext private val context: Context,
    private val callback: Callback //HOW THIS CAN BE PROVIDED FROM FRAGMENT
) : ListAdapter<Post, PostAdapter.Holder>(DIFF) {

  /.../

   interface Callback {
        fun onClick(post: Post)
    }

}

i mean how i can

@Inject PostAdapter

in any fragment ?

I'm about to try HILT for my project. But as soon as I try to add the gradle plugin (even adding the classpath to dependencies) I'm getting errors all over my gradle file. I'm using Kotlin-syntax for my build.gradle-files. Would that be a problem?

is it just me or is

@InstallIn

violating inversion of control? if not for the abstract concept of the monolithic component hierarchy creating a dependency inversion boundary it would be cyclic in nature 😕

Anyone here tried to benchmark build times after migrating to Hilt? I tried migrating a project, but the benchmarks show Hilt is significantly slower. I’m going to investigate if there’s just something wrong with my setup; and I’d love to hear your experiences if anyone can share 🙏

Working on some best practices documentation for my team. Poll Do you prefer: 1️⃣ field injection 2️⃣ provision methods (

@Provides

)

Hi, How can I implement dagger hilt in my module if my module is shipped as an aar library in the main project? Because I have to annotate my application class with @HiltApplication. How will this work for my library module?

Hi Guys, may I ask a question. I am using

Hilt

for Android DI. I am wondering whats the recommended approach of where to define the

Hilt

Modules. In a multi-module project, is it ok to define

Hilt

modules in each module? So for example I have a

UserModule (Android Submodule)

and with in it I define the

Hilt

Module. Or is it better to define all

Hilt

Modules inside the

app

Module itself?

interface Builder

class BuilderImpl @Inject(abstraction: Builder::class.java) constructor(): Builder

Hi guys, Looks I found some weird issue in Hilt. Try to create a sample activity with

@AndroidEntryPoint

in

case

package (

com.android.ui.case

or something). Result:

Failed Caused by: javassist.NotFoundException:

Are there any forbidden package names? (code without hilt annotation is working fine)

how to use Hilt with Dagger/Android for example AndroidInjector side by side

It is normal that a dependency in one module needs to also be added to the main module when using hilt? I have a class in a module which uses a library:

@AndroidEntryPoint
class MyFragment: Fragment(), SomeInterfaceFromALibrary {
    @Inject
    lateinit var someClass: SomeClass
    
    ....
}

Now whenenver I build my project it says "could not access SomeInterfaceFromALibrary" The only way I fixed it was to add the same dependency in the main module:

:app
...
dependencies {
    implementation "someLibrary:version"
}

:otherModule
...
dependencies {
    implementation "someLibrary:version"
}

Is this intended or am I doing something wrong?

thanks for the quick response. i tried it with optional but with hilt it throws a compilation error: java.util.Optional<androidx.fragment.app.Fragment> cannot be provided without an @Inject constructor or an @Provides-annotated method.

In Hilt is there a way to have a dependency scoped to

@ActivityRetainedScoped

but have a value injected to it from the

Activity

. I need the depedency to survive device rotation but the problem is it also needs a value taken from the `Activity`'s bundle. Any advise on how to work around this?

I have several test classes that are annotated by

HiltAndroidTest

and they have

UninstallModules

with the same set of modules to uninstall. If I add or remove an extra module to uninstall, I have to cascade the changes to the rest. Is there a way to avoid repeating myself with Hilt or do I need to file a feature request for that? What I tried and didn't work (inspired by Spring Boot TestComponent annotation)

@UninstallModules(SearchModule::class, SearchResultsModule::class, DestinationsSearchModule::class)
@HiltAndroidTest
internal class MonthsFragmentTest

Tried writing an annotation that combines them

@UninstallModules(
    SearchModule::class,
    SearchResultsModule::class,
    DestinationsSearchModule::class
)
@kotlin.annotation.Target
annotation class UninstallSearchProductionModules

and tried replacing them

@UninstallSearchProductionModules
@HiltAndroidTest
internal class MonthsFragmentTest

Finally wrote out my thoughts about what makes Dagger useful from a "beginners" perspective. https://medium.com/@ColtonIdle/dagger-2-a-beginners-journey-to-understanding-why-dagger-is-useful-accdc0b42b63

(Pretty sure the answer is no, but wanted to double-check https://dagger.dev/hilt/migration-guide.html#be-aware-of-differences-with-monolithic-components) In Dagger-Android,

@ContributesAndroidInjector

made it easy to have a module that is scoped to a specific Activity/Fragment, i.e.:

--- AppComponent:

@Singleton
@Component(
    modules = [
        ActivityBindingModule::class,
        AndroidSupportInjectionModule::class,
        // ...
    ]
)
interface AppComponent : AndroidInjector<MyApplication> {
    // ...
}


--- ActivityBindingModule:

@Module
internal abstract class ActivityBindingModule {
    @ActivityScope
    @ContributesAndroidInjector(modules = [MainActivityModule::class]) // MainActivityModule scoped to MainActivity
    internal abstract fun mainActivity(): MainActivity

    @ActivityScope
    @ContributesAndroidInjector(modules = [AnotherActivityModule::class]) // AnotherActivityModule scoped to AnotherActivity
    internal abstract fun anotherActivity(): AnotherActivity
}


--- MainActivityModule:

@Module
abstract class MainActivityModule {

    @FragmentScope
    @ContributesAndroidInjector(modules = [SignInFragmentModule::class])
    internal abstract fun signInFragment(): SignInFragment

    @FragmentScope
    @ContributesAndroidInjector
    internal abstract fun whatsNewFragment(): WhatsNewFragment

    @FragmentScope
    @ContributesAndroidInjector
    internal abstract fun settingsFragment(): SettingsFragment
}

Is something similar possible in HIlt? Or is there another strategy that might be similar? (random: if not, maybe in It seems like MainActivityModule and AnotherActivityModule would both use

@InstallIn(ActivityScoped::class)

, then both MainActivity and AnotherActivity could

@Inject

from either (I might be missing something?). Similarly, is it possible to have a setup where Fragments could

@Inject

things from their host Activity’s module? (e.g. in the above example, SignInFragment could inject anything from AppComponent, MainActivityModule, and SignInFragmentModule. We’ve taken advantage of this property of Dagger-Android, and I’m currently not quite sure what a migration to Hilt would look like.

In my project I have LoadingHandler class which is responsible for showing different kind of progress bars. I want to inject it in my fragments and attach its lifecycle to fragments view so I use ViewWithFragmentComponent but when I build my project it crashes with error which is telling me that LoadingHandler couldn't be provided. which is weird cause when I change ViewWithFragmentComponent to just FragmentComponent it works fine am I missing something?

Using dagger for the first time I have a doubt coming from Koin. I have a viewmodel which requires a param by constructor:

class UserDetailsViewModel(private val userId: String) : ViewModel() { ... }

With Koin I could inject it in my fragment/activity like this:

class UserDetailsFragment : Fragment() {
  private val viewModel: UserDetailsViewModel by lifecycleScope.viewModel(parametersOf(
    requireArguments().getString(USER_ID)
  ))
}

How can I achieve this with Dagger/Hilt?

Is there a way to use

@Inject

on a Kotlin

object

or are my only options to convert it to a

class

or use

@Provides

?

When utilizing subcomponents keep getting error

java.lang.reflect.InvocationTargetException (no error message)

. Is there any way to expand upon that to see what the actual issue is?

I'm using Dagger @Binds to binding the interface to implementation. I have genric mapper which transform one object to other.

interface DataMapper<T, R> {
     fun transform(from: T): R
 }

So I have couple of Data mapper in each use case layer . Let's I have something like this

class AccountDataMapper @Inject constructor():
DataMapper<Account,Result<Account>>{

override fun transform(account : Account){

}

}

How can I bind this. I have many mapper in the like Login Mapper,User mapper. When I use thr binder it's complaining that @Binds method parameter type must be assignable to the return type @Binds

abstract fun bindAccountMapper(mapper AccountDataMapper) : DataMapper<Account,Result<Account>>

Thanks in advance