iOS Builds

Primio can build native iOS IPA files for TestFlight testing and App Store submission. iOS builds require App Store Connect API credentials.

Build time: ~10 minutes | Requires a paid plan

Note

IPA builds require a paid plan (Build or Scale). To test your app on iOS without a paid plan or App Store Connect credentials, use the free iOS Emulator build — see Emulator.

What you need

Note

You need an Apple Developer Program membership ($99/year) to create the required credentials. Enroll here if you haven’t already.

iOS builds require three pieces of information from your Apple Developer account:

1. App Store Connect API Key (.p8 file) — A private key file downloaded from App Store Connect
2. Key ID — A 10-character alphanumeric identifier shown next to your key
3. Issuer ID — A UUID found at the top of the App Store Connect API Keys page

Setting up credentials

1. Open App Store Connect

   Go to App Store Connect → Users and Access → Integrations → App Store Connect API.

2. Generate a new API key

   Click the + button. Give the key a name (e.g., “Primio Build Key”) and select the App Manager role.

3. Download the .p8 file

   Click Download. You can only download this file once — save it somewhere secure.

4. Note the Key ID

   The Key ID is shown next to your key in the list. It’s a 10-character alphanumeric string.

5. Note the Issuer ID

   The Issuer ID is shown at the top of the API Keys page. It’s a UUID in the format xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx.

Caution

Apple only lets you download the .p8 key file once. If you lose it, you’ll need to create a new key.

Caution

Apple allows a maximum of 3 iOS distribution certificates. Primio’s build process creates one automatically. If you already have 3, the build will fail. Manage your certificates in the Apple Developer Portal.

Note

Your .p8 key file is never stored by Primio — you’ll need to re-upload it each browser session. Your Key ID and Issuer ID are saved locally for convenience.

Building the IPA

1. Open the Publish section

   Go to Workspace → Publish → iOS.

2. Upload your .p8 key file

   Drag the file into the upload area or click to browse.

3. Enter your Key ID and Issuer ID

   Paste the values from App Store Connect.

4. Leave “Upload to TestFlight after build” checked

   It’s on by default and uses the same API key to upload the IPA to App Store Connect server-side. Uncheck it only if you want the IPA file without a TestFlight upload.

5. Click “Build IPA”

   The build takes about 15 minutes; the TestFlight upload runs automatically when it finishes.

Your Key ID and Issuer ID are saved in your browser session, so you don’t need to re-enter them for future builds in the same session.

After the build

Once the build completes, Primio uploads the IPA to App Store Connect automatically (when “Upload to TestFlight after build” is checked), and you can begin testing.

Create your app in App Store Connect

Register your app in App Store Connect before building — Primio’s upload returns a 412 error and shows a snackbar in the app if the app doesn’t exist yet.

1. Go to App Store Connect → Apps → + → New App
2. Fill in the app name, select your Bundle ID, set a SKU, and choose the primary language
3. Click Create

Caution

The Bundle ID must match the one in your Primio project settings. If they don’t match, the upload will fail.

Watch the upload

When the build finishes, the build’s row in Publish shows the upload result:

• Green TestFlight badge — uploaded to App Store Connect. The build appears in TestFlight after a few minutes of Apple processing.
• Amber “TestFlight failed” — click it to expand the error inline. Common causes: the app hasn’t been created in App Store Connect yet (412), the API key is invalid or expired, or the build number is a duplicate.

If you only want the IPA file (no TestFlight upload), uncheck “Upload to TestFlight after build” before clicking Build IPA. The IPA is always downloadable from the build’s row in Publish either way.

Test with TestFlight

1. In App Store Connect, go to your app → TestFlight
2. Your uploaded build appears after processing
3. Complete the Export Compliance Information (most apps select “None of the algorithms mentioned above”)
4. Create an Internal Testing group and add yourself as a tester
5. Download the TestFlight app on your iPhone
6. Open the email invitation on your iPhone — tap the link to install and test

You can add up to 100 internal testers and 10,000 external testers via TestFlight.

TestFlight build expiration

TestFlight builds expire after 90 days. After that, testers can no longer install or open the build. If your testing phase stretches longer, upload a new build before the old one expires to maintain tester access.

Processing times: After Primio finishes the upload, builds take 5-15 minutes to process before they appear in TestFlight. Occasionally this takes longer — check the Activity tab in App Store Connect for status.

External testers: The first build you send to external testers requires a brief Apple review (usually 24-48 hours). Subsequent builds to the same external group are available immediately.

Submit to the App Store

When you’re happy with testing, see the App Store Submission Guide for the full step-by-step submission process.

Project compatibility

Caution

Projects created before March 2026 may need to be regenerated for iOS compatibility. If you see a compatibility warning on the iOS build page, create a new project and re-describe your app.

Build history

Past builds are listed below the build form. Each entry shows the build status, download link for completed builds, and error messages if something went wrong.