Key takeaways
- Replit's own publish flow suits apps that only use Expo SDK modules; dev builds and EAS CLI are not available inside Replit.
- Moving to EAS keeps the same bundle ID and App Store record – only the build pipeline changes, and build numbers must keep rising.
- The Replit deployment stays your backend: the app needs its production URL, never a development address, and public config values are not secrets.
- A development build replaces Expo Go once you need native code; continuous native generation keeps the agent away from hand-edited native folders.
Replit's publish flow or your own EAS pipeline?
Replit Agent builds mobile apps with Expo and React Native. You preview them in Expo Go, and Replit's publishing flow can take an iOS app through Apple sign-in, cloud build and upload to TestFlight – our article on converting Replit to an iOS app describes that route. This article is about the next stage: when the project outgrows Replit's flow and moves into a pipeline you control.
| Your situation | Stay with Replit publishing | Move to EAS |
|---|---|---|
| Native features | Everything works with Expo SDK modules in Expo Go | You need a library with its own native code, a widget or a custom config plugin |
| Team | One maker, changes through Agent | Several developers, code review, CI checks |
| Platforms | iOS only | iOS and Google Play – Replit does not publish to Play |
| Control | Fine with Replit handling credentials | You want your own credential store, build profiles and reproducible builds |
Replit does not support EAS CLI or development builds inside its workspace, so moving means taking the code out. That is a normal step for a growing app, not a sign that something went wrong.
Taking the Expo project out of Replit
Connect the Replit project to GitHub and decide where edits happen from now on. Two-way sync works, but parallel edits in Replit and in a local editor create merge conflicts that agents handle badly. Most teams switch the mobile app to a local workflow – often with a coding agent such as Claude Code; see Claude Code for React Native and Expo – and keep Replit for the server.
Then separate what runs where:
- The backend stays on Replit. The published deployment, ideally on your own domain, is what the app talks to. Builds must never point at a workspace or development address.
- Configuration moves into the app config. Values with the
EXPO_PUBLIC_prefix are inlined into the JavaScript bundle. Use them for the API URL and publishable keys only. Server secrets stay in the Replit deployment's secrets. - Auth and payments keep their providers. Clerk and RevenueCat work outside Replit too; make sure the app uses their production instances, not development ones.
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.
Keep the bundle ID and the App Store record
If the app was already published through Replit, its bundle identifier is fixed and an App Store Connect record exists in your Apple account. Do not create a second record. EAS builds for the same bundle ID, and the new builds simply appear under the existing app.
Three details make the switch smooth:
- Build numbers. Every upload needs a higher build number than the last one Replit uploaded. EAS can manage version numbers remotely and increment them automatically – set that up before the first EAS build.
- Credentials. EAS can generate a distribution certificate and provisioning profile or use ones you upload. Apple limits how many distribution certificates a team can hold, so check what already exists in your account before generating new ones.
- Push. If the app sends notifications, the push key or certificate has to be available to the new setup as well.
Expo's EAS Build documentation covers profiles and credentials in detail.
Replace Expo Go with a development build
Expo Go only contains the modules bundled with the Expo SDK. Once your app needs anything else, create a development build: a debug version of your own app with the developer tools built in. Install it on registered test devices or the simulator, and the agent-built code finally runs with the native modules it needs.
Keep the native projects generated, not hand-edited. With continuous native generation, the ios folder is created from the app config during the build, and changes happen through config plugins and app config fields. That suits agents well: they edit one readable config file instead of an Xcode project. Release-relevant settings then live in one place:
ios.bundleIdentifier– fixed, never changed by an agent,ios.infoPlist– purpose strings that name the feature using each permission,ios.privacyManifests– required-reason API declarations for your own code,ios.usesAppleSignIn– if Sign in with Apple is offered.
Use a current Expo SDK so the EAS build image archives with Xcode 26 and the iOS 26 SDK, which App Store uploads require.
What App Review checks in a Replit Agent app
- A server that answers. An Autoscale deployment scales to zero when idle. The reviewer's first request may wake it, so the app must show a loading state rather than an error. An always-on deployment avoids the issue.
- A review account in production. Create it against the production auth instance, confirm its email and unlock paid features.
- Sign in with Apple wherever Google or another third-party login is offered as the main account option.
- In-App Purchase for digital upgrades, with RevenueCat products mapped to StoreKit products in App Store Connect.
- Account deletion in the app, removing the auth user and their data on the server.
- No changes during review. An Agent session that redeploys the backend while Apple tests can change what the reviewer sees – our article on Replit apps and Guideline 5.6 explains why that matters.
Submitting from EAS – and who presses the button
EAS Submit uploads the finished build to App Store Connect with an API key stored in your Expo account; from there it appears in TestFlight. Test with internal testers first, then submit the version for review with complete notes and the demo login. The listing, App Privacy answers, age rating and the review conversation stay with the account holder.
Our AI Code Engineers handle this transition regularly: moving the Expo project to EAS, setting up credentials and CI, preparing the listing and privacy details and managing the review in your own Apple account. See the iOS submission service, and continue with Replit Agent app to Google Play if Android is next.
Moving a Replit Agent app to EAS
- You know why you are leaving Replit's publish flow – native modules, team workflow or Android.
- Edits to the mobile app happen in one place; Replit keeps the backend.
- The app points at the production deployment, and only public values use the EXPO_PUBLIC_ prefix.
- EAS builds the existing bundle ID, and build numbers continue above the last Replit upload.
- Existing distribution certificates were checked before EAS generated anything new.
- A development build replaced Expo Go for testing native modules.
- Purpose strings, privacy manifest and Sign in with Apple are set in the app config.
- The review account exists in production and the backend does not show errors after idle periods.
Frequently asked questions
Can I keep publishing from Replit after moving to EAS?
Pick one pipeline per app. Two build systems uploading to the same App Store record lead to clashing build numbers and confusion about which code is live. Once you move to EAS, build and submit from there.
Do I lose my App Store listing when I leave Replit's publish flow?
No. The listing belongs to your Apple Developer account. EAS builds for the same bundle ID, and new builds appear under the existing app in App Store Connect.
Do I need a Mac for EAS builds?
No. EAS builds iOS apps on macOS machines in Expo's cloud. A Mac is useful for running the simulator locally, but not required for the store build.
Can Replit Agent still work on the backend?
Yes. Many teams keep the server on Replit and let Agent work there, while the mobile app lives in GitHub with its own pipeline. Coordinate API changes so the version in review keeps working.
Can you help move our Replit app?
Yes. Book a free call and an AI Code Engineer looks at your Replit project, your Apple account and your goals, then suggests the shortest safe route to EAS and the App Store.
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.