Skip to content

Commit 7bd99b0

Browse files
authored
Updating the Android deployment page (#13242)
Fixes #12137
1 parent 8a3305c commit 7bd99b0

1 file changed

Lines changed: 23 additions & 8 deletions

File tree

src/content/deployment/android.md

Lines changed: 23 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -27,9 +27,9 @@ This guide explains how to perform the following tasks:
2727

2828
:::note
2929
Throughout this page, `[project]` refers to
30-
the directory that your application is in. While following
31-
these instructions, substitute `[project]` with
32-
your app's directory.
30+
the directory that contains your application.
31+
While following these instructions,
32+
substitute `[project]` with your app's directory.
3333
:::
3434

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

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

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

6363
[flutter_launcher_icons]: {{site.pub}}/packages/flutter_launcher_icons
6464
[launchericons]: {{site.material}}/styles/icons
65-
[configuration qualifiers]: {{site.android-dev}}/guide/topics/resources/providing-resources#AlternativeResources
65+
[config-qual]: {{site.android-dev}}/guide/topics/resources/providing-resources#AlternativeResources
6666
[applicationtag]: {{site.android-dev}}/guide/topics/manifest/application-element
6767

6868
## Enable Material Components
@@ -123,7 +123,7 @@ dependencies {
123123
<a id="signing-the-app"></a>
124124
## Sign the app
125125

126-
To publish on the Play Store, you need to
126+
To publish on the Play Store, you must
127127
sign your app with a digital certificate.
128128

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

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

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

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

190190
### Reference the keystore from the app
191191

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

495+
If you update the `applicationId` and `namespace` properties,
496+
you must also update the `package` statement in your `MainActivity.kt`
497+
or `MainActivity.java` file and move the file
498+
to the corresponding directory structure.
499+
500+
For example:
501+
502+
- In Kotlin, if your new ID is `com.example.myapp`,
503+
move your `MainActivity` file to
504+
`android/app/src/main/kotlin/com/example/myapp/MainActivity.kt`
505+
and ensure the first line is `package com.example.myapp`.
506+
- In Java, move your `MainActivity` file to
507+
`android/app/src/main/java/com/example/myapp/MainActivity.java`
508+
and ensure the first line is `package com.example.myapp`.
509+
495510
[application-id]: {{site.android-dev}}/studio/build/application-id
496511

497512
### Android SDK versions

0 commit comments

Comments
 (0)