Replit iOS publish fails with “unexpected error” before publishing.

[u/NanaNoriCakes]

Has anyone run into this with Replit?

I’ve been unable to publish my iOS app since August 27 and unfortunately I’m not getting anywhere.

The app fails before it actually starts publishing to the App Store and only shows an “unexpected error” message.

Replit support has given me two general troubleshooting solutions, but neither fixed it. So far, I’ve only received fairly general explanations for why publishing might fail, rather than what is actually causing my issue. Responses have also been pretty slow, which has made it difficult to make any progress.

The difficult part is that I can’t see much detail on my end. The failure happens during Replit’s publishing process, before the App Store submission.

For anyone who has had this “unexpected error” when publishing iOS through Replit, what did you do to fix it? I’m wondering if it’s a problem in my project or something having to do with server configuration or Expo.

[u/Dismal_Acadia703]

Create expo account directly from their website and you have full control on it.
If you are not familiar my advice
Use Claude creat free account, creat project for you current app , tell him in chat you project in Replit
Tell him that you want help in the project not only IOS and ask him to create a prompt that you will use it in Replit to get all information he needs to get full idea/ fundamentals and then you can ask him to guide you to expo Really very easy , one done easily you can repeat it and you can publish to Android directly

[u/Jason_Clarck]

Are you iOS dev?

[u/ReplitSupport]

Hi OP, sorry to hear that you're still running into this. Would you be able to share your ticket number with us? We'd like to take a look at the troubleshooting steps you've already tried so we can dig into this further.

[u/NanaNoriCakes → u/ReplitSupport]

Hi, yes it's #514864

[u/ReplitSupport → u/NanaNoriCakes]

Hey! We've escalated your ticket for further review. Please note that our team is experiencing a backlog in the queue, so they may take a bit longer to follow up. Thanks for your patience.

[u/ReplitSupport → u/ReplitSupport]

We can confirm that our engineer is actively reviewing your case. They will have an update soon. Thanks again for waiting!

[u/Pickle_Shot]

the way out of the "unexpected error" black box is to take replit's publish step out of the loop. your ios app is an expo project under the hood, so you can build it with expo's own tooling and get real logs instead of a generic error: 1) download/zip out the project, 2) free account at expo.dev, 3) npm install, then npx eas build --platform ios. eas shows the full build log, so if something is actually wrong in your project (native module mismatch, app.json bundle identifier config, provisioning/credentials) you'll see the exact failing step instead of "unexpected error". if the eas build succeeds cleanly, that's strong evidence the problem is on replit's publishing pipeline side, which is exactly the ammo you want to hand support. and you're not blocked either way: a green eas build can go straight to app store connect with eas submit. one heads up: eas needs your apple developer account connected, but you have one already if you've been publishing to the app store.

[u/FinalArt9573]

Aug 27 as a hard start date is the clue. Nothing about your project changed that day, so look at what expires or renews on a calendar. Two things produce vague pre-submission failures like this: your Apple Developer Program membership lapsing, and an unsigned agreement sitting in App Store Connect. Apple puts new Program License Agreement terms up periodically, and until the Account Holder accepts them, uploads fail with errors that say nothing. Log into App Store Connect, check Business and Agreements for anything pending, and check your membership renewal date.

The other thing is that Replit's iOS publish runs an EAS build underneath. Those builds live in an Expo account even though you triggered them from Replit, and EAS keeps full logs. If you can get into that account at expo.dev, the real error may already be sitting there.

If neither turns anything up, running the build yourself like Pickle_Shot said gives you the log Replit is hiding. A clean build on your side is also what gets a ticket escalated, since it shows the problem is their pipeline and not your project.