updated: AGP 9 project migration guide #530

zamulla · 2025-10-14T09:49:46Z

No description provided.

ElviraMustafina · 2025-10-17T14:30:41Z

mpd.tree

 		<toc-element toc-title="Basic project structure" topic="multiplatform-discover-project.md"/>
 		<toc-element toc-title="Advanced project structure" topic="multiplatform-advanced-project-structure.md"/>
 		<toc-element toc-title="Project configuration options" topic="multiplatform-project-configuration.md"/>
+        <toc-element toc-title="Project configuration options" topic="multiplatform-project-agp-9-migration.md"/>


Wrong toc-title

ElviraMustafina · 2025-10-17T14:34:57Z

topics/development/multiplatform-project-agp-9-migration.md

+      You can remove old run configurations associated with the `composeApp` module.
+2. In the `gradle/libs.versions.toml` file, update the AGP version to a 9.* version, for example:
+
+    ```txt


"CDE016: Unknown language is specified for a code block"
Let's try toml or text

ElviraMustafina · 2025-10-17T15:12:32Z

topics/development/multiplatform-project-agp-9-migration.md

+         // ...
+       }
+       ```
+    4. In the `kotlin {}` block, specify the targets that the common module should support in this example:


The previous step is for the root build.gradle.kts file, specify the file with the kotlin {} block

ElviraMustafina · 2025-10-17T15:25:34Z

topics/development/multiplatform-project-agp-9-migration.md

+> To do that, in the `gradle.properties` file of your project add this property:
+> `android.enableLegacyVariantApi=true`.


Suggested change

> To do that, in the `gradle.properties` file of your project add this property:

> `android.enableLegacyVariantApi=true`.

> To do this, add the following property to the `gradle.properties` file:

> `android.enableLegacyVariantApi=true`.

ElviraMustafina · 2025-10-17T15:38:54Z

topics/development/multiplatform-project-agp-9-migration.md

+Before actually creating a module, you need to decide on what is business logic, which code is both UI- and
+platform-independent.


Suggested change

Before actually creating a module, you need to decide on what is business logic, which code is both UI- and

platform-independent.

Before creating a module, you need to identify the code for business logic that is both UI- and platform-independent.

ElviraMustafina · 2025-10-17T16:33:20Z

topics/development/multiplatform-project-agp-9-migration.md

+### Update the iOS integration
+
+Since the iOS app entry point is not built as a separate Gradle module, you can embed the source code into any module.
+In this example, `sharedUi` makes most sense:


Suggested change

In this example, `sharedUi` makes most sense:

In this example, `sharedUi` makes the most sense:

ElviraMustafina · 2025-10-17T16:36:04Z

topics/development/multiplatform-project-agp-9-migration.md

+
+### Remove `composeApp` and update the Android Gradle plugin version
+
+When all code is working from correct new modules:


Suggested change

When all code is working from correct new modules:

Once all code works correctly from the new modules:

ElviraMustafina · 2025-10-17T16:36:30Z

topics/development/multiplatform-project-agp-9-migration.md

+
+1. Remove the old module completely:
+   1. Remove the `composeApp` dependency from the `settings.gradle.kts` file (the line `include(":composeApp")`).
+   2. Remove the `composeApp` directory entirely.


Suggested change

2. Remove the `composeApp` directory entirely.

2. Delete the `composeApp` directory entirely.

ElviraMustafina · 2025-10-17T16:37:32Z

topics/development/multiplatform-project-agp-9-migration.md

+
+4. That your apps build and run with the new AGP.
+
+Congratulations, you modernized and optimized the structure of your project!


🎉

Suggested change

Congratulations, you modernized and optimized the structure of your project!

Congratulations! You have modernized and optimized the structure of your project.

ElviraMustafina · 2025-10-17T16:44:18Z

topics/development/multiplatform-project-agp-9-migration.md

