Skip to content
Winter Sale from $619, until 31st December 2026 Book now
From agentic coding tool to the App Store iOS · App Store Bolt

Bolt Expo App to the App Store: Turning the Expo Go Preview into a Signed, Approved iOS App

A Bolt mobile project runs inside Expo Go during development – a host app with its own bundle ID, URL scheme, permissions and entitlements. Your App Store build has none of these until you configure them. Fix redirects, purpose strings, capabilities, native modules, environment values and icons, put the signing credentials in an account your company owns, and plan updates as new builds unless a change is a pure fix.

7 min read

Key takeaways

  • Expo Go borrows its identity to your project during preview; the signed app needs its own scheme, purpose strings, entitlements and icons.
  • Auth redirects are the most common break: the preview uses an Expo Go address, the release build needs your own scheme on the auth provider's allow list.
  • Keep Apple and Expo credentials in accounts the company – or the client – owns, not in a freelancer's personal account.
  • Use over-the-air updates for fixes only; new features ship as new builds with review notes.

What the Bolt preview proves – and what it does not

When the first prompt asks Bolt for a mobile app, it sets up an Expo project, and Bolt's device preview lets you scan a QR code and run it on your phone in Expo Go. That is a fast feedback loop. It is also a source of false confidence, because Expo Go is a finished app of its own: it brings its own bundle identifier, URL scheme, permission texts, entitlements and a fixed set of native modules. Your JavaScript runs inside it.

The binary you upload to App Store Connect has none of those borrowed parts. Everything Expo Go provided must now come from your app config and your Apple account. Our blog post on converting Bolt to an iOS app covers the EAS commands; this article covers what breaks between the preview and the store, and how to keep it from breaking.

Six things that change between Expo Go and your signed build

1. Auth redirects

Email confirmation links, password resets and OAuth flows redirect back to the app. In Expo Go they target an Expo Go address; in your build they need your own scheme from the app config. Add that scheme and its redirect paths to the allow list of your auth provider – Bolt Database or Supabase – or sign-up works in the preview and fails for the reviewer.

2. Purpose strings

Expo Go asks for camera or location access with its own texts. Your build needs specific purpose strings under ios.infoPlist, naming the feature and the reason. Generic texts are a common reason for questions from App Review.

3. Capabilities and entitlements

Push notifications, Sign in with Apple and universal links worked – or seemed to – in the preview. In your app they require capabilities on your App ID and a matching provisioning profile. Declare them in the app config so the build service can set them up.

4. Native modules

Expo Go only contains modules from the Expo SDK. If Bolt added a library with its own native code, it may have failed silently in the preview or been stubbed out. In your build it works only if it is installed properly and configured through its config plugin – test it in a development build before you trust it.

5. Environment values

Values Bolt kept in its project environment must reach the build. Public values such as the API URL or a publishable key use the EXPO_PUBLIC_ prefix and are visible in the bundle; real secrets belong on a server, never in the app.

6. Name, icon and bundle ID

Replace generated placeholder icons with a 1024 × 1024 App Store icon without transparency, set the display name, and choose a bundle ID you will keep forever.

Talk to an AI Code Engineer about shipping your app to the App Store.

In a free call we look at what you built, tell you honestly what stands between it and an approved release – and whether you need us at all.

Who owns the signing credentials

EAS can create and store your distribution certificate and provisioning profiles in your Expo account, or use credentials you manage yourself. Either is fine technically. The question that matters is ownership:

  • The Apple Developer account should belong to the company that publishes the app – for agencies, that means the client's account, with the agency invited as team members.
  • The Expo account that holds the credentials should be an organization account, not a freelancer's personal login.
  • The App Store Connect API key used for uploads should be created by the account holder and stored as a secret in Expo or CI.

Getting this right before the first build saves a painful transfer later. It also matches how App Review expects apps to be published: by the business behind them.

Bolt plus a local agent: one repository, one owner per file

