Feature request: Manually regenerate application component about dagger HOT 1 CLOSED

I don't think we can add this as a feature to Hilt since it basically subverts the notion of what @Singleton means since now those objects can be instantiated more than once (and you could have multiple instances still around if something else is holding on to the previous instance).

For your particular solution, besides the obvious issue of this reflecting on internal Hilt implementation details that aren't guaranteed, you should be careful about code obfuscation. Also, as alluded to above, this doesn't change that existing things may already have references to the old component that won't be dropped. So any existing activity, fragment, service, etc, won't be updated immediately. You might be fine with that, but you may also consider that weird things can happen on configuration change. For example, if the ApplicationComponent is switched and then a configuration change happens, the new activity would use the new ApplicationComponent while any ViewModel created before that would not because ViewModels are retained through configuration change. This could cause unexpected situations since your Activity would be using different singletons than your ViewModel. So overall, I wouldn't recommend this pattern.

from dagger.