> ## Documentation Index
> Fetch the complete documentation index at: https://moengage.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Migrate To The Extension Integrator Tool

> Migrate from a manual iOS notification extension setup to the MoEngage Extension Integrator Tool in your React Native app.

All steps in this guide are performed in Xcode, open your iOS project by launching `ios/YourApp.xcworkspace` in Xcode before proceeding.

To migrate from an existing manual implementation to the integrator tool, follow the below steps:

### Step 1: Prerequisites

Before proceeding, ensure the following are in place:

* Ensure you are using MoEngage React Native SDK version [12.6.0](/docs/release-notes/sdks/react-native#core-12-6-0) or above to utilize the extension integrator tool.
* **SDK initialization:** Initialize the MoEngage SDK using [file-based initialization](/docs/developer-guide/react-native-sdk/sdk-integration/react-native/sdk-initialization/file-based-initialization/file-based-initialization).
  * **App Group configuration:** Provide the `AppGroupName` key (for example, `group.com.organization.app`) you are using with your `sdkConfig.appGroupID`.
* After integration is complete, you may be prompted to access the keychain for code signing. Click **Always Allow.**
  <Frame>
    <img src="https://mintcdn.com/moengage/X586_MHJ15DsSG1z/images/keychain.png?fit=max&auto=format&n=X586_MHJ15DsSG1z&q=85&s=bba38a4dc7160d9ee9eafc785c9dc5ba" alt="Keychain" title="Keychain" style={{ width:"48%" }} className="mr-auto" width="1040" height="404" data-path="images/keychain.png" />
  </Frame>

### Step 2: Integrate MoEngageRichNotification

Integrate `MoEngageRichNotification` if you need to support either of the following push notification features:

* **Rich media** — display images, GIFs, or video in the notification banner
* **Rich push templates** — render interactive notification layouts such as carousel

<Info>
  This step is mandatory if you have integrated the content extension.
</Info>

<Tabs>
  <Tab title="Swift Package Manager (SPM)">
    To install the `MoEngageRichNotification` through SPM, perform the following steps:

    1. Navigate to **File > Add Package**.
    2. Enter the repository URL:
       * `https://github.com/moengage/apple-sdk.git`
    3. Select the **master** branch or a specific version and select **Add Package**.
    4. Target the package to your application.
  </Tab>

  <Tab title="CocoaPods">
    <Warning>
      **Information** CocoaPods is being deprecated. MoEngage recommends using Swift Package Manager for all new integrations. For more info, refer [here](/docs/developer-guide/ios-sdk/sdk-integration/basic/sdk-integration).
    </Warning>

    1. Add the following line to your `Podfile` inside your app target.

    <Info>
      The `react-native-moengage` package already brings in `MoEngage-iOS-SDK`, you only need to add the `RichNotification` subspec.
    </Info>

    ```ruby lines wrap theme={null}
    pod 'MoEngage-iOS-SDK/RichNotification'
    ```

    2. Run pod install:

    ```ruby lines wrap theme={null}
     pod repo update
     pod install
    ```
  </Tab>
</Tabs>

### Step 3: Integrate the extension integrator tool

Automate the extension configuration by adding a custom script to your build process.

1. In Xcode, select your application target, go to **Build Phases**, and click **+** to add a **New Run Script Phase**.

<Frame>
  <img src="https://mintcdn.com/moengage/F4npPBVazsQn0JKX/images/newrunscriptphase.png?fit=max&auto=format&n=F4npPBVazsQn0JKX&q=85&s=4c0db98aafc37139866d3cd48765ef80" alt="Newrunscriptphase" title="Newrunscriptphase" className="mr-auto" style={{ width:"54%" }} width="1094" height="944" data-path="images/newrunscriptphase.png" />
</Frame>

<Info>
  If you have already added a script phase and configured the input files, you can simply update the run command as described in step 3 below.
</Info>

2. Add the following paths to the **Input Files** section:

* `$(BUILT_PRODUCTS_DIR)/$(INFOPLIST_PATH)`
* `$(INSTALL_DIR)/$(INFOPLIST_PATH)`

<Frame>
  <img src="https://mintcdn.com/moengage/F4npPBVazsQn0JKX/images/path-1.png?fit=max&auto=format&n=F4npPBVazsQn0JKX&q=85&s=e38b6527f2e8dd128e6d1642f12e32ee" alt="Path 1" title="Path 1" style={{ width:"54%" }} className="mr-auto" width="1096" height="908" data-path="images/path-1.png" />
</Frame>

3. In the shell script input box of the Run Script Phase added in step 1, enter the command relevant to your dependency manager, replacing `$OPTIONS` with your desired configuration:

<Tabs>
  <Tab title="Swift Package Manager (SPM)">
    ```bash Swift Package Manager (SPM) lines wrap theme={null}
      ${OBJROOT}/../../SourcePackages/artifacts/apple-sdk/moengage-extensions-integration/moengage-extensions-integration.artifactbundle/moengage-extensions-integration/bin/moengage-extensions-integration $OPTIONS
    ```
  </Tab>

  <Tab title="CocoaPods">
    ```bash CocoaPods lines wrap theme={null}
      ${PODS_ROOT}/MoEngageExtensionsIntegration/moengage-extensions-integration.artifactbundle/moengage-extensions-integration/bin/moengage-extensions-integration $OPTIONS
    ```
  </Tab>
</Tabs>

#### Available options

Replace `$OPTIONS` with one or more of the following:

| Option                                                                 | Description                                                                                                                                                                   |
| :--------------------------------------------------------------------- | :---------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `--enable-push-notification-templates`                                 | Required if the content extension from Step 2 is used.                                                                                                                        |
| `--notification-service-extension-name $CUSTOM_SERVICE_EXTENSION_NAME` | Sets a custom name for the service extension. Use this when migrating to this tool from a custom service extension implementation.  (Default: `MoEngageNotificationService`). |
| `--notification-content-extension-name $CUSTOM_CONTENT_EXTENSION_NAME` | Sets a custom name for the content extension. Use this when migrating to this tool from a custom content extension implementation. (Default: `MoEngageNotificationContent`).  |

### Step 3: Remove existing extensions

Remove existing service and content extensions added in **Frameworks**, **Libraries** and **Embedded Content** section.

<Frame>
  <img src="https://mintcdn.com/moengage/xuAxu0ab-ChXtexC/images/removeexistingextensions.png?fit=max&auto=format&n=xuAxu0ab-ChXtexC&q=85&s=f788a1e626bf9799cd9f857cc6d7b5aa" alt="Removeexistingextensions" title="Removeexistingextensions" style={{ width:"62%" }} width="1024" height="705" data-path="images/removeexistingextensions.png" />
</Frame>

<Warning>
  Failing to remove prevents push delivery impressions and rich push notifications.
</Warning>