dagger-2

I've started using Dagger2 to manage dependencies and I'm trying to understand how I can use DI to provide a singleton GoogleApiClient. The motivations for this are: reduce boilerplate code : multiple Activities & Fragments require a GoogleApiClient improve testability : currently these Activities and Fragments are not well tested I want to provide a Singleton GoogleApiClient at the Application scope. How do you handle callbacks? Whether you choose an auto-managed or manually-managed connection , there are some callbacks that must be handled: GoogleApiClient.ConnectionCallbacks (manual only)

I'm getting the following error: Error:(8, 1) error: java.lang.String cannot be provided without an @Inject constructor or from an @Provides- or @Produces-annotated method. I'm stuck trying to make a module that provides two qualified Strings. Here is the simplified setup of dagger. @Singleton @Component(modules = [GreetingsModule::class]) interface AppComponent { fun inject(activity: MainActivity) } @Qualifier annotation class Spanish @Qualifier annotation class French @Qualifier annotation class English @Module @Singleton class GreetingsModule { @Provides @Spanish fun providesHola(): String

I'm working on an android application and I'm trying to inject a field which is type parameterized in an abstract class : BaseListFragment public abstract class BaseListFragment<E, A extends ArrayAdapter<E>, S> extends BaseFragment { @Inject protected S service; } But I get this following error at compile : error: cannot find symbol class S Here is my code for BaseFragment : public class BaseFragment extends Fragment { @Override public void onCreate(Bundle savedInstanceState) { super.onCreate(savedInstanceState); ((App) getActivity().getApplication()).inject(this); } } here is my service

I'm working on setting up Dagger 2 into my android project. It is my first time with this framework and everything goes well so far. But I'm seeing different approaches on the way you can set up this framework in your project and I wonder which one is better, because I compare both and for me the result is kind of the same. I followed this guide: https://github.com/codepath/android_guides/wiki/Dependency-Injection-with-Dagger-2 Searching on Internet all of them use this approach. It use @Module and @Component to define the dependencies. and your application ends up like this: public class

In order to learn Dagger 2 i decided to rewrite my application but I'm stuck with finding the proper solution for the following problem. For the purpose of this example let's assume we have an interface called Mode : public interface Mode { Object1 obj1(); //some other methods providing objects for app } and two implementations: NormalMode and DemoMode . Mode is stored in singleton so it could be accessed from anywhere within application. public enum ModeManager { INSTANCE,; private Mode mode; public Mode mode() { if (mode == null) mode = new NormalMode(); return mode; } public void mode(Mode

Suppose I'm building a car and I have several Brake beans with different implementations class Car { @Inject Car(@BrakeType(value="abs")Brake frontBrake, @BrakeType(value="nonabs")Brake rearBrake) { } } @Qualifier @Retention(RetentionPolicy.RUNTIME) public @interface BrakeType { String value(); } interface Brake {} @BrakeType(value="abs") class AbsBrakeImpl implements Brake { @Inject AbsBrakeImpl() {} } @BrakeType(value="nonabs") class BrakeImpl implements Brake { @Inject BrakeImpl() {} } why does my CarModule have to define @Provides for the specific Brake types? Shouldn't the custom

I'm following the Dagger2 sample of TODO app but encounted with 2 errors. Error1: can't find symbol DaggerNetComponent . (Which is actually there) Error2: Sharedpreference can't be provided without @provider-annotated method.(Which I think results from error1) And here's my long but simple code: Three modules: @Module public class AppModule { private final Application mApplication; AppModule(Application application) { mApplication = application; } @Provides Application provideApplication() { return mApplication; } } @Module public class LoadingModule { public final LoadingContract.View mView;

I have a scoped dependency in my Activity and I want to test that activity with some mocks. I have read about different approach that suggest to replace Application component with a test component during the test, but what I want is to replace the Activity component. For example, I want to test the Activity against mock presenter in my MVP setup. I believe that replacing component by calling setComponent() on Activity will not work, because Activity dependencies already injected via field injection, so during the test, real object will be used. How can I resolve this issue? What about Dagger1?