Skip to main content

Documentation Index

Fetch the complete documentation index at: https://bilt.me/docs/llms.txt

Use this file to discover all available pages before exploring further.

Bilt handles the full path from working app to App Store submission — certificates, provisioning profiles, builds, and TestFlight distribution.

​
Overview

Publishing an iOS app normally requires a Mac, Xcode, an Apple Developer account, code signing certificates, provisioning profiles, and familiarity with App Store Connect. Bilt simplifies this by managing the build and submission pipeline in the cloud.

​
What you need

  • Apple Developer account — Required by Apple for App Store distribution ($99/year at developer.apple.com)
  • App Store Connect API key — Generated in your Apple Developer portal
  • App details — Name, bundle ID, description, screenshots

​
Setup

The App Store tab in your project settings walks you through configuration:
1

API key

Upload your App Store Connect API key. This allows Bilt to submit builds on your behalf.
2

App ID and bundle ID

Set your app’s unique identifiers.
3

Distribution certificate

Upload or generate a distribution certificate for code signing.
4

Provisioning profile

Upload the provisioning profile that links your certificate to your app ID.
5

Expo / EAS setup

Configure your Expo access token and EAS project details for cloud builds.

​
Building and submitting

Once configured, you can:
  1. Build for iOS — Bilt creates a release build using Expo/EAS in the cloud
  2. Submit to TestFlight — Push the build to TestFlight for beta testing
  3. Submit to App Store — Send the build for App Store review
All of this is managed through the App Store tab — no terminal commands or Xcode required.

​
Status tracking

The App Store tab shows configuration health with status cards:
  • Green checkmarks for completed steps
  • Warnings for missing or expired credentials
  • Quick links to fix issues

​
Guide

For a detailed walkthrough, see the deploy to App Store guide.