updated: AGP 9 project migration guide #530
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
ElviraMustafina
requested changes
Oct 17, 2025
| <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"/> |
| 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 |
There was a problem hiding this comment.
"CDE016: Unknown language is specified for a code block"
Let's try toml or text
| // ... | ||
| } | ||
| ``` | ||
| 4. In the `kotlin {}` block, specify the targets that the common module should support in this example: |
There was a problem hiding this comment.
The previous step is for the root build.gradle.kts file, specify the file with the kotlin {} block
Comment on lines
+14
to
+15
| > To do that, in the `gradle.properties` file of your project add this property: | ||
| > `android.enableLegacyVariantApi=true`. |
There was a problem hiding this comment.
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`. |
Comment on lines
+60
to
+61
| Before actually creating a module, you need to decide on what is business logic, which code is both UI- and | ||
| platform-independent. |
There was a problem hiding this comment.
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. |
| ### 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: |
There was a problem hiding this comment.
Suggested change
| 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: |
There was a problem hiding this comment.
Suggested change
| When all code is working from correct new modules: | |
| Once all code works correctly from the new modules: |
| 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. |
There was a problem hiding this comment.
Suggested change
| 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! |
There was a problem hiding this comment.
🎉
Suggested change
| Congratulations, you modernized and optimized the structure of your project! | |
| Congratulations! You have modernized and optimized the structure of your project. |
| kotlin { | ||
| // ... | ||
| androidLibrary { | ||
| namespace = "com.jetbrains.greeting.demo.sharedLogic" |
There was a problem hiding this comment.
Should it be sharedUi?
|
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. |
| <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"/> |
There was a problem hiding this comment.
Also, I'm not sure if this guide will be discoverable under "Explore project structure"
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.