Skip to content

Commit d05c398

Browse files
ConnorLandConnorLand
committed
Duplicate updates to Mx10 and Mx9 docs
1 parent ba614d8 commit d05c398

File tree

3 files changed

+64
-95
lines changed

3 files changed

+64
-95
lines changed

‎content/en/docs/refguide/mobile/distributing-mobile-apps/distributing-native-apps.md

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -95,7 +95,6 @@ To generate a keystore for Android, follow these steps:
9595
9696
6. Finishing these questions generates a keystore which will be saved into a *file.keystore* file in your current working directory.
9797
98-
9998
## Building a Release App {#building-release}
10099
101100
Once your signing credentials are ready, you can build the signed release version of your app using Xcode (for iOS) or Android Studio (for Android).

‎content/en/docs/refguide10/mobile/distributing-mobile-apps/distributing-native-apps.md

Lines changed: 32 additions & 47 deletions
Original file line numberDiff line numberDiff line change
@@ -95,78 +95,63 @@ To generate a keystore for Android, follow these steps:
9595
9696
6. Finishing these questions generates a keystore which will be saved into a *file.keystore* file in your current working directory.
9797
98-
9998
## Building a Release App {#building-release}
10099
101100
Once your signing credentials are ready, you can build the signed release version of your app using Xcode (for iOS) or Android Studio (for Android).
102101
103102
### iOS (Xcode)
104103
105-
1. Open your project in Xcode (this can be generated by Mendix Native Builder).
106-
107-
2. In the project navigator, select your app target.
108-
109-
3. Go to the Signing & Capabilities tab and ensure your team and provisioning profile are set.
110-
111-
4. Choose Any iOS Device (arm64) in the device target dropdown.
112-
113-
5. Go to the Product menu and select Archive.
114-
115-
6. When the archive is complete, the Organizer window will open.
104+
To build your iOS app in Xcode, do the following:
116105
117-
7. From there, you can export the .ipa file by selecting Distribute App > App Store Connect or Ad Hoc, depending on your goal.
106+
1. Open your project in Xcode (this can be generated by the Mendix Native Builder).
107+
1. In the project navigator, select your app target.
108+
1. Go to the **Signing & Capabilities** tab and ensure your team and provisioning profile are set.
109+
1. Choose **Any iOS Device (arm64)** in the device target dropdown.
110+
1. Go to the **Product** menu and select **Archive**.
111+
1. When the archive is complete, the **Organizer** window will open.
112+
1. From there, you can export the *.ipa* file by selecting **Distribute App** > **App Store Connect** or **Ad Hoc**, depending on your goal.
113+
1. Follow the steps to export the *.ipa* file or upload it directly to App Store Connect
118114
119-
8. Follow the steps to export the .ipa file or upload it directly to App Store Connect.
120-
121-
The exported .ipa file can typically be found under:
122-
123-
`"~/Library/Developer/Xcode/Archives/<DATE>/<YourApp>.xcarchive"`
115+
Once you finish the final step, the exported *.ipa* file is usually located under `"~/Library/Developer/Xcode/Archives/DATE/YOUR-APP.xcarchive"` (with the publish date and name of your app instead of DATE and YOUR-APP).
124116
125117
### Android (Android Studio)
126118
127-
1. Open the android directory of your Mendix Native project in Android Studio.
128-
129-
2. Select Build > Generate Signed Bundle / APK from the top menu.
130-
131-
3. Choose APK or Android App Bundle (AAB).
132-
133-
4. Follow the wizard and choose your keystore file, alias, and password.
119+
To build an Android app in Android Studio, do the following:
134120
135-
5. Select release as the build variant.
121+
1. Open the android directory of your Mendix Native project in Android Studio.
122+
1. Select **Build** > **Generate Signed Bundle / APK** from the top menu.
123+
1. Choose **APK** or **Android App Bundle (AAB)**.
124+
1. Follow the wizard and choose your keystore file, alias, and password.
125+
1. Select release as the build variant.
126+
1. Complete the wizard and wait for Android Studio to build the release file.
136127
137-
6. Complete the wizard and wait for Android Studio to build the release file.
128+
Once you finish the final step, the output *.apk* or *.aab* file will be located in one of two places (with the name of your project instead of YOUR-PROJECT):
138129
139-
The output .apk or .aab file will be located in:
140-
`"<your-project>/android/app/build/outputs/apk/release/app-release.apk"`
141-
or
142-
`"~<your-project>/android/app/build/outputs/bundle/release/app-release.aab"`
130+
* `"YOUR-PROJECT/android/app/build/outputs/apk/release/app-release.apk"`
131+
* `"~YOUR-PROJECT/android/app/build/outputs/bundle/release/app-release.aab"`
143132
144133
## Publishing to App Stores {#publishing}
145134
146135
### iOS – App Store Connect
147136
148-
1. Log into App Store Connect.
149-
150-
2. Create a new app record if this is your first time submitting.
137+
To publish in the iOS App Store, do the following:
151138
152-
3. Upload the .ipa file directly from Xcode or by using Transporter (a free tool from Apple).
153-
154-
4. Fill in all required metadata, screenshots, and compliance information.
155-
156-
5. Submit your app for review.
139+
1. Log into App Store Connect.
140+
1. Create a new app record if this is your first time submitting.
141+
1. Upload the *.ipa* file directly from Xcode or by using Transporter (a free tool from Apple).
142+
1. Fill in all required metadata, screenshots, and compliance information.
143+
1. Submit your app for review.
157144
158145
Make sure your Apple Developer Account is active and the app has passed validation before submission.
159146
160147
### Android – Google Play Console
161148
162-
1. Go to the Google Play Console.
163-
164-
2. Create a new application and fill in the store listing information.
165-
166-
3. Navigate to the Release > Production > Create Release section.
149+
To publish in the Android Google Play Console, do the following:
167150
168-
4. Upload your signed .apk or .aab file.
169-
170-
5. Review and roll out your release to production.
151+
1. Go to the Google Play Console.
152+
1. Create a new application and fill in the store listing information.
153+
1. Navigate to the **Release** > **Production** > **Create Release section**.
154+
1. Upload your signed *.apk* or *.aab* file.
155+
1. Review and roll out your release to production.
171156
172157
Be sure to enroll in Google Play App Signing if you plan to use AAB files. Also, don’t forget to set up content rating, privacy policies, and testing tracks if needed.

