the error I was talking about was something along the lines of:

dagger.internal.codegen.ComponentProcessor was unable to process this class because not all of its dependencies could be resolved. Check for compilation errors or a circular dependency with generated code.

and it was there, even though the final cause would seem to be something different, as it was in your case. What I'm saying is, it didn't detect the cycle, but still it suggested it as a possible cause