Build fails with Android Gradle Plugin 4.1.0

[barbeau]

Summary

After updating from classpath 'com.android.tools.build:gradle:4.0.2' to classpath 'com.android.tools.build:gradle:4.1.0', the demo app will no longer build and I get the error:

> Extension not initialized yet, couldn't access compileSdkVersion.

If I change back to classpath 'com.android.tools.build:gradle:4.0.2' it builds and runs without any problems.

Here's a branch showing the issue:

https://github.com/googlemaps/android-maps-utils/tree/sean/gradle-4.1.0

I believe this is an issue with Android Gradle Plugin 4.1.0, so I've opened an issue on the Google IssueTracker here:
https://issuetracker.google.com/issues/172273529

Expected behavior

Demo app should build (and from within Android Studio, the demo app should launch)

Observed behavior

Executing tasks: [:demo:assembleDebug] in project C:\android-projects\android-maps-utils

Starting Gradle Daemon...
Gradle Daemon started in 2 s 668 ms
Configuration on demand is an incubating feature.

FAILURE: Build failed with an exception.

* What went wrong:
Could not determine the dependencies of task ':demo:compileDebugJavaWithJavac'.
> Extension not initialized yet, couldn't access compileSdkVersion.

Steps to reproduce

1. Clone/checkout https://github.com/googlemaps/android-maps-utils/tree/sean/gradle-4.1.0
2. Run the demo app from within Android Studio, or run ./gradlew :demo:assembleDebug from the command line

Environment details

See branch https://github.com/googlemaps/android-maps-utils/tree/sean/gradle-4.1.0 for code.

Build: AI-201.8743.12.41.6858069, 202009231536,

AI-201.8743.12.41.6858069, JRE 1.8.0_242-release-1644-b01x64 JetBrains s.r.o, OS Windows 10(amd64) v10.0 , screens 1536x960, 1707x960, 1536x864

AS: 4.1; Kotlin plugin: 1.4.10-release-Studio4.1-1; Android Gradle Plugin: 4.1.0; Gradle: 6.5; NDK: from local.properties: (not specified), latest from SDK: (not found); LLDB: pinned revision 3.1 not found, latest from SDK: (package not found); CMake: from local.properties: (not specified), latest from SDK: (not found), from PATH: (not found)

[barbeau]

Google marked this issue as "Won't Fix (Intended Behavior)", with this response:

Thank you for filing the issue. The problem is use of org.gradle.configureondemand=true and subprojects { ... closure in the root project build.gradle. These 2 features have not been designed to work together, you can either use configuration on demand or eagerly apply configuration to projects. To fix this:

• you can remove org.gradle.configureondemand=true from gradle.properties
• or you can do the following:
  • add apply plugin: 'com.android.library' to your library projects
  • apply more configuration logic if these projects get evaluated by changing the subprojects closure with:

subprojects { project ->
   project.plugins.withId('com.android.library') {
       if (project.ext.artifactId == null) return

       project.plugins.apply('com.hiya.jacoco-android')
       project.plugins.apply('maven-publish')
       project.plugins.apply('signing')
   }
}

This will apply additional plugins only for library projects that are evaluated as part of the build.

The reason why this changed is use of Gradle build services to share state between projects. In your case, because you are apply the Android Library plugin to :library project that project will create a build service that needs compileSdkVersion information. However, because you are using configuration on demand, project build script will not run i.e compileSdkVersion will be null. Then, when :demo project accessing that build service (it is shared between all projects), the >service fails to initialize correctly.

[barbeau]

Still an issue with plugin classpath 'com.android.tools.build:gradle:4.1.3' (master branch at 52d0e58) and Android Studio:

Android Studio 4.1.3
Build #AI-201.8743.12.41.7199119, built on March 10, 2021
Runtime version: 1.8.0_242-release-1644-b01 amd64
VM: OpenJDK 64-Bit Server VM by JetBrains s.r.o
Windows 10 10.0
GC: ParNew, ConcurrentMarkSweep
Memory: 1546M
Cores: 8
Registry: ide.new.welcome.screen.force=true, external.system.auto.import.disabled=true
Non-Bundled Plugins: org.intellij.plugins.markdown, com.intellij.marketplace, org.jetbrains.kotlin

To clarify behavior, if you do "Rebuild" within Android Studio it will build successfully, but when you try to run the demo app then you get a "Build failure" with the above info.