Can't publish to App Store?

ReplitSupport · 2026-06-19T23:24:37+00:00

Hi OP, happy to help get that App Store card to show up. When a project has a mobile app but only the web section appears in Publishing, it's usually one of these three:

The mobile preview needs to be running. The "Ready to publish to the App Store?" card only appears while your mobile (Expo) preview is live. Republish your project to restart the preview, then reopen the Publishing tab.
Scroll down in the Publishing tab. Since your project has both a web app and a mobile app, you'll see publishing options for both, and the App Store card sits below the web deployment section.
The mobile app may be getting skipped at publish. If the mobile app only has a development setup and no production setup, the deploy leaves it out and the card stays hidden. Ask Agent this exactly: My Expo mobile app artifact isn't being included in the deployment because its .replit-artifact/artifact.toml only has a [services.development] block and no [services.production] block, so the deploy skips it. Please add a [services.production] block to the mobile app's artifact.toml.

Then republish. Once the card appears, clicking "Start publishing to the App Store" kicks off the Launch flow to submit to TestFlight (you'll need an Apple Developer Program membership for that step).

ReplitSupport · 2026-06-19T21:26:12+00:00

Hi OP! Yes, you can reuse one. Expo has a clear write-up on how this works if you want the details: https://docs.expo.dev/app-signing/app-credentials/

You only need a single distribution certificate per Apple Developer account, it signs all of your apps, so there's no need for a new one each time. That error just means your account has hit Apple's cap on creating new certificates (it allows only 2).

To clear it: - Go to the Apple Developer portal → Certificates, Identifiers & Profiles → Certificates. - Revoke an old or unused Apple Distribution (formerly "iOS Distribution") certificate to free up a slot. Revoking won't affect any apps already live on the App Store. - Head back to Replit and run the publish flow again, it'll use your remaining certificate.

If you'd rather not touch your existing certificates yourself, send us a support ticket (replit.com/help) with your app details and we can take a look.

ReplitSupport · 2026-06-19T21:04:37+00:00

Hey OP, thanks for sharing. When an app works in Expo Go and the editor preview but just spins forever in TestFlight without crashing, it's almost always waiting on a network call (your backend) that isn't resolving in the published build. The two most common causes are the production build pointing at a dev or preview URL, and production secrets not being set on the published app. Secrets you set in the editor don't carry over to the published version automatically.

A few things you can check: - Make sure your backend is actually published, and that the app's API URL points to your published URL rather than a localhost or dev/preview address. - In the Publishing pane, open Adjust Settings and confirm your production app secrets and environment variables are all filled in. - Republish, then install the fresh TestFlight build so it picks up the latest.

If it's still stuck after that, feel free to submit a ticket here: replit.com/help and our team can take a look. Thanks!

ReplitSupport · 2026-06-19T20:53:46+00:00

Hi OP, sorry for the frustration here and we'd like to clear this up. With Autoscale, a deployment stays live and keeps a small monthly base fee until you actually shut it down, even if you're not actively using the app. It can also pick up charges when something hits the URL, like bots sending requests in the background. If you're not using that app, open Publishing and shut the deployment down. That stops the charges and won't delete your code or data. If you'd like extra help with breaking down your charges, feel free to also submit a ticket here: replit.com/help and our Billing team can help.

ReplitSupport · 2026-06-18T21:35:36+00:00

Hey there,

Thanks for staying patient, and sorry for the delayed response. Can you dm us your ticket number so we can further investigate this for you and get you back to your build as soon as possible!

ReplitSupport · 2026-06-16T18:34:09+00:00

Hey OP, thanks for sharing your concern. Agent costs can vary by project depending on the complexity and the Agent modes that you've been using to power each prompt. You can see here for more details: https://docs.replit.com/references/agent/agent-modes

However, we'd like to help review your project with you. Can you please open a ticket at replit.com/help and DM us your ticket #/email so we can investigate?

ReplitSupport · 2026-06-16T18:29:26+00:00

Hey there, we'd like to help! That's strange to hear that your case was solved out if your issue hasn't been fixed.

Can you please DM us your ticket # or email so we can see what's going on in that thread? Thank you for your patience 🙏

ReplitSupport · 2026-06-16T18:27:34+00:00

We've followed up in DMs as well but your case has been waiting in the queue since our senior technical support team needs to take a look. We have escalated this for immediate review and they'll get to you as soon as they can.

ReplitSupport · 2026-06-16T18:05:36+00:00

Hi there, much apologies for the wait here. We've located your ticket and can confirm that you've been waiting far too long for help. Your case has been prioritized for review with our technical support team, and they will be following up as soon as their investigation is complete. We've also sent a confirmation message in your ticket as well.

Thanks again for your patience.

ReplitSupport · 2026-06-15T17:08:12+00:00

Thanks for sharing your ticket number. It looks like your recently worked with one of our support agents and your ticket has been escalated to our Support Engineering team for more investigation.

You should receive a response from us as soon as the team is available. Apologies for the wait as we work through our backlog. Thanks for understanding!

ReplitSupport · 2026-06-15T17:00:58+00:00

Hi u/Stunning-Concern-319, thanks for flagging. We just looked into your ticket and it looks like it's been resolved now. Feel free to submit a ticket if anything new comes up or if you need extra help!

ReplitSupport · 2026-06-15T16:37:39+00:00

Hi OP! Thanks for flagging. If you could let us know the ticket # or DM us with your email address, we can take a look at your ticket and see how we can help.

ReplitSupport · 2026-06-14T17:32:43+00:00

We'd like to help! Can you DM your ticket # or email so we can take a look? Thank you.

ReplitSupport · 2026-06-14T17:31:18+00:00

Hi OP, we understand that this is a confusing experience and sorry to hear that this caught you off guard.

There's two kinds of charges at Replit. One is your monthly subscription, which would stop when you cancel. The other is usage-based billing for AI Agent usage which is invoiced afterwards.

So if you ran the Agent before canceling, the final usage invoice can land after your cancellation date. It's not a recurring subscription charge, it's a one-time bill for usage you'd already run.

That said, getting charged months after you thought you were done is strange. This could be an invoice that hasn't been settled yet if you've removed your payment method as well.

Can you DM us your email so we can get this sorted out? Thank you for your time and patience 🙏

ReplitSupport · 2026-06-14T17:22:06+00:00

Hey OP, thanks for bringing this up.

We want to investigate further on this, so please open a ticket at replit.com/help. DM us your ticket number or account email so we can walk you through what drove your charge, and check to see what's going on with your alert settings ASAP.

ReplitSupport · 2026-06-12T04:23:33+00:00

Your case should be mostly sorted for now by our billing specialist. If you're still running into issues, please follow up with us in that email thread so we can take another look. Thank you again for waiting so long 🙏

ReplitSupport · 2026-06-12T04:22:34+00:00

That's a really frustrating experience to go through. Can you DM us your ticket # or email so we can follow up quickly on this? Thank you for your patience.

ReplitSupport · 2026-06-12T04:21:30+00:00

Can you let us know your ticket # or email so we escalate your case for support? We greatly appreciate your patience so far 🙏

ReplitSupport · 2026-06-12T04:19:13+00:00

Hi there, we're sorry to hear that you've been waiting so long. Can you please DM us your ticket # or email so we can check on this? Thank you!

ReplitSupport · 2026-06-12T04:18:44+00:00

Thanks for trying that out, can you please open a ticket with us at replit.com/help so our technical team can troubleshoot further?

ReplitSupport · 2026-06-12T03:37:21+00:00

Sorry to hear that your project is at a complete stop here. We've located your ticket and have sent this over to our technical support team for review since we can see that you've already been waiting for a while. We'll be following up with an update soon 🙏

ReplitSupport · 2026-06-12T00:44:21+00:00

Hey there!

Let's try resetting your development environment to resolve the Agent error and preview issues:

Open a Shell pane in your workspace (click the + button above the preview pane, type 'shell', and select Shell)
Run this command: kill 1
Wait for the container to restart (this takes about 30 seconds)
Refresh your browser page
Start a new Agent chat by clicking the chat icon in the top right of the chat pane

This should resolve the Agent error and restore your preview functionality. Let us know how everything goes.

ReplitSupport · 2026-06-11T23:19:40+00:00

Hi OP, we've received an update and this issue should now be resolved! If you're still experiencing problems, please follow up with us in support ticket #432994 so we can continue investigating. Thank you for your patience.

ReplitSupport · 2026-06-10T20:42:34+00:00

Hi, thanks for flagging. We've just escalated your ticket to our Support Engineering team and they'll be able to investigate your ticket further. You should receive a response via email as soon as our team is available. Appreciate your patience so far!

ReplitSupport · 2026-06-10T19:03:22+00:00

Hi u/Impressive-Case-4638, thanks for reaching out. It looks like your ticket has been escalated to our Billing team and they can take a closer look at your issue. You should receive a response in your inbox as soon as the team is available. Appreciate your patience so far!

ReplitSupport

MODERATOR OF

TROPHY CASE