--- title: "Distributing Associate App" slug: "distributing-associate-app-2" tags: ["abm", "Associate App", "testmode", "app distribution", "delivery", "mdm", "apple", "sdk", "test"] updated: 2025-11-05T10:38:15Z published: 2025-11-05T10:38:15Z canonical: "docs.newstore.com/distributing-associate-app-2" --- > ## Documentation Index > Fetch the complete documentation index at: https://docs.newstore.com/llms.txt > Use this file to discover all available pages before exploring further. # Distributing Associate App Understand how to distribute NewStore Associate App using Apple Business Manager. > [!NOTE] > Important > > This example uses [simpleMDM](https://simplemdm.com/) as an MDM application to distribute NewStore Associate App. Actual steps to distribute NewStore Associate App for your business may vary based on the MDM application you use. > > *Prerequisites for selecting an MDM application* > > - Ensure that the MDM application you want to use to distribute NewStore Associate App supports AppConfig. > - NewStore recommends using [simpleMDM](https://simplemdm.com/) or [jamf Pro](https://www.jamf.com/products/jamf-pro/) as MDM applications, as we provide full support for them. NewStore does not guarantee support for distributing NewStore Associate App via any other MDM applications. Note the following about NewStore Associate App when it is distributed with Apple Business Manager: - It is built with NewStore's Distribution Certificates. - It is distributed using NewStore's App Store Connect Account. - It is downloaded using your Apple Business Manager account, which allows you to distribute the app manually or using an MDM. Apps published privately in App Store Connect cannot be seen in the public App Store, but can be downloaded via Apple Business Manager. ## Prerequisites 1. Enable `Custom Apps` in Apple Business Manager. 1. In Apple Business Manager, go to `Settings` and select `Enrollment Information`. 2. Ensure that `Custom Apps` is set to `Enabled`. 2. (Optional) Connect your MDM to Apple Business Manager. 1. To download your server token, in your Apple Business Manager account, go to `Settings` > `Apps and Books` >`My Server Tokens`, and click `Download`. ![](https://cdn.document360.io/c2d22fcd-a44b-4e1e-bf3a-84f0ffba0dbe/Images/Documentation/8c850a90-bcb4-4f4a-8a96-3459a156ab05.png) 2. Upload the server token to your MDM application. ![](https://cdn.document360.io/c2d22fcd-a44b-4e1e-bf3a-84f0ffba0dbe/Images/Documentation/f49af737-12bd-4a98-8c04-d3be3b62d71f.png) 3. The name of your organization (`Organization Name`) and your `Apple ID` should appear in the list. ![](https://cdn.document360.io/c2d22fcd-a44b-4e1e-bf3a-84f0ffba0dbe/Images/Documentation/c2616547-6c71-4c86-ac00-7495246127c4.png) ## Requesting access to Associate App 1. Ensure you have an Apple Business Manager account. See [ABM](https://business.apple.com). 2. In Apple Business Manager, in the lower left corner, click `Settings` > `Enrolment Information`. 3. Send your Apple Business Manager **organization name** and the `Organization ID` to your contact point at NewStore. You contact point will inform you when your organization is configured on the NewStore side. 4. In the same screen, in the `Custom Apps` section, click `Enable`. 5. *(Optional)* If you use an MDM application, ensure your devices are enrolled in Apple Business Manager. 6. Go to the `Content` > `Custom Apps` section, you should see the app. It might take a few minutes to appear once NewStore has added your organization ID to its setup. > [!NOTE] > Important > > Your NewStore apps will appear in the `Custom Apps` tab, and not in the `Apps and Books` tab. ## Getting licenses 1. In Apple Business Manager, click `Custom Apps` and click the app name. 2. In the app details, find `Licence type` and select one of the following options: - `Managed`: use this option if you have an MDM application. - `Redemption Codes`: use this option if you want to manually distribute the app. 3. Select the number of apps you require and click `Get`. It might take some minutes for you to have access to the licenses. The available licenses appear in `Custom Apps` > `Manage Licenses`. Once ready, you can either use your MDM application to distribute the app, or share the redemption codes. For more information about licenses, see the [Apple documentation](https://support.apple.com/en-gb/guide/apple-business-manager/asmc21817890/web). ## Syncing with your MDM 1. Before you start distributing, sync your NewStore apps in the MDM application you are using. The available licenses should appear in the MDM now. ![](https://cdn.document360.io/c2d22fcd-a44b-4e1e-bf3a-84f0ffba0dbe/Images/Documentation/e331dc68-fd56-4cea-b1dc-6f2ba627f39a.png) 2. In the `Catalog` or `Apps` tab in your MDM application, the list of NewStore apps and associated licenses should appear. ![](https://cdn.document360.io/c2d22fcd-a44b-4e1e-bf3a-84f0ffba0dbe/Images/Documentation/2eb8320b-12d9-47f0-a537-e97145198b2f.png) If you cannot see the NewStore apps or available licenses in your MDM application, contact the support team. ## Configuring Associate App before distribution Currently, you can use `Managed Configuration Support` to configure NewStore Associate App in your MDM application before distribution: 1. In your MDM application, go to `Catalog` > `Managed Configuration Support`. 2. Configure the following keys (an example is shown in the screenshot below): > [!NOTE] > Important > > If both the `test` and `live` keys have been configured and set, Associate App opens in the `live` environment by default when launched or opened. Associates can then manually switch to the `test` environment if needed. - `test`: Specify the tenant string provided by NewStore, to be used for testing the app. The string includes a `-staging` in the name as a suffix. - `live`: Specify the tenant string provided by NewStore, to be used for using the app in a live environment. The string does not include `-sandbox` or `-staging` as a suffix. - *(Optional)* `storeId`: Specify the store ID to which the device is going to be assigned for the tenant. For more information on enabling associates to automatically switch stores, see [Using your credentials](/v1/docs/using-newstore-associate-app#using-your-credentials). ![](https://cdn.document360.io/c2d22fcd-a44b-4e1e-bf3a-84f0ffba0dbe/Images/Documentation/23c21293-3e00-4636-8aaa-f9638b2619ee.png) > [!NOTE] > Important > > This configuration is required **only** for **new** retailers with tenants available only on the `production` environment. To properly set **existing** retailers in the platform with tenants on `staging` and `production` environments, set the following keys: > > - `stage`: Specify the stage for the apps (`p` for production or `s` for staging). > - `tenant`: Specify the name of the tenant. > - *(Optional)* `storeId`: Specifies the store ID to which the device is assigned for the tenant. ### Using TestFlight to access beta builds > [!NOTE] > Important > > We use [TestFlight](https://developer.apple.com/testflight/) as a tool to access beta builds before the official release of a new version of Associate App. It is provided and maintained by Apple, and offers quick access via an Apple Account. To receive access to a beta build, you must request access to an external testing group. These are created and maintained by NewStore. NewStore will provide an invitation link to onboard you to the testing group. Once onboarded, every build uploaded to TestFlight is accessible and the user is notified. 1. Request an external testing group from NewStore. 2. Download [TestFlight](https://apps.apple.com/us/app/testflight/id899247664) from the [App Store](https://www.apple.com/app-store/) for the iPhone that you want to use it for. 3. Open the public invitation link provided by NewStore to onboard onto the testing group. 4. Tap `NewStore Associate App` to open the menu for the app. 5. Tap `Install` to download the latest version or tap `Previous builds` to choose a build to download. The version and build number are provided by NewStore. 6. You must bootstrap the downloaded Associate App versions via TestFlight. Either scan a provided QR code or enter this URL in the Safari Browser of your device: `com.newstore.associate-one://bootstrap?live={tenant}&test={tenant-staging}` Add an additional `storeId` parameter to create an [automatic assignment](/v1/docs/enabling-associates-to-work-in-multiple-stores#setting-up-automatic-assignment-using-a-qr-code%E2%80%8B) to a store for any user logging in. `com.newstore.associate-one://bootstrap?live={tenant}&test={tenant-staging}&storeId={store-id}` ### Configuring Associate App with a PLIST configuration file Most of the MDM applications require a `ManagedAppConfig.plist` file to be uploaded. This PLIST file contains the necessary keys to configure the application during the distribution to the devices. A sample PLIST configuration file is provided here: ```xml      live    YOURTENANT    test    YOURTENANT-staging    storeId    YOUR-STORE-ID    cartExtendedAttributes           [         { "name": "device_id", "value": "00007130-000215A325C1401D" },         { "name": "some_key", "value": "some_value" }       ]       ``` - `live`: your live tenant - `test`: your testing tenant - `storeId` (optional): Specify a store this device will be assigned to. Associates who log into the app on this device will then be automatically assigned to that store. - `cartExtendedAttributes` (optional): Retailers often need to associate specific metadata with orders processed through the Associate App. For example, you may want to automatically assign a unique device identifier to orders (for example, tax reporting). This can be done by setting an array of objects containing `name` and `value` fields. When configured, the app automatically adds this data to each order’s extended attributes, including during offline operations. If you are using `Meraki` as your MDM application, you may have to copy the values manually to your `AppConfiguration` file. For more information, see [Using the Managed App Settings Payload](https://documentation.meraki.com/SM/Profiles_and_Settings/Using_the_Managed_App_Settings_Payload). Users of `jamf` may run into issues using the sample config above. In this case, only use the part between `<dict>` and `</dict>`. ### FAQs #### Is it possible to share IPA (iOS AppStore Package) files? Apple does not officially support sharing IPA files directly for general distribution. IPA files are meant to be distributed through Apple's official channels, such as the Apple App Store or through Apple's enterprise distribution methods. Here are some methods recommends by Apple: - App Store : The most common method, where apps are submitted, reviewed, and then made available to the public or in specific regions via the App Store. - TestFlight : Apple's official beta testing service, `TestFlight`, allows developers to share their apps with a limited number of testers before the app is released in the App Store. `TestFlight` also enables the installation of specific versions of the app. Sharing IPA files outside of these official channels pose security risks, as users would need to trust the app and manually install it. This has the potential to bypass important security checks and updates provided by the App Store. #### Is it possible to limit the distribution to specific version using MDM? No, MDM synchronizes with the App Store. So, whenever a new version is available there, it is also available to MDM. However, you can choose whether to roll out the new version to devices. Until the new version is installed, users can continue using the old version unless it is deleted from the device. This means that while the MDM cannot control the availability of app versions, it can decide whether to install the new version or remain on the older version. **Related topics** - [Prerequisites](/v1/docs/prerequisites#assoapp-reqs) - [Using NewStore Associate App](/v1/docs/using-newstore-associate-app#assoapp-instorepurchase)