Status Update
No update yet.
Comments
js...@google.com
je...@google.com
bi...@google.com
Maybe a dup of
jf...@block.xyz
Android Gradle Plugin: 8.7.1
Could you try the latest canary, AGP 8.8.0-alpha09?
bi...@google.com
I just updated to Android Gradle Plugin: 8.7.2 and the bug is fixed.
an...@google.com
I spoke too soon. The bug appears gone when I use a different computer, but that is only because the lint check is disabled on it. The computer with the false positive is a new cloning of my github project which apparently has the lint check enabled. The AGP 8.8.0-alpha09 plugin will not work on ladybug, and I'm too busy to switch to a canary build of android studio just to fix a false positive lint check, sorry.
dg...@oreillyauto.com
I just tried running lint on two more of my computers, one which also has a fresh clone of the github project, and one which has an "ancient" (but up to date) clone of the project -- the two computers have very different Settings -> Editor -> Inspections choices. The old clones do not have this lint check anywhere in their choices, whereas new clones do. Very odd indeed. (I have .idea/ in my .gitignore BTW).
Description
In Android Studio Ladybug Canary 09, when tests are run from the IDE, the injected
ijresolvers2.gradleinit script contains multiple instances ofProject.hasPropertyadded byaddGradleAndroidTestListener.gradlefromGradleAndroidProjectResolverExtension.Project.hasPropertyis an isolated projects violation in most cases because if the project doesn't have the requested property, Gradle searches upward through parent projects to the root.