Prepare your app for store publishing

“App publishing” brings together Expo connection and the iPhone and Android steps. Preview is available now. Store artifact builds and uploads are temporarily paused.

Before opening the wizard

1. 1

   Test the app

   Select “App” and test its screens and features in preview. Fix failures before requesting a store release.

2. 2

   Connect Expo as the owner

   Open publishing and follow Connect Expo. Saving reveals the Android trial, iPhone, and Google Play sections.

3. 3

   Prepare the store account

   You will need an Apple Developer account for iPhone or a Google Play Console account for Android. Check account fees and verification requirements on the store website when registering. Save credentials only in the wizard fields.

iPhone wizard steps

1. 1

   Complete Apple Developer enrollment

   In the iPhone section, open the enrollment link. Once membership is active, click “Done, I completed this step” in the wizard. Activation follows Apple’s process.

2. 2

   Save an App Store Connect key

   Use the Users and Access, Integrations, API Keys link to prepare a key with appropriate permissions. Copy the Key ID, Issuer ID, and .p8 file contents into the matching fields, then click “Save key”. “Saved securely” appears after saving.

3. 3

   Create the app record

   Open App Store Connect, Apps, then +. Choose iOS and enter the name, language, matching app identifier, SKU, and access. If you do not know the app identifier, ask the assistant before creating the record. Return and mark the step done.

4. 4

   Build and upload when available

   The wizard proceeds from “Build the iOS app” to “Upload to TestFlight”. Both are currently paused. When available, wait for a successful build before uploading. TestFlight is a testing stage; public release requires completing Apple’s process and review.

Android wizard steps

1. 1

   Complete your Google Play account

   Open Play Console from the Android section and complete registration and verification, then mark the wizard step done.

2. 2

   Prepare a store release when builds are available

   “Build the store bundle (AAB)” prepares the store artifact and shows a download button after success. Builds are currently paused. The APK section is for direct Android installation, and it is paused too.

3. 3

   Follow the manual first-upload step

   The current wizard directs you to create the app in Play Console and upload the first AAB manually, with descriptions, images, and store requirements. Mark the step done after completing it there.

4. 4

   Prepare optional updates

   For later uploads through the platform, prepare a Google service account with app permissions in Play Console. Paste the Service Account JSON into “Automatic updates” and save. Uploads use “Upload an update to Google Play” when available; editing the app alone does not trigger an upload.

Progress and errors

The wizard saves completed steps so you can return later. When builds are available, it shows “Queued”, “Building”, and “Ready”, with a build-page link. The wizard does not guarantee a fixed queue, build, or store-processing duration.

1. 1

   If saving credentials fails

   Check the fields, error message, and your owner access, then save again. Do not send key contents in chat or to support.

2. 2

   If a build fails once service is available

   Read the detailed log. If “Ask Codey to fix the error” appears, click it, follow the chat, and rebuild after the fix finishes. Address any security warning before the next attempt.

3. 3

   If maintenance remains visible

   Use preview to continue testing and keep your preparation ready. Changing tokens or retrying will not enable builds during maintenance.