IssueTracker

From the logs:

2023-12-06 16:34:17,743 [89868589]   INFO - #com.android.tools.idea.gradle.project.build.invoker.GradleBuildInvoker - About to execute Gradle tasks: [...]

do you see the same issue?

Unfortunately, yes...

I see some namespaces warnings Namespace '<redacted>.versioncheck' is used in multiple modules and/or libraries... could it be related?

Nvm, it's not 😅

How can I assist?

Thanks for reporting on required info. The namespace-related warning should not really matter to this problem.

Because this reproduces from the command line, can you please file an issue against Gradle (https://github.com/gradle/gradle/issues) as the root cause is almost certainly in the Gradle build tool? Once there is an issue I can ping the Gradle team and hopefully someone from their end will be able too look into it.

Thanks!

Will you do me the courtesy, please, to remove/restrict the https://issuetracker.google.com/issues/315023802#comment2 gradle commands? Thank you

Re #9: Comment #2 is updated now.

Superb! Thank you! Are you able to read #8? Idk how restricted vs restricted+ actually works...

Sadly not, I think I should be able to read it if you reduce access to restricted (which should also avoid having it accessible publicly)?

Sent again with restricted

I have access now, thanks.

Issue https://github.com/gradle/gradle/issues/26060 was filed by me, but the root cause has been fixed on the IDE side. Mixing clean and assemble tasks in the invocation was tripping Gradle, causing the error. However, from logs in Iguana, I can see that all clean tasks are invoked first, followed by assemble&friends. Given that, this does look like a Gradle issue to me.

The plot thickens... Sorry for wasting your time, had no idea you're the same person. Okay, I'll open a gradle issue, I just need to reproduce it first with an open source project or create a new one with my current structure

It's reproducible in nowinandroid, main branch, but now, if I use the Rebuild Project complex command in terminal I get this <attached> even though :app:clean task does exist...Disabled configuration-cache and it's the same thing... I'll open the github issue tomorrow...I'm trying to create a reproducer repo first

I have this same issue after upgrading to Android Studio Iguana | 2023.2.1. It seems the problem lies in that the new Android Studio adds a :plugins:testClasses task to the rebuild task list (which the previous didn't).

Our project configuration has a plugins module that is pluginManagement { includeBuild("plugins") }'ed in settings.gradle.kts and for some reason Gradle chokes on it.

However I discovered that I can work around the issue by defining gradle.startParameter.excludedTaskNames.addAll(listOf(":plugins:testClasses")) in settings.gradle.kts, which reverts the breaking task list change.

I've created a new ticket for the buildSrc issue - https://issuetracker.google.com/issues/328871352

I fixed it by adding following line to settings.gradle.kts file:

gradle.startParameter.excludedTaskNames.addAll(listOf(":build-logic:convention:testClasses"))

source: https://medium.com/@jihyeonbae424/android-studio-iguana-build-logic-buildsrc-rebuild-projects-fail-testclasses-112f2ccd744d

This is not a gradle issue because ./gradlew clean and ./gradlew assembleDebug are working from the command line.

Adding this line to the top of my settings.gradle.kts also worked for me as shown in the above comment #23:

gradle.startParameter.excludedTaskNames.addAll(listOf(":build-logic:convention:testClasses"))

I created a new project based off of the multimodule sample from architecture samples:

architecture-samples multimodule sample

which is why my folder with convention plugins is also named build-logic and therefore the adding the above line worked for me.

Addressing these issues in a timely manner helps us Android devs take on recommended changes like starting to use Kotlin DSL. Thanks.

Attached is MyApplication.zip, which is literally just a new project but also I've added an AndroidApplicationConventionPlugin if you want to take a look. It only Rebuilds with the line I have listed in the above comment.

Comment #23 did it for me.

That workaround was giving me an error when I enabled the configuration cache, so I'm using this now:

import org.gradle.api.internal.StartParameterInternal

if (!(gradle.startParameter as StartParameterInternal).configurationCache.get()) {
    gradle.startParameter.excludedTaskNames.addAll(listOf(":build-logic:convention:testClasses"))
}