@ContributesAndroidInjector, custom scope and @AssistedInject issue

[cashapp]

@ContributesAndroidInjector, custom scope and @AssistedInject issue

[davidliu]

I'm guessing you're using the multibinds ViewModelFactory pattern, where you've got an omni factory made at the @Singleton level that can create all the other ones. Don't do that. The omni-factory, since it lives at the @Singleton level, requires all the dependencies to be filled at that level, and it can't get the @AuthScope dependencies.

Instead of using the multibind factory stuff, just directly get the factory of the vm you need and use that.

[davidliu]

Also, this issue should be closed, as it's not really related to AssistedInject at all, just a bog-standard Dagger question.

[Suet]

Hello.
As I mentioned at the very beginnig "Everything compiles and works fine if I don't use @AssistedInject, @AssistedInject.Factory and ViewModelAssistedFactoriesModule."

[davidliu]

Yes, but you wanted to use @AssistedInject right? So I don't see why that's relevant.

[Suet]

That's exactly what my question was about. I wondered if the code working fine without assisted inject library should still work if I use it and amend a code accordingly. As far as I see there is not much changed in a code. But something breaks and it stops to compile.