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
TaskExecutionException Migrating Dagger 2.28.3 to Newer Dagger Version #4138
Comments
Hi @wahyupermadie, can you try again with the latest version of Dagger and give the stacktrace with that version? We don't maintain branches for old versions of Dagger, and the code has change a lot since then. |
Hi @bcorso I'm trying with 2.43 and also get the same error I think, I'm not able to use the latest version due to metadata and Kotlin poet conflict
|
The error you're hitting is something we don't expect to ever fail (which is why we use Furthermore, even if we were able to find the issue and fix it you wouldn't be able to get the fix unless you upgraded to the latest version of Dagger because we don't release patches for older versions of Dagger. Thus, I think in order to make progress on this you really need to be able to use the latest version of Dagger. |
is there any way to me can debug it ? I don't see we able to use the latest dagger in near future due to conflic with our kotlin and kotlin poet and maybe some others lib as well @bcorso |
Hi @bcorso I have been trying to bump my dependencies But I got an error that the code generated by Dagger was not able to resolve my code generation
UPDATE:: I Have been using the generated class directly, and the issue related missing import resolved, but then I faced this issue again #4138 (comment) |
Do you have kapt in your build gradle? upgrade to AGP 8+ , also use Java 17. |
@pedrovarela86 yes I'm using kapt, but for upgrading to agp 8 i think its not possible now for my project |
@wahyupermadie fwiw I've added the updated error message to the |
Hi @bcorso thanks for the update, btw what is the min requirement to use that ? and do that version also eligible for android support ?
|
Hi @bcorso thank you, i found the message error
this component is using @Subcomponent.Builder, but why its indicated as Factory? |
We use the same logic for both factory and builders so you can ignore that nuance in the error message. The error message is saying that we could not find the required abstract method in @Component
interface CallOptionsComponent {
@Component.Builder
interface Builder {
// This is the method we can't find (doesn't actually need to be called "build")
CallOptionsComponent build();
}
} |
Hi @bcorso thanks for the response, but still I got confused here My code in the component builder looks like this
and inside and I register the screen by
I don't think we need to have |
Looks like there's a lot going on there, and I'm not sure we're going to be able to debug this with just small snippets of the code. If you can provide a repro project I can help take a look. |
Hi team, I got this kind of error when I wanted to bump my dagger to 2.42, since my version is already very old 2.28.2, I tried again with 2.29.1 but I got the same issue when I tried to bump to 2.42. I there any way to debug it, because I don't really understand the stack trace message provided in the log. Thank you
AGP: 7.2.2
Java: 11
Kotlin: 1.6.21
Dagger: 2.29.1
The text was updated successfully, but these errors were encountered: