brainbaby

How to Publish an iOS App — Build, Test and App Review

Treat building, uploading, testing and public release as separate steps. Brainbaby’s app-builder workflow can help develop the project, while Apple controls App Store distribution and review. Review the actual project, account settings and installed build before submitting. A working browser preview is not proof that the signed iOS app is ready.

Step by step

  1. Define a small app and verify its behavior

    Specify the intended user, main screens and one complete task. Iterate in the builder, then inspect the actual output. Check login, navigation, input, permissions and failure states before planning a store release. Keep a record of issues that still need work.

  2. Review the project and developer account

    Confirm the app identifier, version, build number and release settings in the project you will build. Check enrollment and required tasks in your Apple developer account. Do not assume that a generated project has every signing or store setting completed.

  3. Build and upload the intended binary

    Use the build and submission path appropriate to the actual project. For Expo projects, EAS Submit uploads a signed iOS binary to App Store Connect. Inspect the selected build and processing status. Uploading it is a checkpoint, not public release.

  4. Test the installed TestFlight build

    Install the exact build that will be submitted and reproduce the main workflow on a real device. Check keyboard behavior, small screens, authentication and any paid feature. Resolve issues in the signed build rather than relying on a web preview or a previous build number.

  5. Complete review information and purchase setup

    Finish the relevant listing, screenshots, privacy information and reviewer access. If the app sells digital products, review the product metadata and submission items. Apple requires an active Paid Apps Agreement for paid apps and In-App Purchases. Check the actual account status separately from the code.

  6. Select the build and submit for App Review

    Review the app version and associated items in App Store Connect, then submit the intended set. Apple’s submission overview explains which items can be reviewed together. Track the submission result and chosen release option. TestFlight availability does not mean that the app has been approved or released.

A small example to adapt

These are original fictional planning examples. They are not a generated benchmark, a completed release or a customer result.

  • Example brief: define a first-release app

    Plan a first release for a fictional personal shopping-list app. Screens: list, add item and settings. Expected behavior: blank input adds nothing; one valid item appears once; deleting an item removes the selected item. List the project settings and real-device checks still needed. Do not claim a signed build, TestFlight upload, payment test or App Review submission was completed.
  • Build and review record

    Project revision:
    App identifier:
    Version and build number:
    Signed-build processing status:
    Exact build installed for testing:
    Main workflows checked:
    Review access and purchase items checked:
    App Review submission status:
    Public-release status:

Review before the next action

  • Check the exact build

    Compare the uploaded, installed and selected build numbers. A fix in source code does not prove that the reviewer will receive that fix.

  • Make reviewer access usable

    Test the provided sign-in and the features that require it. Keep reviewer instructions consistent with what the installed build actually does.

  • Keep release statuses separate

    Record upload, processing, beta availability, review and public release independently. Do not describe an intermediate success as an App Store launch.

Frequently asked questions

Does an EAS upload release the app publicly?

No. EAS Submit uploads the binary. After processing, complete the App Store Connect steps and submit the selected build for App Review.

Does this guide promise automatic approval?

No. Apple evaluates the app and submitted items. Follow the current store requirements and resolve any reported issues.

Can subscription products be included with the app version?

Apple supports including subscription and purchase items in a review submission. Check the products’ metadata and actual submission state.

Does Brainbaby complete my developer account settings automatically?

Do not assume so. Confirm the actual signing, account, product and submission configuration before authorizing an upload or release.

Sources