-
Notifications
You must be signed in to change notification settings - Fork 2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Mysterious error when Dagger tries to report missing binding in certain circumstances #1614
Comments
I was actually coming here to post the same issue. I haven't been able to make heads or tails of it. |
Edit: still get the same error This issue is might be caused by this. |
Ran into this today, seems to be causes by complex Multibinding Key. Not sure what, but removed my multi bindings with complex keys and it goes way. It's an annotation with two enums in it |
FYI, if it helps the annotation is defined in kotlin and the two referenced enums are in a different module - it looks like a kapt bug looking at the exception - going to try and move stuff to java/same module to see if it fixes it. |
OK, reproduceable ; Module A: Can be kt or java doesn't matter
Module B: (implements module a) Complex Key Type:
Will produce:
Moving the enum into the same module fixes the issue for me. |
Might be #1991 |
After looking into it a bit, seems like Dagger is not properly handling annotations on interfaces from libraries that themselves have annotations not on the current module's compile classpath.
The annotation itself is available, but the annotation attribute return type is marked as
<nulltype>
(even thoughvalue()
is clearly a string), which causes a failure during validation.The text was updated successfully, but these errors were encountered: