The reason I think the issue is around stub genera...

# android

[nemi]

The reason I think the issue is around stub generation, is because if I declare an empty interface (even if it is in kotlin), make the dao interface extend this empty interface and only reference the empty interface in the dagger module method signatures, I don’t get an error

[lovis]

nemi: are you just using kapt, or do you apply plugin: 'kotlin-kapt'?

[nemi]

hey Lovis, I’m using kotlin-kapt

[lovis]

ok. and do you use kapt { generateStubs true }? because that’s basically “forbidden” for kapt3

[nemi]

nope, not using it

[lovis]

you’re not using the internal modifier by any chance? because that means “in module only”

[lovis]

I have this “something with kapt doesn’t work” check list, but maybe I need to add a new point to it, since it doesn’t work for you: https://gist.github.com/lmller/3c43eff454f7508474210fb2491b488a

[nemi]

If I don’t reference the interface spit out by the annotation processor in the dagger module, everything compiles. So I really think that the stubs are not generated. If I add another module to the project on which the AP runs and I consume the generated classes in the APP module everything is fun

[nemi]

fun -> fine

[lovis]

does 1.3.2 fix your issue? it says it fixes ? “Syntax error while generating kapt stubs”

[nemi]

I am using 1.1.3-2, but it’s all the same unfortunately

[lovis]

sorry I couldn’t help 😞 maybe file a bug

[nemi]

No worries, thank you for your time!. I have raised a bug in parallel but did not get any answer that really moves things forward. For the time being I can work around the issue easily in a way that’s not hacky but it might make things more difficult in the long run.