-
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
[KSP] java.lang.IllegalStateException: Unexpected element #4046
Comments
Thanks for reporting. This looks like a bug in Room's XProcessing, a library Dagger uses for KSP migration. I'll include a fix in the next version. |
Test: n/a Bug: google/dagger#4046 Change-Id: I8d185c76bc618876bb2f4a30ffc6806f3b9f16bf
I guess this has not been released yet if yes when is next release planned ? |
I have the same issue |
We're still hoping to get fixes for a few more issues in before doing another release (particularly, the incremental processing issues in #4063, #4060, #4054). Also, FYI, if you're really itching to get this fix you can always check out the HEAD-SNAPSHOT artifacts until the next official release is out. |
Thanks for trying it out and reporting back. Looks like the issues is that we haven't drop the new XProcessing jars into Dagger. That should be done once #4077 is submitted (probably on Monday). |
Hi i have fixed the issue by finding the root cause , we had 3 project but 2 of them does not have nay issue implementing latest 2.48 and it was one specific code that cause this error in one project It was an annotation in our code "@set:Inject " when i removed it was no more referencing to room compiler error , i am not sure why it was happening but removing that solved my issue @paladin952 your code also might have something like this, i found out this by removing module by module and narrowed down to file and specific set of code Thank you @bcorso for the prompt |
❤️ thanks a lot! you are right. I had one instance of @set:inject ... Thank you a lot! |
Okay, the updated XProcessing jars have been dropped into Dagger so I'm going to close this. The changes should be available in the HEAD-SNAPSHOT artifacts, and will be included in the next official Dagger release. |
I'm posting my issue here since it seems to be related to this thread, I just updated to Dagger 2.48.1 which should fix this issue, now I'm facing this crash when compiling:
As you can see, the stacktrace is a little bit different but looks the same. You can read the complete failed build here: https://github.com/VincentMasselis/TPMS-advanced/actions/runs/6419647393/job/17429926373 |
Hi, @VincentMasselis , thanks for reporting. Looks like we still missed some types here. I'll try to replace |
@kuanyingchou Tell me when it's done, I can try snapshot releases my repo easily |
Hi, @VincentMasselis , the fix is in now. Could you give HEAD-SNAPSHOT a try? |
I'm no longer facing this compilation crash ! Thanks @kuanyingchou ! But I'm facing a new one :/ I'll create a new github issue to report it |
@VincentMasselis had the same issue but looks like fixed as HEAD-SNAPSHOT is not giving the compilation error, hope we will get stable release soon |
I've encountered the following issues, and what's intriguing is that my project doesn't involve the use of any Room compiler or similar components.
The text was updated successfully, but these errors were encountered: