Replit App to App Store: Fix Rejections at the Source

How to publish a Replit app to the App Store

Replit mobile apps run on Expo and React Native, so you ship a real native app. According to Replit's iOS upload docs, the Launch wizard works like this. After that, you test on TestFlight and submit for review from App Store Connect.

• 1. Publish the web app first, so your backend is live.
• 2. Confirm or create the Expo project.
• 3. Sign in with your Apple Developer account.
• 4. Set the app name and bundle ID.
• 5. Let Launch create the distribution certificates and provisioning profiles.
• 6. Select "Launch to App Store". The build is compiled and uploaded to App Store Connect, and you get a TestFlight invite.

What the Launch flow does, and what it doesn't

For each area, here is what Launch does and what it leaves to you. Every rejection below comes from what it leaves to you.

• iOS build and signing. What Launch does: builds, signs and uploads. What it leaves to you: nothing.
• Bundle ID. What Launch does: locks it to your Replit project after the first publish. What it leaves to you: picking the right one before that publish.
• Backend. What Launch does: your server runs on Replit. What it leaves to you: publishing it, keeping it up, not breaking it during review.
• App icon and permissions. What Launch does: takes them as they are in the build. What it leaves to you: a new store build every time they change.
• Store listing, privacy answers, review notes. What Launch does: nothing. What it leaves to you: all of it.
• Google Play. What Launch does: not supported. What it leaves to you: the whole Android release, by hand.

Why Apple rejects Replit apps: symptom, cause, fix

For each problem, here is the symptom, the cause on the Replit side and the fix.

• Rejected under 2.1, "app crashed" or "blank screen". Cause on the Replit side: the build calls a dev or preview URL, or the web app was never published. Fix: publish the web app, point the build at the published URL, rebuild.
• Rejected under 2.1, errors on some screens only. Cause on the Replit side: you changed the backend API after the build was uploaded. Fix: keep the API stable during review, or rebuild and resubmit.
• Launch fails on a later publish. Cause on the Replit side: the bundle ID was changed after the first build. Fix: go back to the original bundle ID or plan a new app record.
• Permission prompt missing or unclear. Cause on the Replit side: permissions or their text were changed in code, but no new store build was made. Fix: make a new store build. Hot reload does not reach store builds.
• Reviewer can't get past login. Cause on the Replit side: no demo account in App Review Information. Fix: add a working demo account and write review notes.

The dev URL trap

In the workspace, your app talks to a preview server. That works on your phone through Expo Go. A store build that still points there will fail as soon as the preview goes to sleep or changes. That's why Replit's docs tell you to publish the web app before you launch. Before you submit, open the TestFlight build on mobile data, with the Replit workspace closed. If a screen breaks, the build depends on something that isn't published.

A backend that moves during review

Replit's mobile docs say your server runs on Replit in the cloud. That makes it easy to change. It also means a prompt like "rename this field" can break the build the reviewer is testing, because their build still expects the old API. Freeze the backend from the moment you submit until the app is approved. After that, version your API before you change anything the store build depends on.

The bundle ID you can't take back

Replit ties the bundle ID from your first publish to your project. If you change it later, the next App Store publish fails. Decide two things before your first publish: the final bundle ID, and whether the app goes out under your name or under a company account. Investors and future buyers usually expect the company account.

Icons and permissions need a new build

Replit's docs say changes to app icons or permissions usually need a new store build. A common mistake: you fix the camera prompt text in Replit, see it working in preview and resubmit the old build. Apple then sees the same issue again. Every change to app.json, the icon or a permission string needs a new Launch.

Apple's general rules, in one line each

These apply to every app, built in Replit or not. Each one is quoted from Apple's App Review Guidelines. Our AI prototype to production guides go into each one in more detail. Not sure which of these is blocking your build? Book a call and send us the rejection message beforehand.

• 3.1.1: if you unlock features or content inside the app, such as subscriptions or premium access, you must use in-app purchase.
• 5.1.1(v): if your app supports account creation, you must also offer account deletion within the app.
• 4.8: if you use a third-party login like Google Sign-In for the main account, you must also offer an equivalent login that limits data to name and email and lets users keep their email private. Sign in with Apple meets these conditions. There are exceptions, for example apps that only use your company's own sign-in.
• Privacy: you need a live privacy policy URL and privacy answers that match what the app collects, including text or photos sent to an AI model.

How to get a Replit app on Google Play

Replit's docs say publishing to Google Play is not yet supported. You can preview Android in the emulator, but the release is manual. The backend issues above apply here too. An Android build pointing at a preview URL fails the same way.

• Build an Android App Bundle (.aab) with Expo's EAS build service.
• Create the app in Play Console, fill in the content rating and data safety form, and upload the bundle.
• Repeat the upload by hand for every new version.
• Check your account type before you plan a launch date. According to Google's Play Console Help, personal developer accounts created after November 13, 2023 must run a closed test with at least 12 testers, opted in continuously for at least 14 days, before they can apply for production access. That page covers personal accounts, so pick the account type early.

Keep fixing in Replit, or hand it over?

For each situation, here is the best move. If you built with other AI tools too, our Lovable and AI builder guides cover the same move from prototype to store.

• Free app, iOS only, one rejection you understand. Best move: fix it in Replit with the list above.
• Several rejections in a row. Best move: get the code and the listing reviewed before resubmitting.
• Paid digital features. Best move: set up in-app purchase properly first.
• You need iOS and Android together. Best move: a studio build skips the manual Android path.
• You want the code on your own GitHub. Best move: move to a repo you fully own.

What handing it over looks like with us

We start from your Replit app and build the production version. Want to know if your Replit app should be fixed or rebuilt? Free 30-minute call. Book a call. What you get:

• Apps for web, iOS and Android.
• Fixed at $3,460, with a fixed quote before we start.
• Delivered in about 20 days.
• Progress shown every week.
• Design included.
• 100% of the code is yours, on your GitHub.
• 2 weeks of fixes after launch.

Does Replit publish to the App Store directly?

Replit builds, signs and uploads your iOS app to App Store Connect, then sends you a TestFlight invite. You finish the listing and submit for review yourself.

Why does my Replit app work in Expo Go but fail review?

Expo Go runs against your workspace preview. The store build has to call your published backend. If the web app wasn't published, or the build points at a dev URL, the reviewer sees errors.

Can I change the bundle ID of a Replit app?

Not safely. Replit ties the bundle ID from your first publish to the project, and changing it makes the next App Store publish fail.

Can Replit publish to Google Play?

Not yet, according to Replit's docs. You build the .aab yourself, for example with EAS, and upload it in Play Console for every version. Stuck between Replit and the App Store? Book a call and we'll look at your build together.