‎content/en/docs/refguide9/mobile/distributing-mobile-apps/distributing-native-apps.md

Lines changed: 32 additions & 47 deletions
Original file line numberDiff line numberDiff line change
@@ -95,78 +95,63 @@ To generate a keystore for Android, follow these steps:
9595
9696
6. Finishing these questions generates a keystore which will be saved into a *file.keystore* file in your current working directory.
9797
98-
9998
## Building a Release App {#building-release}
10099
101100
Once your signing credentials are ready, you can build the signed release version of your app using Xcode (for iOS) or Android Studio (for Android).
102101
103102
### iOS (Xcode)
104103
105-
1. Open your project in Xcode (this can be generated by Mendix Native Builder).
106-
107-
2. In the project navigator, select your app target.
108-
109-
3. Go to the Signing & Capabilities tab and ensure your team and provisioning profile are set.
110-
111-
4. Choose Any iOS Device (arm64) in the device target dropdown.
112-
113-
5. Go to the Product menu and select Archive.
114-
115-
6. When the archive is complete, the Organizer window will open.
104+
To build your iOS app in Xcode, do the following:
116105
117-
7. From there, you can export the .ipa file by selecting Distribute App > App Store Connect or Ad Hoc, depending on your goal.
106+
1. Open your project in Xcode (this can be generated by the Mendix Native Builder).
107+
1. In the project navigator, select your app target.
108+
1. Go to the **Signing & Capabilities** tab and ensure your team and provisioning profile are set.
109+
1. Choose **Any iOS Device (arm64)** in the device target dropdown.
110+
1. Go to the **Product** menu and select **Archive**.
111+
1. When the archive is complete, the **Organizer** window will open.
112+
1. From there, you can export the *.ipa* file by selecting **Distribute App** > **App Store Connect** or **Ad Hoc**, depending on your goal.
113+
1. Follow the steps to export the *.ipa* file or upload it directly to App Store Connect
118114
119-
8. Follow the steps to export the .ipa file or upload it directly to App Store Connect.
120-
121-
The exported .ipa file can typically be found under:
122-
123-
`"~/Library/Developer/Xcode/Archives/<DATE>/<YourApp>.xcarchive"`
115+
Once you finish the final step, the exported *.ipa* file is usually located under `"~/Library/Developer/Xcode/Archives/DATE/YOUR-APP.xcarchive"` (with the publish date and name of your app instead of DATE and YOUR-APP).
124116
125117
### Android (Android Studio)
126118
127-
1. Open the android directory of your Mendix Native project in Android Studio.
128-
129-
2. Select Build > Generate Signed Bundle / APK from the top menu.
130-
131-
3. Choose APK or Android App Bundle (AAB).
132-
133-
4. Follow the wizard and choose your keystore file, alias, and password.
119+
To build an Android app in Android Studio, do the following:
134120
135-
5. Select release as the build variant.
121+
1. Open the android directory of your Mendix Native project in Android Studio.
122+
1. Select **Build** > **Generate Signed Bundle / APK** from the top menu.
123+
1. Choose **APK** or **Android App Bundle (AAB)**.
124+
1. Follow the wizard and choose your keystore file, alias, and password.
125+
1. Select release as the build variant.
126+
1. Complete the wizard and wait for Android Studio to build the release file.
136127
137-
6. Complete the wizard and wait for Android Studio to build the release file.
128+
Once you finish the final step, the output *.apk* or *.aab* file will be located in one of two places (with the name of your project instead of YOUR-PROJECT):
138129
139-
The output .apk or .aab file will be located in:
140-
`"<your-project>/android/app/build/outputs/apk/release/app-release.apk"`
141-
or
142-
`"~<your-project>/android/app/build/outputs/bundle/release/app-release.aab"`
130+
* `"YOUR-PROJECT/android/app/build/outputs/apk/release/app-release.apk"`
131+
* `"~YOUR-PROJECT/android/app/build/outputs/bundle/release/app-release.aab"`
143132
144133
## Publishing to App Stores {#publishing}
145134
146135
### iOS – App Store Connect
147136
148-
1. Log into App Store Connect.
149-
150-
2. Create a new app record if this is your first time submitting.
137+
To publish in the iOS App Store, do the following:
151138
152-
3. Upload the .ipa file directly from Xcode or by using Transporter (a free tool from Apple).
153-
154-
4. Fill in all required metadata, screenshots, and compliance information.
155-
156-
5. Submit your app for review.
139+
1. Log into App Store Connect.
140+
1. Create a new app record if this is your first time submitting.
141+
1. Upload the *.ipa* file directly from Xcode or by using Transporter (a free tool from Apple).
142+
1. Fill in all required metadata, screenshots, and compliance information.
143+
1. Submit your app for review.
157144
158145
Make sure your Apple Developer Account is active and the app has passed validation before submission.
159146
160147
### Android – Google Play Console
161148
162-
1. Go to the Google Play Console.
163-
164-
2. Create a new application and fill in the store listing information.
165-
166-
3. Navigate to the Release > Production > Create Release section.
149+
To publish in the Android Google Play Console, do the following:
167150
168-
4. Upload your signed .apk or .aab file.
169-
170-
5. Review and roll out your release to production.
151+
1. Go to the Google Play Console.
152+
1. Create a new application and fill in the store listing information.
153+
1. Navigate to the **Release** > **Production** > **Create Release section**.
154+
1. Upload your signed *.apk* or *.aab* file.
155+
1. Review and roll out your release to production.
171156
172157
Be sure to enroll in Google Play App Signing if you plan to use AAB files. Also, don’t forget to set up content rating, privacy policies, and testing tracks if needed.

0 commit comments

Comments
 (0)