+        kotlin {
+            // ...
+            androidLibrary {
+                namespace = "com.jetbrains.greeting.demo.sharedLogic"


Should it be sharedUi?

ElviraMustafina · 2025-10-17T21:40:53Z

The guide is long and intimidating, with repetitive steps for each platform. What do you think about adding a section with general steps for creating a module? This would help identify common patterns upfront and allow us to make repetitive steps collapsible.

ElviraMustafina · 2025-10-20T13:48:36Z

mpd.tree

 		<toc-element toc-title="Basic project structure" topic="multiplatform-discover-project.md"/>
 		<toc-element toc-title="Advanced project structure" topic="multiplatform-advanced-project-structure.md"/>
 		<toc-element toc-title="Project configuration options" topic="multiplatform-project-configuration.md"/>
+        <toc-element toc-title="Project configuration options" topic="multiplatform-project-agp-9-migration.md"/>


Also, I'm not sure if this guide will be discoverable under "Explore project structure"

evilya · 2025-10-30T12:10:28Z

topics/compose-onboard/compose-multiplatform-new-project.md


    ```kotlin
-    fun currentTimeAt(location: String): String? {
+   @OptIn(ExperimentalTime::class) 


could we add opt-in on a project level?

evilya · 2025-10-30T12:16:32Z

topics/development/multiplatform-project-agp-9-migration.md

+Kotlin Multiplatform projects with Android targets which were created using the Android Gradle plugin version earlier
+than 9.0
+need to be restructured to upgrade to AGP 9.0.
+Several APIs needed for KMP configuration are hidden in AGP 9.0 and eventually are going to be removed.


Is it publicly communicated/documented? It would be nice to provide a link to outline a rough timeline

evilya · 2025-10-30T12:18:46Z

topics/development/multiplatform-project-agp-9-migration.md

+than 9.0
+need to be restructured to upgrade to AGP 9.0.
+Several APIs needed for KMP configuration are hidden in AGP 9.0 and eventually are going to be removed.
+To solve this in the long term, we recommend updating your project structure to isolate AGP usage to an Android module.


Hmm, it's not entirely correct. Library-AGP is still going to be used in a shared module, but Application-AGP will be isolated in an Android module. I'm not sure if there's established terminology for distinguishing between these two types of AGPs

evilya · 2025-10-30T12:21:35Z

topics/development/multiplatform-project-agp-9-migration.md

+The example project is a Compose Multiplatform app that is the result of the [](compose-multiplatform-new-project.md)
+tutorial.
+You can check out the initial state of the project in
+the [update_october_2025 branch](https://github.com/kotlin-hands-on/get-started-with-cm/tree/update_october_2025)


It's a temporary branch that I was planning to delete 😅 should we create a new one with more meaningful name?

evilya · 2025-10-30T12:26:59Z

topics/development/multiplatform-project-agp-9-migration.md

+* Isolate the Android module (that uses the `androidApplication` Gradle plugin) from KMP modules (that use the
+  `androidLibrary`
+  Gradle plugin).


Could we explicitly state somewhere at the beginning that the goal for this migration is to not use com.android.application and org.jetbrains.kotlin.multiplatform in the same module? Maybe even before describing workaround with android.enableLegacyVariantApi=true, so people would know if they even need to migrate

evilya · 2025-10-30T12:40:14Z

topics/development/multiplatform-project-agp-9-migration.md

+You have isolated the shared logic in a separate module and successfully used it cross-platform.
+Next step, creating a shared UI module.
+
+<!-- TODO Platform.kt may be a good example of migrating expect-actuals, but are they still there in the sample we're using?


Good catch, it's not used in the sample app. We either need to come up with a better example for expect/actual usage in this particular sample or just keep it more generic without mentioning Platform class and related methods

evilya · 2025-10-30T12:47:02Z

topics/development/multiplatform-project-agp-9-migration.md

+           sourceSets {
+               commonMain.dependencies { 
+                   implementation(projects.sharedLogic)
+                   implementation(compose.runtime)


We're going to get rid of dependency aliases in CMP, so this block will change by the time of release. I'll let you know what it's going to look like

zamulla added 5 commits October 7, 2025 16:13

update: initial for AGP 9 migration

6e5caee

update: basic structure of the page

3d6528d

update: first modules detailed

32cebc0

update: done with the bulk of instructions

5128e23

update: done, with a couple of todos left up to discussion

e03b11f

zamulla assigned ElviraMustafina Oct 14, 2025

zamulla requested a review from a team as a code owner October 14, 2025 09:49

ElviraMustafina requested changes Oct 17, 2025

View reviewed changes

zamulla requested a review from evilya October 20, 2025 11:49

ElviraMustafina reviewed Oct 20, 2025

View reviewed changes

evilya reviewed Nov 3, 2025

View reviewed changes

zamulla added 2 commits November 4, 2025 12:20

update: change the focus of the intro a little

dd65d31

fix: preciser

8fb0d15

		> To do that, in the `gradle.properties` file of your project add this property:
		> `android.enableLegacyVariantApi=true`.

		Before actually creating a module, you need to decide on what is business logic, which code is both UI- and
		platform-independent.

	Before actually creating a module, you need to decide on what is business logic, which code is both UI- and
	platform-independent.
	Before creating a module, you need to identify the code for business logic that is both UI- and platform-independent.

	In this example, `sharedUi` makes most sense:
	In this example, `sharedUi` makes the most sense:


		### Remove `composeApp` and update the Android Gradle plugin version

		When all code is working from correct new modules:

	When all code is working from correct new modules:
	Once all code works correctly from the new modules:

	2. Remove the `composeApp` directory entirely.
	2. Delete the `composeApp` directory entirely.


		4. That your apps build and run with the new AGP.

		Congratulations, you modernized and optimized the structure of your project!

	Congratulations, you modernized and optimized the structure of your project!
	Congratulations! You have modernized and optimized the structure of your project.

updated: AGP 9 project migration guide #530

Are you sure you want to change the base?

updated: AGP 9 project migration guide #530

Conversation

zamulla commented Oct 14, 2025

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

ElviraMustafina commented Oct 17, 2025

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

4 participants