Replit iOS publish fails with "unexpected error" before it ever submits

Your mobile app runs fine in the Replit preview. You hit publish to send it to the App Store, and it dies almost instantly with a generic "unexpected error". No log, no error code, no hint. You retry, same thing. You ask support and get silence. This exact failure has been hitting Replit users since late August 2026: iOS publishes fail before submission, support tickets sit unanswered for days, and r/replit has filled up with the same report. If this is you, the most important thing to know is that the error is almost certainly not in your app. Here is how to confirm that, and how to get your app to the App Store without waiting for Replit's publish button to come back.

Why the error is a black box

When you publish an iOS app from Replit, your app does not go straight to Apple. Replit's pipeline wraps two big steps: it builds your app with Expo's build service (EAS), then submits the result to the App Store. Both of those steps produce detailed logs. Replit shows you none of them. When something inside that pipeline breaks on their side, all you see is "unexpected error", and nothing you change in your app will make it go away, because your app was never the problem. That is why people rebuild screens, rename bundles, and burn agent credits for days with zero effect.

First, check whether it is you or them

1. Does the app run in preview? If your app works normally in the Replit preview and on your phone via the preview link, the app itself builds and runs. A genuinely broken app usually fails in preview too.
2. Does publish fail instantly with no detail? A real build error takes minutes to surface and usually names a file or a setting. An instant failure with a generic message means the pipeline fell over before it even looked at your code.
3. Check for a wider incident. Open status.replit.com and search r/replit for "iOS publish". If other people are reporting the same failure the same week, it is their pipeline, and no amount of editing your app will fix it.

If all three point at Replit, stop debugging your app. You have two real options: route around their publish button, or wait it out the smart way. Both are below.

The workaround: build and submit it yourself with Expo

Here is the part Replit does not advertise: your Replit mobile app is an Expo project under the hood. Expo is a normal, open toolchain that anyone can use directly, for free. That means you can run the exact same build Replit runs, on Expo's own service, with full logs, and even submit to the App Store yourself. You stop depending on Replit's broken button entirely.

1. Get your code out. In your Replit workspace, download the project as a zip (or push it to GitHub). Unzip it on your computer, or open it in any environment where you can run commands.
2. Create a free Expo account. Sign up at expo.dev. The free tier is enough for this.
3. Install the EAS command line tool and run a build. In the project folder:

   npm install -g eas-cli
   eas login
   npx expo prebuild
   eas build --platform ios

   The prebuild step is only needed if the build asks for it. EAS will walk you through the first-time setup questions with sensible defaults.
4. Read the real logs. This is the payoff. EAS shows you the entire build, line by line. If there truly is a code or config problem in your app, it stops being an "unexpected error" and becomes a named, visible, fixable error. And if the build goes green, you have proof the app is fine.
5. Use a green build as ammo for your support ticket. Reply to your Replit ticket with: "The app builds successfully on EAS, build link attached. The failure is in your publish pipeline." That moves your ticket from "user app problem" to "our infrastructure problem", which is a different, faster queue.
6. Submit to Apple directly if you cannot wait.

   eas submit --platform ios

   This sends your green build straight to App Store Connect using your own Apple Developer account. Your app reaches Apple review without Replit's publish button being involved at all.

A note on Apple credentials

Publishing an iOS app requires an Apple Developer account ($99 per year). Replit requires this from you anyway, so you almost certainly already have one. Replit builds through their own pipeline, but the App Store listing is yours, under your account. When you run eas submit, EAS asks you to sign in with that Apple account and can create and manage the signing certificates and provisioning profiles for you automatically. You do not need to understand Apple's signing system. Answer the prompts and let EAS handle it.

When to just wait instead

The EAS route is real command line work. If that is not something you can take on right now, waiting is a legitimate choice, but wait actively, not passively:

• Reply to your existing support ticket with your ticket number in the message, and say plainly that publishing is blocked and preview works. Replies bump tickets; new tickets start over at the back.
• Post in r/replit. The ReplitSupport account does escalate tickets from there. Include your ticket number in the post. Users in this incident got escalations that way after email went nowhere.
• Do not ask the agent to "fix publish". The agent edits your code. It cannot touch Replit's publish pipeline, which is where the failure lives. Every "let me fix that" attempt costs a checkpoint and changes code that was not broken. That is money spent making your app worse while the actual problem sits on Replit's servers.

Still stuck?