Note: Generating a MembersInjector or Factory for *. Prefer to run the dagger processor over that class instead.
See original GitHub issueIn Android on the qualitymatters project we are getting this message from Dagger:
Note: Generating a MembersInjector or Factory for com.artemzin.qualitymatters.QualityMattersApp. Prefer to run the dagger processor over that class instead.
Also what’s interesting is that the moment we’re trying to add error-prone, compiling will fail with IllegalStateException couldn't register MembersInjectionBinding ... was already registered for Key{type=com.artemzin.qualitymatters.QualityMattersApp}
. Full Stacktrace is here.
Could you explain this note to @artem-zinnatullin & me?
Issue Analytics
- State:
- Created 8 years ago
- Comments:25
Top Results From Across the Web
"Prefer to run the dagger processor over that class instead" in ...
"Note: Generating a MembersInjector or Factory for com.packageNameXXX.CourseDiscoveryMapFragment. Prefer to run the dagger processor over that class instead.".
Read more >Prefer to run the dagger processor over that class instead ...
When I build my project I see a note: Generating a MembersInjector or Factory for com.demo.MainActivity. Prefer to run the dagger processor ......
Read more >"Prefer to run the dagger processor over that class instead" in ...
I'm getting this note in the build whenever I do an inject into a kotlin class (btw, I have a mixed android project...
Read more >Android 102 : Why does dagger generate MembersInjector for ...
We introduced MembersInjector as something which helps us inject all dependencies in a class at once, instead of doing it separately for each...
Read more >Android - Dagger
Dagger is a replacement for these FactoryFactory classes that implements the dependency injection design pattern without the burden of writing the boilerplate.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I did and I’m still getting it.
2.2 didn’t fix the problem. Dagger team: do you think it’s a problem & if so -> would you be open for a PR?