AutoFactory / Dagger integration requires fully qualified types about auto HOT 8 CLOSED

I have a similar problem when trying to create a factory that contains another generated factory as a provided dependency.

@AutoFactory
public class SomeClass {

  SomeClass(@Provided AnotherClassFactory anotherClassFactory,
            @Provided SomeDependency someDependency,
            int someValue) {
    ...
  }
}

Given that AnotherClass is placed in a different package, the generated SomeClassFactory does not import com.example.another.AnotherClassFactory and compilation fails. If I use the fully qualified type of AnotherClassFactory in the constructor of SomeClass compilation works.

Tested with 1.0-beta2.

from auto.

To anyone googling for "error: cannot find symbol", "Note: Generating a Provider for", "Prefer to run the dagger processor over that class instead": using fully qualified types solved the issue for me.

from auto.

I have the same problem but I can not pinpoint the cause.

from auto.

We are likely mismanaging imports. We will be upgrading to the new
javawriter when we peel it out of dagger 2, and fix several of these issues
at a stroke.
On Sep 9, 2014 2:14 AM, "Zubnix" [email protected] wrote:

I have the same problem but I can not pinpoint the cause.

—
Reply to this email directly or view it on GitHub
#124 (comment).

from auto.

Just ran into this too. Usually works great, but refactoring of the package structure triggered this bug. The workaround is okay, but annoyingly verbose.

from auto.

So, in short, for some reason, factory fails at using dependencies that are yet to be generated by autofactory itself. Looks like code gen does not include import for those dependencies. I might find some time to look at this. Is it currently being worked on and are contributions welcome?

from auto.

Any news on this issue? I just run into it and it will be great to get it fixed.

from auto.

Let's merge this into #297, I think it's two sides of the same coin

from auto.