AGP Upgrade Assistant and Configuration Cache Compatibility

Does the AGP Upgrade Assistant invalidate the configuration cache?

No – the assistant only edits build scripts and does not trigger Gradle’s configuration‑cache invalidation.

Confirmed facts

• The AGP Upgrade Assistant modifies the build.gradle(.kts) files and/or the gradle-wrapper.properties but does not invoke any Gradle task that clears the configuration cache.
• Gradle’s configuration cache key incorporates the build script contents and the classpath; changing the AGP version or DSL therefore changes the key, so a cache created with the old AGP becomes stale.
• If the cache is not cleared, a subsequent build may reuse the stale cache, leading to synchronization errors or failures that reference removed/changed APIs.

Steps to avoid stale‑cache issues

1. Before running the Upgrade Assistant, disable the configuration cache by adding --no-configuration-cache to the Gradle command or setting org.gradle.configuration-cache=false in gradle.properties.
2. Run the assistant as usual (e.g., via Android Studio → Build → AGP Upgrade Assistant).
3. After the assistant finishes, re‑enable the configuration cache (remove the flag or restore the property) and perform a clean build (./gradlew clean assembleDebug) to populate a fresh cache.
4. Alternatively, keep the cache enabled and manually delete the .gradle/configuration-cache directory after the assistant runs, then run a normal build to regenerate the cache.

Missing diagnostic detail

If you are observing build failures after the migration, please share the exact error message (including any stack trace) so we can verify whether a stale configuration cache is the root cause.