Duplicate changes

content/en/docs/howto10/extensibility/build-javascript-actions/create-native-javascript-action.md

@@ -315,11 +315,11 @@ Congratulations on making your own native JavaScript action! Please use your own
 
 Until this section, you have used a custom developer app to validate your application. When you want to distribute your app in the Google Play Store or Apple App Store, you have to make a build that includes the bundled Mendix app.
 
-For the full explanation on how to build, sign, and distribute your app to an app store see [Build a Mendix Native App in the Cloud](/refguide10/mobile/distributing-mobile-apps/building-native-apps/deploying-native-app/), as well as the tutorial's subsequent sections.
+For the full explanation on how to build, sign, and distribute your app to an app store see [Building, Testing, and Distributing Apps](/refguide10/mobile/distributing-mobile-apps/).
 
 ## Read More
 
-* [How to Build a Mendix Native App in the Cloud](/refguide10/mobile/distributing-mobile-apps/building-native-apps/deploying-native-app/)
+* [Building, Testing, and Distributing Apps](/refguide10/mobile/distributing-mobile-apps/)
 * [JavaScript Actions Reference Guide](/refguide10/javascript-actions/)
 * [How To Build JavaScript actions](/howto10/extensibility/build-javascript-actions/)
 * [Declaring Native Dependencies](/apidocs-mxsdk/apidocs/pluggable-widgets-native-dependencies/)

content/en/docs/refguide10/mobile/building-efficient-mobile-apps/logging.md

@@ -78,7 +78,6 @@ The following log nodes are used by Mendix when writing log messages:
 
 | Log Node | Description |
 | --- | --- |
-| Client_AppCenter| Logs messages related to the state and phases of over-the-air updates by App Center. |
 | Client_Auth | Logs messages related to the different authentication states and user actions.|
 | Client | The default log node when no log node is provided. |
 | Client_Database | Logs messages related to different read/write operations on the local database. |

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

@@ -17,9 +17,6 @@ Many of these guides use the Mendix Native Mobile Builder UI tool included in Me
 
 * [Build a Mendix Native App Locally](/refguide10/mobile/distributing-mobile-apps/building-native-apps/native-build-locally/) – Follow this guide to build your apps locally using the Mendix Native Mobile Builder.
 * [Build a Mendix Native App Locally Manually](/refguide10/mobile/distributing-mobile-apps/building-native-apps/native-build-locally-manually/) – Follow this guide to build your apps locally and without an internet connection.
-{{% alert color="warning" %}}
-Building mobile apps with App Center is deprecated and will be removed on March 30, 2025. Learn more about the new and improved ways to build mobile apps with Bitrise in [our documentation](/refguide10/mobile/distributing-mobile-apps/building-native-apps/bitrise/).
-{{% /alert %}}
 * [Build a Mendix Native App in the Cloud](/refguide10/mobile/distributing-mobile-apps/building-native-apps/deploying-native-app/) – Go from a blank slate to an app running on a device.
 * [Create a Custom Developer App](/refguide10/mobile/distributing-mobile-apps/building-native-apps/how-to-devapps/) – Create a custom developer app (a substitute for the Make It Native app) which accommodates custom dependencies such as native widgets or fonts.
 * [Native Template](/refguide10/mobile/distributing-mobile-apps/building-native-apps/native-template/) – The Native Template describes the native dependencies your app needs, and it includes two native apps (one for iOS and one for Android) that can be independently built to create the finished apps.

content/en/docs/refguide10/mobile/distributing-mobile-apps/building-native-apps/how-to-devapps.md

@@ -36,7 +36,7 @@ A custom developer app helps you by serving as a replacement for the Make It Nat
 
 1. Click the *Build developer app* button
 
-1. The tool will set up your GitHub repository commit your changes, configure App Center if needed with two new apps, one for iOS and one for Android and continue with building the apps.
+1. The tool will set up your GitHub repository, commit your changes, and continue with building the apps:
 
     {{< figure src="/attachments/howto10/mobile/native-mobile/distribution/build-native-apps/deploying-native-app/build-release-app-build-step1.png" alt="Building"   width="350"  class="no-border" >}}{{< figure src="/attachments/howto10/mobile/native-mobile/distribution/build-native-apps/deploying-native-app/build-release-app-build-step1.png" alt="Building"   width="350"  class="no-border" >}}
     {{< figure src="/attachments/howto10/mobile/native-mobile/distribution/build-native-apps/deploying-native-app/build-release-app-build-step2.png" alt="Build release app" width="350" class="no-border" >}}

content/en/docs/refguide10/mobile/distributing-mobile-apps/building-native-apps/native-build-locally.md

@@ -49,7 +49,7 @@ To set up your local app, do the following:
 1. In the **Build type** make sure the **Local** option is selected. 
     {{< figure src="/attachments/howto10/mobile/native-mobile/distribution/build-native-apps/native-build-locally/wizard-buildtype-local.png" alt="Build type"   width="350"  class="no-border" >}}
 1. Select the folder for your app's Native Template. Valid choices are an empty directory or a directory with an existing Native Template.
