agp-9-upgrade

Migrates Android projects to Android Gradle Plugin 9 with new DSL and built-in Kotlin.

1|Updated Jun 9, 2026
One-click install
npx skills add https://github.com/kariemSeiam/android-claw --skill agp-9-upgrade-kariemseiam
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: agp-9-upgrade
Source: https://github.com/kariemSeiam/android-claw/tree/main/skills/installed/agp-agp-9-upgrade
Command: npx skills add https://github.com/kariemSeiam/android-claw --skill agp-9-upgrade-kariemseiam

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Upgrading an Android project to Android Gradle Plugin (AGP) 9 involves many breaking changes, including a new DSL, built-in Kotlin support, and kapt deprecation. This Skill guides the migration step by step so the project builds correctly on AGP 9 without missing critical changes. ## Core Features & Use Cases - Guided AGP 9 Migration: Walks through dependency updates (KSP 2.3.6+, Hilt 2.59.2+), built-in Kotlin migration, new AGP DSL adoption, and gradle.properties cleanup. - kapt to KSP Migration: Explains how to check KSP compatibility of annotation processors and apply the legacy-kapt plugin when migration is not possible. - BuildConfig and DSL Recipes: Provides reference guides for custom BuildConfig fields, APK renaming via androidComponents.onVariants, and Paparazzi workarounds for Gradle 9. - Use Case: A developer with an AGP 8 project asks to upgrade to AGP 9; the Skill checks the current version, updates dependencies, migrates the DSL and Kotlin setup, and verifies the result with Gradle sync and build dry-runs. ## Quick Start Migrate my Android project to AGP 9 and verify that the Gradle sync and build still succeed.

Frequently Asked Questions about agp-9-upgrade

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I migrate my Android project to AGP 9?▼

First ensure the project is on the latest stable AGP version, then update KSP to 2.3.6+ and Hilt to 2.59.2+, migrate to built-in Kotlin, adopt the new AGP DSL, move kapt usages to KSP, and clean up obsolete gradle.properties flags. Verify with a Gradle sync and ./gradlew build --dry-run.

How to migrate kapt to KSP in an Android project?▼

Remove the org.jetbrains.kotlin.kapt plugin, then check each kapt dependency's jar for a services/com.google.devtools.ksp.processing.SymbolProcessorProvider file to confirm KSP compatibility. Migrate compatible processors to KSP and apply the com.android.legacy-kapt plugin for any that are incompatible.

Does AGP 9 support Kotlin Multiplatform projects?▼

No, this migration path does not support Kotlin Multiplatform (KMP) projects. The skill explicitly excludes KMP projects and should not be used to migrate them to AGP 9.

Why does Paparazzi fail after upgrading to AGP 9?▼

Paparazzi 2.0.0-alpha04 and lower use internal Gradle classes that break with Gradle 9, which AGP 9 requires. The workaround is to disable HTML test reports by setting reports.html.required = false on Test tasks in every module applying the Paparazzi plugin.

What gradle.properties flags should be removed after AGP 9 migration?▼

Remove android.builtInKotlin, android.newDsl, android.uniquePackageNames, and android.enableAppCompileTimeRClass from gradle.properties after the migration. These flags are no longer needed once the project is fully on AGP 9.