Skip to content

Updating the Android deployment page #13242

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
sfshaza2 wants to merge 1 commit into
base: main
Choose a base branch
from
+17 −8
Open

Updating the Android deployment page #13242

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
25 changes: 17 additions & 8 deletions src/content/deployment/android.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -27,9 +27,9 @@ This guide explains how to perform the following tasks:

:::note
Throughout this page, `[project]` refers to
the directory that your application is in. While following
these instructions, substitute `[project]` with
your app's directory.
the directory that contains your application.
While following these instructions,
substitute `[project]` with your app's directory.
:::

[play]: {{site.android-dev}}/distribute
Expand All @@ -47,7 +47,7 @@ Alternatively, you can do it manually using the following steps:

1. In the `[project]/android/app/src/main/res/` directory,
place your icon files in folders named using
[configuration qualifiers][].
[configuration qualifiers][config-qual].
The default `mipmap-` folders demonstrate the correct
naming convention.

Expand All @@ -62,7 +62,7 @@ Alternatively, you can do it manually using the following steps:

[flutter_launcher_icons]: {{site.pub}}/packages/flutter_launcher_icons
[launchericons]: {{site.material}}/styles/icons
[configuration qualifiers]: {{site.android-dev}}/guide/topics/resources/providing-resources#AlternativeResources
[config qual]: {{site.android-dev}}/guide/topics/resources/providing-resources#AlternativeResources
Copy link
Copy Markdown
Contributor

@gemini-code-assist gemini-code-assist bot Apr 1, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

The link reference label [config qual] does not match the identifier [config-qual] used on line 50. Markdown link references must match exactly (including spaces and hyphens) to resolve correctly.

Suggested change
[config qual]: {{site.android-dev}}/guide/topics/resources/providing-resources#AlternativeResources
[config-qual]: {{site.android-dev}}/guide/topics/resources/providing-resources#AlternativeResources

[applicationtag]: {{site.android-dev}}/guide/topics/manifest/application-element

## Enable Material Components
Expand Down Expand Up @@ -123,7 +123,7 @@ dependencies {
<a id="signing-the-app"></a>
## Sign the app

To publish on the Play Store, you need to
To publish on the Play Store, you must
sign your app with a digital certificate.

Android uses two signing keys: _upload_ and _app signing_.
Expand All @@ -144,7 +144,7 @@ To sign your app, use the following instructions.
If you have an existing keystore, skip to the next step.
If not, create one using one of the following methods:

1. Follow the [Android Studio key generation steps][].
1. Follow the [Android Studio key generation steps][as-key-steps].
1. Run the following command at the command line:

On macOS or Linux, use the following command:
Expand Down Expand Up @@ -185,7 +185,7 @@ If not, create one using one of the following methods:
the keystore type defaults to PKS12.
:::

[Android Studio key generation steps]: {{site.android-dev}}/studio/publish/app-signing#generate-key
[as-key-steps]: {{site.android-dev}}/studio/publish/app-signing#generate-key

### Reference the keystore from the app

Expand Down Expand Up @@ -492,6 +492,15 @@ Typically, this is a reverse domain name, such as `com.example.myapp`.
Once you upload your app to the Play Store, you cannot change the Application ID.
:::

If you update the `applicationId` and `namespace` properties,
you must also update the `package` statement in your `MainActivity.kt`
or `MainActivity.java` file and move the file
to the corresponding directory structure.
For example, if your new ID is `com.example.myapp`,
move your `MainActivity` file to
`android/app/src/main/kotlin/com/example/myapp/MainActivity.kt`
and ensure the first line is `package com.example.myapp`.
Comment on lines +499 to +502
Copy link
Copy Markdown
Contributor

@gemini-code-assist gemini-code-assist bot Apr 1, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

Since the instructions mention both Kotlin and Java files, it's helpful to provide the example path for both languages to ensure clarity for all users.

Suggested change
For example, if your new ID is `com.example.myapp`,
move your `MainActivity` file to
`android/app/src/main/kotlin/com/example/myapp/MainActivity.kt`
and ensure the first line is `package com.example.myapp`.
For example, if your new ID is com.example.myapp,
move your MainActivity file to
android/app/src/main/kotlin/com/example/myapp/MainActivity.kt
(or android/app/src/main/java/com/example/myapp/MainActivity.java)
and ensure the first line is package com.example.myapp.


[application-id]: {{site.android-dev}}/studio/build/application-id

### Android SDK versions
Expand Down
Loading