-1. Disable any service you do not wish to use. App Center requires GitHub as a service to work.
+1. Disable the GitHub service if you do not wish to use it. 
 1. Click **Next Step** until you reach the end of the wizard. Feel free to configure any step as needed.  
 1. Select **Build type** from the side bar. 
 

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

@@ -650,8 +650,7 @@ A CI environment needs to be able to do the following to successfully configure
 * Set up the configuration and move assets as needed (this can be done with simple shell scripts or any other solution, and is the implementer's choice) 
 * Run `npm i` and `npm run configure` to configure the app using Mendix Mobile Toolkit before the build.
 
-How to build the apps is a choice for the implementer. Mendix Native App Builder use App Center for convenience. There are multiple other 
-solutions, on premise or as a service, that can be used for this purpose. We do not endorse one over the other.
+How to build the apps is a choice for the implementer. There are multiple solutions, on premise or as a service, that can be used for this purpose. We do not endorse one over the other.
 
 ## Read More
 

content/en/docs/refguide10/mobile/distributing-mobile-apps/use-min-older-sp.md

@@ -367,7 +367,7 @@ If using Native Builder UI (which also creates native apps to use for testing),
 1. In Studio Pro, click **App** > **Build Native Mobile App**.
 1. Click **Configure app for local building**.
 1. (Build type) Select a disk location for the native app source code.
-1. (Build type) Disable GitHub and App Center cloud services.
+1. (Build type) Disable GitHub.
 1. (Splash screens / App icon / Custom fonts) Use the default splash screen and app icons and no custom fonts (because we need the JavaScript bundle and project assets, this step isn't important but required).
 1. (App details) Select **Portrait** and **Landscape** for app's **orientation selection**.
 1. (App details) Select **Phones** and **Tablets** for app's **Device targets selection**.

content/en/docs/refguide10/mobile/getting-started-with-mobile/prerequisites.md

@@ -32,7 +32,7 @@ Native mobile apps are not run in the device browser like web-based Mendix apps.
 * **Build Native App**: For building native apps, we provide a tool called Build Native App. This tool must be configured and run each time a new build is created. Build Native App is not supported on Studio Pro for Mac. Build Native App updates itself automatically by downloading new versions from AWS.
 * **Native Template**: Build Native App needs to download the Native Template from [GitHub](https://github.com/mendix/native-template). This template contains the React Native project that is used to build the native app for iOS and Android.
 * **Dependencies**: The Native Template makes use of several open-source projects, including React Native. These must be downloaded from several external services including npm, gradle, and Cocoapods.
-* **Building**: Once prepared using Build Native App, the Native Template can be built for each target mobile operating system. Building can be done [locally](/refguide10/mobile/distributing-mobile-apps/building-native-apps/native-build-locally/) by downloading the mobile operating system's IDE or [remotely](/refguide10/mobile/distributing-mobile-apps/building-native-apps/deploying-native-app/) using a third-party continuous integration and delivery (CI/CD) platform. For building remotely, a [GitHub account](https://github.com/) and an [App Center account](https://appcenter.ms/) is required.
+* **Building**: Once prepared using Build Native App, the Native Template can be built for each target mobile operating system. Building can be done [locally](/refguide10/mobile/distributing-mobile-apps/building-native-apps/native-build-locally/) by downloading the mobile operating system's IDE or [remotely](/refguide10/mobile/distributing-mobile-apps/building-native-apps/bitrise/) using a third-party continuous integration and delivery (CI/CD) platform. For building remotely, a [GitHub account](https://github.com/) is required.
 * **Deploying**: Most mobile devices refuse to install APK/IPA files without additional steps. At minimum, the file must be signed to identify its developer and prevent manipulation. Furthermore, for iOS and recent versions of Android, the app must be published via the official mobile operating system's store or a mobile device management (MDM) system.
 * **Connectivity**: When running a Mendix native mobile app, it must connect to the Mendix Runtime at least once during startup. If no connection can be established, an error is shown. Connectivity is also needed to run microflows and to synchronize data.
 
@@ -50,7 +50,6 @@ For building:
 * Determine which native template version to download: `https://raw.githubusercontent.com/mendix/native-template/master/mendix_version.json`
 * Download the native template from GitHub: `https://github.com/mendix/native-template/archive/refs/tags/*.zip`
 * Upload the project to GitHub (optional): `https://api.github.com/`
-* Start App Center Pipeline (optional): `https://api.appcenter.ms/v0.1/`
 
 In some situations, it can be beneficial to designate a single machine for building native mobile apps or outsourcing the process to a partner.
 

content/en/docs/refguide10/mobile/using-mobile-capabilities/deep-links.md

@@ -33,7 +33,7 @@ Please note that the Make It Native app has already the registered schema `makei
 
 Before starting this guide, make sure you have completed the following prerequisites:
 
-* Complete the [Prerequisites](/refguide10/mobile/distributing-mobile-apps/building-native-apps/deploying-native-app/#prerequisites) section of *Build a Mendix Native App in the Cloud*
+* Complete the [Prerequisites](/refguide10/mobile/getting-started-with-mobile/prerequisites/) of your app per its type
 * Make sure your [Native Mobile Resources](/appstore/modules/native-mobile-resources/) module is up to date
 * Install Git [command line](https://git-scm.com/downloads) tool for working with the Native Mobile App Builder CLI
 * Install Mendix Studio Pro v 8.15.0 or above in order to use the Native Mobile App Builder

content/en/docs/refguide10/mobile/using-mobile-capabilities/generic-permission-action.md

@@ -11,7 +11,7 @@ Advanced features in mobile apps often require permission from users. Apps need
 
 ## Prerequisites
 
-* Complete the [Prerequisites](/refguide10/mobile/distributing-mobile-apps/building-native-apps/deploying-native-app/#prerequisites) section of *Build a Mendix Native App in the Cloud*.
+* Complete the [Prerequisites](/refguide10/mobile/getting-started-with-mobile/prerequisites/) of your app per its type
 * Install Mendix Studio Pro to use the Native Mobile App Builder and the latest Nanoflow Commons module.
 * Confirm your [Native Mobile Resources](/appstore/modules/native-mobile-resources/) module is up to date.
 * Confirm you are using the latest version of the [Make It Native 10 app](/releasenotes/mobile/make-it-native-parent/).

content/en/docs/refguide10/mobile/using-mobile-capabilities/local-notifications/native-local-notifications.md

@@ -22,7 +22,7 @@ Before starting this guide, make sure you have completed the following prerequis
 * Install the [Make It Native](/refguide10/getting-the-make-it-native-app/) app on your mobile device
 
 {{% alert color="info" %}}
-To use push notifications with apps created with the Native Builder, make sure you have completed [How To Build a Mendix Native App in the Cloud](/howto10/mobile/deploying-native-app/) and the guides described in [Push Notifications](/refguide10/mobile/using-mobile-capabilities/push-notifications/)
+To use push notifications with apps created with the Native Builder, make sure you have completed [Building Native Apps](/refguide10/mobile/distributing-mobile-apps/building-native-apps/) and the guides described in [Push Notifications](/refguide10/mobile/using-mobile-capabilities/push-notifications/)
 {{% /alert %}}
 
 ## Creating an App and Configuring Notifications

content/en/docs/refguide10/mobile/using-mobile-capabilities/location-and-maps.md

@@ -17,7 +17,7 @@ The Mendix Native Mobile Builder does not currently support connections behind p
 
 ## Prerequisites
 
-* Complete the [Prerequisites](/refguide10/mobile/distributing-mobile-apps/building-native-apps/deploying-native-app/#prerequisites) section of *Deploying Native Apps*
+* Complete the [Prerequisites](/refguide10/mobile/getting-started-with-mobile/prerequisites/) of your app per its type
 * Create an app on the [Google Cloud Console](https://console.cloud.google.com/google/maps-apis/overview) and have Google Maps enabled for Android (and iOS, if you wish to use Google Maps on iOS as well) and also posses an [API key](https://developers.google.com/maps/documentation/android-sdk/get-api-key). 
 * Before you can start using the Google Maps Platform APIs and SDKs, you must sign up and create a [billing account](https://developers.google.com/maps/gmp-get-started#create-billing-account).
 * Install Mendix Studio Pro 8.15.0 and above to use the Native Mobile App Builder

content/en/docs/refguide10/mobile/using-mobile-capabilities/mobile-accessibility.md

@@ -16,7 +16,7 @@ This guide only applies to native mobile apps.
 Before starting this guide, make sure you have completed the following prerequisites:
 
 * Install [Mendix Studio Pro](https://marketplace.mendix.com/link/studiopro/)
-* Complete the [Prerequisites](/refguide10/mobile/distributing-mobile-apps/building-native-apps/deploying-native-app/#prerequisites) section of *Build a Mendix Native App in the Cloud*
+* Complete the [Prerequisites](/refguide10/mobile/getting-started-with-mobile/prerequisites/) of your app per its type
 * Make sure you are using [Make It Native 9 app](/releasenotes/mobile/make-it-native-parent/)
 
 ## Setting Up Accessibility for Mendix Native Widgets

content/en/docs/refguide10/mobile/using-mobile-capabilities/native-language-change.md

@@ -19,7 +19,7 @@ While this guide gives your end-user the ability to switch their app's language,
 Before starting this guide, make sure you have completed the following prerequisites:
 
 * Install Mendix Studio Pro version [9.14.0](/releasenotes/studio-pro/9.14/) or above
-* Complete the [Prerequisites](/refguide10/mobile/distributing-mobile-apps/building-native-apps/deploying-native-app/#prerequisites) section of *Build a Mendix Native App in the Cloud*
+* Complete the [Prerequisites](/refguide10/mobile/getting-started-with-mobile/prerequisites/) of your app per its type
 * Make sure your [Nanoflow Commons](/appstore/modules/nanoflow-commons/) module is up to date
 * Read the [Language Menu](/refguide10/translatable-texts/) guide to understand the basics of the Mendix Language menu
 * Set up the required [languages](/refguide10/language-settings/) in Studio Pro—this tutorial has been configured with three languages as below: