What gets uploaded
A build is a real, installable copy of your app, the same kind of file you’d get from the App Store, except it isn’t published yet. Expo Go runs your code inside a shared preview app, a build is your app on its own, which is why features like push notifications and in-app purchases only work here. Replit’s Launch feature creates that build, signs it, and uploads it from the Publishing tab.Publish the web app first

Publishing PixelGames' web app and API server first.
Start publishing to the App Store

Starting the App Store launch from Replit's Publishing tab.
Choose your Expo project

Choosing the Expo project to launch.
Sign in with Apple

Signing in with Apple to connect the Expo project.
Choose your Apple app

Setting the app name and bundle identifier.
Configure Apple certificates

Launch configuring Apple's distribution certificate and provisioning profile.
Launch to the App Store

All steps complete, ready to launch to the App Store.
Wait for publishing to finish

Publishing to the App Store in progress, tracked from the Publishing tab.
Open it in TestFlight
Uploading again later
Changed something in PixelGames? Run the same flow again to get the new version up. It goes much faster the second time. Your Expo project, Apple account, app, and certificates are all still filled in, so most steps are just confirming what’s already there.Troubleshooting
- No distribution certificates found: normal on a first launch, select Create new certificate and Launch generates one.
- Sign in with Apple fails: confirm the account is enrolled in the Apple Developer Program, not just a regular Apple ID.
- Publishing seems stuck: it can take up to 45 minutes, and builds are queued at peak times. Check your Expo dashboard under Builds before assuming something’s broken.