IssueTracker

Thanks a lot for the sample project!

This looks like a Gradle bug, I've filed https://github.com/gradle/gradle/issues/28566.

In the mean time, we'll try to come up with a fix/workaround in AGP.

Just curious, does it happen for older Gradle versions?

Yes, it happens for all Gradle versions (as long as it's larger than the minimum required by AGP). Regarding AGP version, it happens on AGP 8.3+, not on AGP 8.2.

Note that the issue happens only if the user runs ./gradlew assemble (it doesn't happen if they run ./gradlew assembleDebug or ./gradlew assembleRelease individually).

So the current workarounds include:

• Building the 2 variants separately: ./gradlew assembleDebug && ./gradlew assembleRelease instead of ./gradlew assemble
• Making the build single-threaded: ./gradlew assemble --max-workers=1

Another workaround is to enable configuration cache, if that works for your project, that would be the best workaround so far:

• Enable configuration cache: ./gradlew assemble --configuration-cache

We've added a workaround in AGP to avoid this issue (by removing relevant usages of ValueSource which caused the deadlock): https://android.googlesource.com/platform/tools/base/+/bd3578169629317cda426c0e9c02bfa39a99f0a3 (this link may take a few weeks to show up).

It will be included in AGP 8.3.2, 8.4.0-rc01, and 8.5.0-alpha04.

Thank you for this report!

The cherrypicked commit for AGP 8.3.2 is being reviewed, keeping this bug open for a little longer until that commit gets merged.

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 Iguana | 2023.2.1 Patch 2
• Android Gradle Plugin 8.3.2

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!

Great to hear, thanks for your confirmation!