so I’m injecting a couple of dependencies into my ViewModel like so ```@HiltViewModel class Authent...

# compose

[oday]

so I’m injecting a couple of dependencies into my ViewModel like so

@HiltViewModel
class AuthenticationViewModel @Inject constructor(
    private val determineAuthStatus: DetermineAuthStatus,
    private val populateUserPrefs: PopulateUserPrefs
) : ViewModel() {

and I want to use the viewmodel in a composable like so

val viewModel : AuthenticationViewModel = hiltViewModel()

but I get that the viewmodel does not have any zero-argument constructors, I’ve already created the module for these 2 deps to be provided

this composable that i’m using the viewmodel in, is started inside an Activity which I’ve set @AndroidEntryPoint on, what am I missing ?

[Chris Fillmore]

Can you show the module?

[Berkeli Alashov]

I usually check this when it happens to me https://dzolnai.medium.com/dagger-hilt-viewmodelclass-has-no-zero-argument-constructor-causes-76d40007eb28

[FunkyMuse]

Did you add @HiltAndroidApp in your Application?

[oday]

this is the module https://github.com/Odaym/Booksum/blob/master/authentication/src/main/java/com/saltserv/authentication/AuthenticationModule.kt

[oday]

I don’t think I need a module even

[oday]

the problematic file there is AuthenticationViewModel

[oday]

so the MainActivity calls Authentication composable

Authentication composable creates new instance of AuthenticationViewModel

AuthenticationViewModel injects populateUserPrefs and determineAuthStatus

AuthenticationViewModel has @HiltViewModel and MainActivity has @AndroidEntryPoint, Application class has @HiltAndroidApp, populateUserPrefs and determineAuthStatus both have @Inject constructor so that Hilt could “see” them

[oday]

what if it has something to do with MainActivity being in another module than the rest of the files like Authentication and AuthenticationViewModel?

[oday]

[oday]

so if I initialize the viewmodel in the same file where @AndroidEntryPoint is defined, using by viewModels() it works fine

but if I initialize it inside the composable using = viewModel() it does the no zero-argument constructor error

[oday]

I want to initialize it inside the composable, I dont want to initialize it inside the activity and then pass the viewmodel to the composable, that’s just dumb

[FunkyMuse]

You need to enable aggregating task for hilt in your app module

[oday]

hmm what’s that

[oday]

kapt {
 correctErrorTypes true
}

?

[oday]

ah this

hilt {
    enableAggregatingTask = true
}

[oday]

that did nothing

[oday]

there is something fundamentally wrong with what’s happening

[oday]

HALP!

[oday]

despair

[Reda AOUTEM]

In your code, you’ve written val viewModel : AuthenticationViewModel = viewModel() instead of = hiltViewModel() . Could it be the mistake ?

[oday]

Tried that already

[oday]

Turned out to be an issue of multi module, main activity that has AndroidEntryPoint is sitting in another package than where I'm calling the composable

[oday]

Opted for single package instead of this headache