-
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
No dependencies reported for generated source after 2.53 and Kotlin 2.1.0 update #4526
Comments
Also seeing this with Dagger 2.53 and Kotlin 2.0.21, so looks like this might be isolated to the Dagger 2.53 release? |
Thanks for reporting this! I think the issue is that the new I'll fix this and release a 2.53.1 update. |
I had a feeling the room link for the issue tracking was misleading! Oh well 👍🏻 |
Forgetting the originating element was an oversight. Gradle's incremental processing requires originating elements to determine when to reprocess files. This CL fixes `LazyMapKeyProxyGenerator` by extending `SourceFileGenerator`, which takes care of assigning the originating element. In addition, it removes some duplicate code that's already handled in `SourceFileGenerator` (e.g. adding the generated and suppress annotations). Fixes #4526 RELNOTES=Fixes #4526: Add the originating element in LazyMapKeyProxyGenerator. PiperOrigin-RevId: 702804185
When will the next version be released? |
I plan on doing a release today. |
After we updated to Dagger 2.53 and Kotlin 2.1.0 we now see a lot of similar warnings already reported in the past: #4182.
There is also already a new bug in the issue tracker: https://issuetracker.google.com/issues/381887333
Since we did not see any errors with Kotlin 2.0.21 and Dagger 2.52 I think this is not caused by our dependency or project setup.
This warning is shown only for every androidx.lifecycle.ViewModel and no other classes in our project:
The text was updated successfully, but these errors were encountered: