Closed yschimke closed 4 months ago
Possibly relevant - we set dependency.analysis.autoapply=false
and apply separately
We're also seeing this on our internal project and we also disabled auto apply.
The issue does indeed go away if dependency.analysis.autoapply=false
is omitted. It happens because the plugin configures itself for Android projects inside an afterEvaluate
block. I think this may not be necessary. I validated that if I remove the afterEvaluate, this error doesn't occur anymore.
Example PR https://github.com/google/horologist/pull/2009
Build scan link N/A - I think failing during setup
Plugin version
1.29.0
Gradle version 8.5
JDK version 17
(Optional) Kotlin and Kotlin Gradle Plugin (KGP) version 1.9.21
(Optional) Android Gradle Plugin (AGP) version 8.2.2
Describe the bug
To Reproduce Steps to reproduce the behavior: