After a lot of research and having talked to one of the Lombok developers, it turns out that because javac does class loading based on hashCode(), the order of annotation processors running in this scenario is essentially random, and what’s worse, random between multiple runs. There currently does not seem to be a solution to … Read more
Your CoffeeMachine needs CoffeeMaker. And you have declared that Dagger will take care of providing that dependency to the CoffeeMachine by annotating the constructor with @Inject. But Dagger says: CoffeeMaker cannot be provided without an @Provides-annotated method Because you haven’t specified anywhere how CoffeeMaker object should be created. @Injecting SimpleMaker is not enough, because SimpleMaker … Read more
I have run into the same issue and found this article. In a nutshell you have this options: Make not generic wrapper class containing injected fields, make it to be a field of your class and inject it instead of generic class itself. Inject child non-generic class instead of base class. All annotated with @Inject … Read more
What I did to solve this is File – Invalidate Caches/Restart.
@Provides @Singleton public AuthManager providesAuthManager(AuthManager manager) { return manager; } Your providesAuthManager method which provides an AuthManager depends on an AuthManager. There’s your cycle 🙂
I recently post the answer to a question like this in this post : Dagger 2 : error while getting a multiple instances of same object with @Named You need to use @Named(“someName”)in your module like this: @Module public class ApplicationModule { private Shape rec; private Shape circle; public ApplicationModule() { rec = new Rectangle(); … Read more
Dagger depends on JSR 330, the Java standard annotations which are used for dependency injection (think: @Inject, @Singleton, etc.). This is a separate jar that you have to include. If you were using a build system with integrated dependency management (Maven, Gradle, Ant+Ivy, sbt) you’d get this for free. If you’re still copying around jars … Read more
I got this same error because I forgot to expose the objects provided by the modules in the parent component to the other components that are depend on it. Parent component example: @Singleton @Component(modules = {AppModule.class}) public interface AppComponent { AppPref exposeAppPref(); /* my issue was caused by forgot this line, the method name doesn’t … Read more
ApplicationComponent being renamed to SingletonComponent, to allow usage of Hilt in non-Android Gradle modules link
I encountered the same situation. One way to ease a bit the injection from a common component in all Activities is the following: 1) Extend the Application class to be able to create the common component and keep a reference to it. public class ApplicationDagger extends Application { private ApplicationComponent component; @Override public void onCreate(){ … Read more