Publish to App Store Connect

Publishing on iOS runs across two accounts that are yours: the build runs on your Expo account, and the finished binary lands in your App Store Connect account. Cadrant drives both and owns neither.

This flow applies to native Expo apps and to WebView apps, which are built and submitted exactly the same way.

Android has its own guide: Publish to Google Play.

Before you start

• A connected Expo account — the build runs on it, on your own free EAS quota of 15 iOS builds a month. Connect it in Integrations → Expo; without it a publish cannot start.
• An Apple Developer Program membership (annual subscription). That is what gives you access to App Store Connect.

How it works

1. In Cadrant, a four-step flow signs you in with Apple, creates the app on App Store Connect and provisions the distribution certificate.
2. The iOS build runs on your Expo cloud account, then Expo submits the finished binary to your App Store Connect account.
3. You install that binary through TestFlight, finish the listing, and submit the version for Apple review.

1. Join the Apple Developer Program

To publish on the App Store, enroll in the Apple Developer Program. The annual subscription is required. Once enrolled, you access App Store Connect to manage apps, receive builds and submit them to Apple.

2. Publish from Cadrant

From your mobile project preview, open the App Store publish button. A four-step flow guides you:

Step 1 — Apple sign-in

Sign in with your Apple Developer account email and password (enrolled in the program). Complete two-factor authentication if Apple asks for it, then select your development team if you belong to several.

Step 2 — App details

Enter the display name and upload the app icon (PNG, ideally 1024×1024 with no transparency). Cadrant then creates the app record on App Store Connect and links a bundle identifier to your project.

Step 3 — Certificate

Cadrant automatically provisions the iOS distribution certificate and App Store provisioning profile required for publishing. If Apple reports that the certificate limit is reached, import an existing distribution certificate as a .p12 file.

Step 4 — Publish

Start publishing. Three things happen in order: the iOS build is launched on your Expo cloud account, Expo submits the finished binary to your App Store Connect account, and you finalize the listing there. Track progress in the project activity log.

3. Test and finalize in App Store Connect

Once the build is received, continue in App Store Connect. The app is already created there by Cadrant. Install the build on a real device with Test with TestFlight first — it is exactly what your users will get. Then prepare the public release:

1. Open your app under « My Apps ».
2. Fill in the App Store listing: description, keywords, category, support URL and privacy policy URL.
3. Add required screenshots (iPhone, and iPad if applicable).
4. Complete the « App Privacy » questionnaire and age rating.
5. Create a version, then select the build uploaded by Cadrant.
6. Fill in « App Review Information » (demo account if login is required).
7. Click « Submit for Review ». Apple review usually takes 1 to 3 business days.