kotlin-tooling-agp9-migration

To migrate a Kotlin Multiplatform project to Android Gradle Plugin 9.0, you must replace incompatible plugins and restructure modules to enforce a strict separation between Android application and library components.

Your KMP build fails after upgrading to AGP 9.0 because the new plugin enforces strict architectural separation, requiring monolithic application modules to be split into separate Android app and KMP library components.

Splitting a monolithic composeApp module for AGP 9.0 involves extracting the Android entry point into a dedicated application module while preserving shared business logic inside a separate KMP library component.

You can update deprecated Android DSL elements by referencing a comprehensive mapping that transitions old syntax to the new KMP-integrated configuration required for built-in Kotlin support.

Yes, you must separate Android app and library plugins for KMP in AGP 9.0 because the update enforces a strict architectural separation that makes monolithic application modules incompatible.

Correct source set configuration when upgrading KMP modules to AGP 9.0 requires restructuring modules to satisfy built-in Kotlin support and updated DSL syntax across separated Android app and KMP library components.