am getting `Component not initialized` when running tests

# dagger

[Marko Novakovic]

am getting Component not initialized when running tests

[Marko Novakovic]

hey

[Marko Novakovic]

I was able to fix it

[Marko Novakovic]

inside your andriodTest create separate Manifest.xml file and define startup inside of it and disable automatic initialization

[Marko Novakovic]

do it manually

[Jay Barria]

I created AndroidManifest inside androidTest added tools:node="remove" to disable automatic initialization but still failed to create the hilt component for testing. In my case it's not merging at all with the main app manifest.

So I ended up refactoring the startup, removing manifest initialization for the main app altogether and manually triggering the startup inside the Application class. Not ideal, but I didn't had any espresso UI testing issues before migrating Dagger to Hilt.

[Zsolt.bertalan]

@Marko Novakovic @Jay Barria Thank you for your replies. Sorry, I noticed your replies only now, so I will work on it now, trying your recommendations, too.

[Zsolt.bertalan]

Unfortunately androidTest manifest is not overriding the main manifest, so I had to do what Jay recommended. It seems to work, thank you all.

[Enrico Del Zotto]

Got same issues… so in short you avoid the manifest init

[Enrico Del Zotto]

and i presume they have same issue on NowONAndroid : https://github.com/android/nowinandroid/commit/489502ba134481c300f1d8ac8ddd4f93a339a7d7

[Enrico Del Zotto]

the only thing they just decided not to use their own library

[Enrico Del Zotto]

same here : https://issuetracker.google.com/issues/169258537