dagger-2

I'm trying to use dagger 2 on my Android application to inject the new ViewModel from arch android library. From what I see on this sample https://github.com/googlesamples/android-architecture-components/tree/e33782ba54ebe87f7e21e03542230695bc893818/GithubBrowserSample I need to use this: @MustBeDocumented @Target(AnnotationTarget.FUNCTION, AnnotationTarget.CONSTRUCTOR, AnnotationTarget.PROPERTY_GETTER, AnnotationTarget.PROPERTY_SETTER) @Retention(AnnotationRetention.RUNTIME) @MapKey internal annotation class ViewModelKey(val value: KClass<out ViewModel>) @Module abstract class ViewModelModule

In Dagger 1 I had a base class setup such that it would handle creating a scoped graph and injecting dependencies into the current object. For example... public abstract class MyBaseActivity extends Activity { private ObjectGraph graph; protected void onCreate(Bundle savedInstanceState) { graph = ((MyApp) getApplication()).plus(getModules()); graph.inject(this); } protected Object[] getModules(); } public class MyClass extends MyBaseActivity { @Inject SomeDep someDep; @Override protected Object[] getModules() { return new Object[/* Contains a module that provides SomeDep */]; } } This allowed

I have a custom view extending a TextView . Where should I call my component to inject the view? component.inject(customTextView); So, I've find out that I need to add the injection in the constructor of my custom view (in all of them, or make one call the other) Example: public class CustomTextView extends TextView { @Inject AnyProvider anyProvider; public CustomTextView(Context context) { this(context, null); } public CustomTextView(Context AttributeSet attrs) { super(context, attrs); Application.getComponent(context).inject(this); } } My general solution for that kind of thing is this

I have a heavily dependency injected ( dagger2 ) application. I would like to run an espresso test without having the test navigate through the whole application, and log into the application. I would like to start on my teleActivity, and mock the login manager. However in any @test function, we have already hit the null pointer as we have called onCreate. If I override it before we launch the activity (show below) the activity is null. To my understanding, the ability to switch our underlining dependencies is a large reason why we use Dagger2, else it would be just a very over engineered

How to inject a fragment from the package androidx.fragment.app.Fragment ? I'm using the dagger-android framework to inject my dependencies in my code. As the documentation says I do this to inject my fragment @Override public void onAttach(Activity activity) { AndroidInjection.inject(this); super.onAttach(activity); // ... } the problem is that AndroidSupportInjection class accept only fragments of the package android.support.v4.app.Fragment or if I use AndroidInjection class only accept fragments of the package android.app.Fragment and I want to use fragments of the androidx.fragment.app