AGP Upgrade Assistant and Configuration Cache Compatibility

Android Gradle Plugin Migration

The Android Studio AGP Upgrade Assistant automates the migration of build scripts to newer plugin versions to ensure alignment with the IDE release. To optimize build performance, many projects enable the Gradle configuration cache, which persists the output of the configuration phase.

When the Upgrade Assistant modifies the build script DSL or updates the AGP version, the existing configuration cache may become stale or incompatible with the new plugin logic. It is unclear if the IDE automatically invalidates the configuration cache during the migration process or if manual intervention is required to prevent synchronization errors.

• Does the AGP Upgrade Assistant trigger a mandatory cache invalidation upon applying changes?
• What is the expected behavior for projects with enabled configuration caching during a version migration?