Creating and Uploading iOS Builds
To use the full feature set provided by Applause Codeless Automation, iOS apps require two build types for each app:
    Simulator build: for recording and editing tests
    Enterprise build: for test run execution on real devices
You can begin recording tests without uploading an enterprise build; however, to run the tests on real devices you must upload an Enterprise build.

Creating a Simulator Build

Simulator builds must use the naming convention<application>
Optionally, if you want to include a version in your filename using the format <application>-<version>, ACA uses the version to auto-populate the Version field in the Create New Build page.
To create a simulator build of your app, perform the following procedure:
    Run your app in your Xcode iPhone simulator. This automatically creates a simulator build in Xcode's DerivedData folder in the following path: ~/Library/Developer/Xcode/DerivedData folder. For assistance finding this location on your system, open Xcode and select Xcode > Preferences, then select the "Location" tab. The path to the DerivedData folder displays in the Derived Data section.
    Zip your simulator build by navigating to the file in Finder, right-clicking the file, and clicking Compress.
You can verify the simulator build by using the ios-sim utility. Once installed run, ios-sim launch /path/to/

Creating an Enterprise Build

Automated test execution is performed on real devices, and Apple requires Ad-Hoc or In-House (Enterprise) builds to install applications on real devices outside of the Apple App store.
This is a summary of the process for creating an Enterprise build. This process varies for iOS Native apps vs. React Native apps. For assistance, please refer to the official Apple documentation.
To create an Enterprise build of your app for test execution, perform the following procedure:
    Use your Apple Developer Enterprise account to create an iOS Distribution Certificate for “In-House and Ad Hoc”.
    Create your App ID.
    Create an iOS Provisioning profile and select “In House” as a distribution method.
    Select manually signing certificate by unchecking the “Automatically manage signing” selection.
    Select the provisioning profile created in Step 3 for Signing (Debug) and Signing (Release).
    Select Code Signing Identity under Build Setting as “iPhone Distribution for enterprise account”.
    Create an Archive by selecting Product -> Archive.
    Once the Archive is created, select the Export option and select “Enterprise” as the distribution method.
    Follow the steps until it creates the App folder.
    Download the .ipa file.

Uploading iOS Builds

    Click “Builds” to navigate to the builds page.
    From the Products drop-down, select the product matching the build you want to upload.
    Click ‘New Build” to display the Create New Build page. Licensing is structured on a per-app basis; however, you can upload as many builds as you need for the same app.
    In the Simulator Build section, select “File” or “URL”.
      File: If you are uploading a file, drag and drop your simulator build into the UI or click “or click to add” and select your simulator build. Ensure the filename follows the naming convention <application>
      URL: If you want to use a URL to specify the location of your build, click “URL” and enter the URL in the “URL for build” field.
    In the Enterprise Build section, select File or URL and provide the file or URL. Ensure your filename follows the naming convention <application>.ipa Note: If you do not provide an Enterprise build, you cannot run recorded tests on real devices.
    Add notes about the build if needed.
    Click “Create Build”.
Last modified 5mo ago