Atlas E74243keac
Help Center›Deployments and Custom Domains›BUILDING NATIVE MOBILE APPS›What to do once your .ipa is ready for download
Table of contents
  • Before you start (quick checklist)
  • Step 1 — Upload the .ipa to App Store Connect
  • Option A (recommended): Transporter app (macOS)
  • Option B: Windows/Linux (advanced): Transporter command-line tool
  • After upload: what you should see
  • Uploading a build for the updated version of your app from Emergent
  • Step 2 — Test on real iPhones using TestFlight
  • A) Internal testing (your team)
  • B) External testing (customers / users outside your team)
  • Important TestFlight notes
  • Step 3 — Submit your app to the App Store (production release)
    • Related articles

    What to do once your .ipa is ready for download

    Last updated January 2, 2026

    An .ipa file is not something you “install” directly on your device. To run it on iPhones/iPads, you typically upload it to App Store Connect, then distribute it via TestFlight (beta) or the App Store (release).  Apple Developer+1 

    Before you start (quick checklist)

    • You have an Apple Developer Program account and access to App Store Connect.
    • You have the right App Store Connect role to upload builds (Admin/App Manager/Developer, depending on your org setup).

    Step 1 — Upload the .ipa to App Store Connect

    1. Install Transporter from the Mac App Store.  App Store 
    2. Open Transporter and sign in with the Apple ID that has App Store Connect access.Ensure you use the same apple id you used to generate build on emergent.
    3. Click Add (or drag-and-drop) and select the .ipa you downloaded from Emergent.  Apple Support 
    4. Click Deliver to upload.  Apple Support 
    5. Go to App Store Connect → My Apps → Your App → TestFlight and wait for the build to finish processing (this can take 10-15 mins).

    Option B: Windows/Linux (advanced): Transporter command-line tool

    If you don’t have a Mac, Apple also provides a Transporter command-line tool you can install on Windows/Linux, but it’s more technical than the app UI.  Apple Help+1 

    After upload: what you should see

    • Your build will appear in TestFlight and move through statuses like Processing → Ready to Test (wording varies).
    • If it fails, your transporter screen will usually show an error reason (for example: provisioning/profile issues).  Apple Developer+1 

    Uploading a build for the updated version of your app from Emergent

    Every time you generate a new build in Emergent, repeat the upload steps above to push the new .ipa to App Store Connect. (You may also need to add the new build to your TestFlight group, depending on your distribution settings—see Step 2.)

    If anything blocks you at upload/processing time, contact Emergent support.

    Step 2 — Test on real iPhones using TestFlight

    A) Internal testing (your team)

    Internal testers are people on your App Store Connect team (up to 100).  Apple Developer 

    1. Install TestFlight on the iPhone(s).  Apple Developer 
    2. In App Store Connect: My Apps → Your App → TestFlight.
    3. Under Internal Testing, create an internal group (or use an existing one).  Apple Developer 
    4. Add testers to the group (Invite Testers).  Apple Developer 
    5. Add your uploaded build to the group (Add Builds).  Apple Developer 

    Tip: If you enable automatic distribution for an internal group, new builds can be distributed automatically to that group (instead of manually picking builds every time).  Stack Overflow 

    B) External testing (customers / users outside your team)

    You can invite up to 10,000 external testers. External testing typically requires TestFlight App Review before testers can access the build.  Apple Developer+2Apple Developer+2 

    1. In the TestFlight tab, create an External Testing group.  Apple Developer 
    2. Add the build to the external group (this can trigger TestFlight review for the first build).  Apple Developer+1 
    3. Add external testers (email invites or other methods supported by Apple).  Apple Developer+1 
    4. Testers receive an invite email and can install the build using TestFlight.

    Important TestFlight notes

    • A TestFlight build is testable for up to 90 days, then expires—upload a new build to continue testing.  Apple Developer+1 
    • If your build shows “Not available for testing,” App Store Connect will usually tell you why (for example, provisioning/profile configuration).  Apple Developer 

    If you hit issues inviting testers, adding builds to groups, or seeing the build in TestFlight, contact Emergent support.

    Step 3 — Submit your app to the App Store (production release)

    1. Log in to App Store Connect and open My Apps → Your App.
    2. Complete required App Store listing metadata (name, description, screenshots, age rating, etc.).
    3. Create a new version (if needed) and select the build you want to ship.
    4. Submit for review.

    Apple review timing varies by app and region ranging from a 2-14 days. Watch the status inside App Store Connect rather than relying on a fixed timeline.

    If you need any further help , please contact Emergent support.

    Was this article helpful?