Status Update
Comments
jf...@block.xyz <jf...@block.xyz> #2
rp...@google.com <rp...@google.com> #3
Look like this was introduced by the fix for
jf...@block.xyz <jf...@block.xyz> #4
I can't add the property using gradle.beforeProject
like i've been able to do with other plugins (kapt) that have similar isolation issues. Perhaps because the JetGradlePlugin is added and executed earlier than my own code.
vm...@google.com <vm...@google.com>
cm...@google.com <cm...@google.com> #6
Thanks for the patch - I'll cherry pick and adapt internally
cm...@google.com <cm...@google.com>
cm...@google.com <cm...@google.com> #7
an...@google.com <an...@google.com> #8
Thank you for your patience while our engineering team worked to resolve this issue. A fix for this issue is now available in:
- Android Studio Ladybug Feature Drop | 2024.2.2 Canary 9
- Android Gradle Plugin 8.8.0-alpha09
We encourage you to try the latest update.
If you notice further issues or have questions, please file a new bug report.
Thank you for taking the time to submit feedback — we really appreciate it!
jf...@block.xyz <jf...@block.xyz> #9
I'm using Ladybug Feature Drop RC02 and the issue is back, did the change get reverted?
vm...@google.com <vm...@google.com> #10
I reviewed the details shared and I was unable to reproduce it on my end using the steps on RC1
, RC2
but being able to reproduce it on Canary6
(since fix landed on Canary9
).
I also checked that fix is actually present on the AS Ladybug Feature
release branch, however, this isn’t public yet but you can see those for the beta instead more in particular 2024.2.2-beta01
tag:
Having said that will be great if you can provide more details, since there's no sign so far that those changes got reverted somehow.
As a side note there’s the possibility that even if the fix is present as shown the change might not be taken into consideration in the case that platform artifact embedded in studio isn’t updated properly including it. I would say this is unlikely to happen due to automatic processes.
jf...@block.xyz <jf...@block.xyz> #11
When I commented earlier, I made extra certain that I was indeed using RC02. However since then I've been unable to duplicate again. My suspicion is that somehow the JetGradlePlugin from Ladybug was being used by Ladybug Feature Drop as I have both installed.
Description
Originally reported to jetbrains but the offending code comes from the Studio fork, which adds the following code:
Original report to intellij copied below:
Steps to reproduce
2024.9
JetGradlePlugin
Expected result (correct result):
No isolated projects issues
Actual result (faulty result):
You will see thousands of the following isolated projects violation:
Project ':whatever' cannot dynamically look up a property in the parent project ':'
fromcom.intellij.gradle.toolingExtension.impl.model.taskIndex.GradleTaskIndexBuilder.buildAll(GradleTaskIndexBuilder.java:39)
Additionally, the project that this reproducer sample is based on also throws the same error from
com.intellij.gradle.toolingExtension.impl.model.taskModel.GradleTaskModelBuilder.buildAll(GradleTaskModelBuilder.kt:31)
but for some reason I haven't determined yet, this reproducer sample doesn't exhibit.The stacktrace line numbers in the configuration cache report also does not line up with the code in the repo for the tag that this version of Studio is based on. Here's where I think the stacktrace points to, both of which are blank lines:
Neither class calls
DefaultProject.getProperties
as far as i can see in the source code in the links above.Full stacktrace from the configuration cache report (which I can't attach because it is 105MB)
And the other stacktrace from the other project where I have these issues