Prerequisites
- A working Bilt app you’re ready to publish
- Enrollment in the Apple Developer Program ($99/year)
Step 1: Enroll in the Apple Developer Program
If you are not enrolled yet:- Go to developer.apple.com/programs/enroll
- Enroll as an individual or organization
- Complete identity verification (may take 24–48 hours)
Step 2: Create your app and bundle ID
Register the bundle ID in Apple’s developer portal, create the app in App Store Connect, then link both in Bilt.Register a Bundle ID
- Go to Apple Developer Portal — Register a Bundle ID
- Enter your bundle identifier (e.g.
com.yourcompany.appname) and a description - Click Continue and complete the registration
Create the app in App Store Connect
- Go to App Store Connect — Apps
- Click + next to Apps in the top left corner and select New App
- Select iOS as the platform, enter your app name, and choose a primary language
- For Bundle ID, select the bundle ID you registered in the previous step
- For SKU, enter any unique value (for example, the last segment of your bundle ID)
- Set User Access to Full Access, then click Create
Link both in Bilt
In your Bilt project, open Settings → App Store → App Store Connect:
- Under Bundle ID, enter the bundle identifier you registered and click Save
- Find your Apple ID in App Store Connect:
- Open App Store Connect — Apps
- Click the app you created
- In the left sidebar, click General → App Information
- On the App Information page, look under the General Information heading for Apple ID — a numeric value such as
1234567890(this is not your bundle ID) - Copy that number
- Under App ID, paste the Apple ID into the field
Step 3: Create an App Store Connect API key
Bilt uses your API key to create and manage signing assets on your behalf. Generate the key in App Store Connect, then add it in the App Store Connect tab.Open App Store Connect API keys
Generate a new key
Under Team Keys, click + next to Active. Name the key (e.g. “Bilt”), set the role to Admin, and click Generate
Download and copy credentials
Mark down the Issuer ID and Key ID, then download the
.p8 private key file.Step 4: Set up certificates and provisioning profiles
Open Settings → App Store → Certificates:- Generate — Bilt creates a distribution certificate and provisioning profile for you (recommended if you do not already have signing assets)
- Upload your own — Provide an existing
.p12certificate and.mobileprovisionprofile if you already use Apple distribution signing
Step 5: Build and publish to TestFlight
Open Settings → App Store → Publish:- Click Start build & publish when all prior steps are complete
- Bilt runs a cloud build. Progress appears under Recent builds
- After the build finishes and Apple processes it, open TestFlight from the Publish tab to manage testers
Step 6: Submit for App Store review
When you are ready to go live:- Complete your App Store listing in App Store Connect (description, screenshots, pricing)
- Select your build in Testflight and submit for review
- Apple reviews the app
- Once approved, your app is live on the App Store
App Store tabs in Bilt
| Tab | What to configure |
|---|---|
| Quickstart | Guided checklist through all steps above |
| App Store Connect | Bundle ID, App ID, and API key (.p8, Key ID, Issuer ID) |
| Certificates | Generate or upload distribution certificate and provisioning profile |
| Publish | Start builds, monitor progress, and open TestFlight |
Common issues
Distribution certificate already exists
Distribution certificate already exists
You have hit Apple’s limit for distribution certificates on your account. Revoke an unused certificate in the Apple Developer certificates list, then try generating again in the Certificates tab.
Bundle ID already declared on this project
Bundle ID already declared on this project
If you see A target with this bundle id is already declared on the project, that bundle identifier is already linked to this Bilt project (for the main app or an extension). Use the existing target in the Certificates tab, or choose a different bundle ID when registering a new one in Apple Developer.
Certificate or provisioning profile mismatch
Certificate or provisioning profile mismatch
Ensure your distribution certificate matches the provisioning profile, and both match the bundle ID. Regenerate in the Certificates tab or upload matching assets.
Build fails
Build fails
Check the build logs in the Publish tab. Common causes: expired certificate, missing app icon, or unsupported API usage.
App Store rejection
App Store rejection
Apple provides a reason for rejection. Common fixes: add a privacy policy URL, ensure the app has enough functionality, and remove placeholder content.
Further reading
- App Store deployment without developers — Alternatives for non-technical founders to publish to the App Store without using Bilt
- App Store Publishing feature — Feature overview