Many Bolt projects continue in two places: quick UI changes in Bolt, deeper work in Cursor, Claude Code or another local agent, connected through GitHub. That works if you agree which side owns what. A simple rule: release files – the app config, eas.json, the privacy-relevant parts of the config – are only changed through reviewed pull requests.

Any agent, Bolt included, may rewrite the app config while fixing something unrelated. Before every build, look at the diff of the app config: bundle ID, version, permissions, plugins. Our comparison of Rork and Bolt for Expo apps discusses how the two builders handle exports and syncing.

Updates after approval: new build or over-the-air?

Bolt's own documentation describes mobile updates as rebuild and resubmit. Expo also offers over-the-air updates through EAS Update, which deliver new JavaScript to installed builds with a compatible runtime version. Apple tolerates downloaded code only within limits: it must not change the app's purpose or add features the reviewer never saw.

ChangePath
Text fix, bug fix, small layout correctionOver-the-air update is acceptable
New screen, new feature, new paid contentNew build, TestFlight, review with notes
New permission, SDK, capability or native moduleNew build – it cannot ship over the air
Different login or payment flowNew build and updated review notes

Our posts on Bolt apps and Guideline 2.3.1 and Guideline 5.6 show what happens when what users see drifts away from what was reviewed.

The App Review angle for Bolt Expo apps

Beyond the usual rules for sign-in, purchases and account deletion, two issues are typical for Bolt Expo apps. First, generic design: apps built from similar prompts can look alike, and Guideline 4.3 targets apps that are not distinct enough. Give yours its own content, visuals and purpose. Second, a backend that is not ready: a database on a free tier can pause after inactivity, and a reviewer who meets a failed sign-in rejects the build as incomplete.

Our AI Code Engineers take Bolt Expo projects through credentials, EAS or CI builds, TestFlight, the listing and the review conversation – in your own Apple account, via the iOS submission service. For the Android version, read Bolt Expo app to Google Play.

From Bolt preview to App Store build

  • The app config defines your own scheme, and the auth provider allows its redirect URLs.
  • Every permission has a specific purpose string in ios.infoPlist.
  • Push, Sign in with Apple and universal links are declared as capabilities in the app config.
  • Libraries with native code were tested in a development build, not only in Expo Go.
  • Only public values use EXPO_PUBLIC_; secrets live on the server.
  • A 1024 × 1024 icon without transparency, the final name and bundle ID are set.
  • Apple and Expo credentials sit in accounts the publishing company owns.
  • The app config diff was reviewed before each build.
  • Over-the-air updates are limited to fixes; features ship as new builds.
  • The backend stays awake and the review account works in the TestFlight build.

Frequently asked questions

My Bolt app works in Expo Go. Why does the TestFlight build fail?

Because Expo Go supplied things your build now has to provide itself: URL scheme, permission texts, entitlements and native modules. Check auth redirects first – they are the most frequent cause – then purpose strings and any library with native code.

Can Bolt submit my Expo app to the App Store?

No. Bolt creates the project and the preview. Building, signing and uploading happen with EAS or another build service under your Expo and Apple accounts, and you submit in App Store Connect.

Are over-the-air updates allowed on iOS?

Within limits. Fixes that do not change the app's purpose or add new features are generally fine; new features belong in a reviewed build. Anything native – permissions, SDKs, capabilities – always needs a new build.

Should an agency publish client apps under its own account?

No. Publish under the client's Apple Developer account and work in it as invited team members. That keeps ownership clear and matches what App Review expects.

Can you finish our Bolt Expo app for the App Store?

Yes. Book a free call; an AI Code Engineer reviews your exported project with you, lists the gaps between preview and store build and explains what we can take over.

Free, 15 minutes, no obligation

Get your app from agent output to approved release.

Our AI Code Engineers take apps built with Claude Code, Codex, Cursor, Lovable, Base44 and co. through signing, CI/CD, store listings and review – in your own developer accounts.

AI tools, store policies and requirements change quickly – always check the current documentation of the tools and stores you use. This article is independent advice and not affiliated with or endorsed by Apple, Google, Anthropic, OpenAI or any other company or product mentioned; all trademarks belong to their owners.