Skip to main content
TL;DR: Yes, AI can build an app and publish it to the App Store, and Vibecode does both. Its agent writes your iPhone app in Swift, and Vibecode builds it, signs it with your Apple Developer account, uploads it and submits it for Apple’s review. React Native apps go through Expo Launch, and you submit those in App Store Connect.Here’s how to publish an app on the App Store with Vibecode, no Mac needed: click Publish → Publish to App Store, confirm the bundle ID and send the request Vibecode writes in your chat. You need Apple’s Developer Program ($99 a year) and a Vibecode Plus plan or higher. In our test on October 29, 2026, the agent had done everything it could 27 minutes after we pressed Send. The rest waited on a phone number for Apple’s reviewers and one Apple ID sign-in, which a new app’s first release needs. For a different app on October 27, the release build, upload and submission took under 5 minutes. Apple then reviews 90% of submissions within 48 hours (Apple).
To publish an app on the App Store you need four things: a paid Apple Developer Program membership ($99/year), a signed build of your app uploaded to App Store Connect, a complete App Store listing (name, description, screenshots, privacy policy, and privacy details), and approval from Apple’s App Review, which finishes 90% of submissions in under 48 hours. With Vibecode you don’t need a Mac or Xcode. For a native Swift iOS app, click Publish → Publish to App Store: Vibecode builds, signs, uploads, and submits the app for review. For a React Native Mobile app, click Deploy → Submit to App Store: Vibecode prepares the app, Expo Launch builds and uploads it, and you submit it for review in App Store Connect. Still building the app itself? How to make an app covers the steps before this one, from the first prompt to testing on your phone.

The Publishing Process at a Glance

Which AI App Builders Submit to the App Store for You

Every route to the App Store needs Apple’s Developer Program, at $99 a year (Apple), and Apple reviews every app. What differs is who builds the app, who uploads it and who presses submit. We checked each tool’s own docs on October 29, 2026, and each name links to the page we read: Of the tools in this table, only Vibecode’s iOS app flow submits your app for review. With the others, the last step is yours in App Store Connect, and with Bolt, Base44 and Lovable you also handle the build or the upload. For price, code export and what each tool builds, see the best AI app builders and the best AI mobile app builders. Apple never removed Vibecode from the App Store. The Vibecode iPhone app has been on the App Store since June 17, 2025 (App Store status).

Before You Start

You’ll need the following before submitting your app:
  1. Apple Developer Program membership ($99/year)
  2. App Store Connect access
    • Sign in at appstoreconnect.apple.com and accept any pending agreements
    • Charging money? Also complete the Paid Apps Agreement, tax, and banking under Business
  3. A Vibecode plan with App Store submission: Plus or higher (compare plans)
  4. For Mobile app (React Native) projects: a free Expo account. Vibecode uses Expo Launch to build and upload.
  5. For iOS app (Swift) projects: an App Store Connect API key with the Admin role, or App Manager with access to Certificates, Identifiers & Profiles, which Vibecode uses to upload and submit. Sign in with your Apple ID and Vibecode creates the key for you. On a new app’s first release, Vibecode also needs a current Apple ID sign-in, because the key can’t create the app in App Store Connect or confirm its App Privacy answers. If you connected with an API key, or your last sign-in has expired, the agent sends you a link.
  6. An Apple device for 2FA: keep your iPhone, iPad, or Mac nearby for two-factor authentication codes
  7. A privacy policy URL and a support URL. Apple requires both for every app. For an iOS app (Swift), Vibecode writes and hosts both pages when you publish, adds them to your listing and links the privacy policy inside the app. For a Mobile app, have your own ready.
Your app is published under your Apple Developer account, so your name (or your company’s legal name) appears as the seller on the App Store.

iOS App or Mobile App: Which Steps to Follow

Vibecode projects are one of three types. Two of them can go to the App Store, and they publish differently: You can start either flow from the Vibecode web app or from the Vibecode iPhone app: tap Publish at the top of your project. Web apps don’t go to the App Store. To turn a website into an iPhone app, see How to Turn a Website Into an App.

Publish a Native iOS (Swift) App

Native iOS projects don’t use Expo, and you don’t need a Mac, because Vibecode builds the app on its cloud Macs (more on publishing without a Mac). We ran these steps on October 29, 2026 with Mochi Habits, a habit tracker built in Vibecode, from the web app. Our run stopped at the Apple ID sign-in in step 7, so the last step’s time comes from a different app we submitted from the same account on October 27, 2026.
1

Open Publish to App Store

Click Publish at the top right of your project and choose Publish to App Store. In the Vibecode iPhone app, tap Publish at the top of your project.
The Publish menu of a native iOS project in Vibecode, with Install, Publish to App Store and Deploy 4 updates
2

Connect your Apple account (first time only)

If Vibecode doesn’t have an App Store Connect key for you yet, the panel says App Store Connect key needed. Click Add an App Store Connect key. On the page that opens, sign in with the Apple ID you use for developer.apple.com, or click Use an API Key Instead and add a key with the Admin role, or App Manager with access to Certificates, Identifiers & Profiles. Our account was already connected, so we skipped this step.
The Connect Apple Account page, with Apple ID email and password fields and a Use an API Key Instead button
3

Click Publish to App Store

The panel says Vibecode will build your app and submit it for review. Click Publish to App Store.
The Publish to App Store panel with its Publish to App Store button
If your project uses Vibecode Cloud and has backend changes you haven’t deployed, Vibecode asks about them next. Click Deploy backend if your app signs people in or saves data online, since the published app talks to your deployed backend. Mochi keeps its data on the phone, so we clicked Publish anyway.
The Undeployed changes card in the publish panel, with Publish anyway and Deploy backend buttons
4

Confirm your bundle ID

Vibecode suggests a bundle ID, your app’s permanent ID on the App Store. Ours was com.vibecode.mochihabits-q5mvqf. You can edit it now, but not after you publish. Click Confirm and publish.
The bundle ID step of the publish panel, with a suggested bundle ID and a Confirm and publish button
5

Send the publish request

Vibecode writes a publish request into your chat box. Add anything the agent should know, then press Send. We added “Set the release to manual, so it does not go live until I release it.” Everything up to here took us under 2 minutes.
The chat box with the publish request Vibecode wrote, ready to send
6

Let the agent prepare the release

The agent gets the app ready for Apple and reports each step in the chat. In our run it:
  • wrote and hosted a privacy policy page and a support page, and added a Privacy Policy link inside the app, which Apple also requires. It checked the link in the simulator. This took 7 minutes.
  • ran a first cloud build of the app in 5 minutes
  • took three screenshots of the app in the simulator and wrote the description, keywords and category, as a free app in all countries. This took 6 minutes.
  • ran a readiness check, which lists anything Apple will still ask for
7

Give the agent what only you can

The agent asks in the chat for anything it can’t do for you. Ours asked for two things:
  • A phone number for Apple’s reviewers. Apple only uses it if a reviewer needs to reach you.
  • An Apple ID sign-in. Vibecode uploads and submits with your App Store Connect key, but on a new app’s first release only an Apple ID can create the app in App Store Connect and confirm its App Privacy answers. The agent sends you a link, and Apple sends a code to your iPhone or Mac. Apple’s sign-ins expire, so the agent asks again when yours has. Ours had.
The agent's message in the chat: what it has done so far, then a request for an Apple ID sign-in and a phone number for Apple's review team
We tried to skip the sign-in. In App Store Connect we created the app ourselves (+, then New App, with the bundle ID Vibecode had registered) and published its App Privacy answers, which took a few minutes. The agent picked up the new app, but it still needed the sign-in to confirm the privacy answers before a first release, so plan on signing in.
App Store Connect's New App dialog filled in for Mochi Habits, with iOS, English (U.S.), the bundle ID Vibecode registered, a SKU and Full Access
8

Vibecode submits it for review

After you sign in, Vibecode builds the signed release of your app on a cloud Mac, uploads it, waits for Apple to process it, fills in the rest of the listing and submits it for review. Open Publish to follow along. The row shows Publishing to the App Store and then Submitted for review. You can close the panel, and the publish keeps running. When we submitted a different app from the same account on October 27, this last step took under 5 minutes and the app went to Waiting for Review. That app’s cloud build took under 2 minutes, against 4 to 5 for Mochi, and Apple’s processing time varies, so allow longer.
The publish panel showing Building your app while a publish runs
Vibecode builds iOS apps for iPhone and iPad. If your app supports iPad, Apple needs at least one 13-inch iPad screenshot. Vibecode’s preview runs iPhone, not iPad, so the agent draws the iPad screenshot from your app’s design. We wanted only real screenshots, so we asked the agent to make Mochi iPhone-only, which took one more cloud build of 4 minutes.

How Long It Took

From the moment we pressed Send, the agent had done everything it could on its own in 27 minutes, including the iPhone-only rebuild we asked for, and the rest waited on a phone number for Apple’s reviewers and the account owner’s Apple ID sign-in. The full steps for native projects are also in Native iOS Apps: Publish to the App Store. Want testers first? See How to Use TestFlight. Haven’t built your app yet? Describe your app and Vibecode builds it.

Publish a Mobile (React Native) App

Mobile app projects are built with Expo. Vibecode prepares the app, Expo Launch builds it in the cloud and uploads it to App Store Connect, and you submit it for review.

Run Preflight First

Preflight is an automated check that scans your app for common issues that cause Apple to reject it. It’s optional, but it can save you days of waiting on a rejection over a simple fix.
Preflight button in the deploy dropdown
  1. Open the Deploy menu (Deployments once your app is published)
  2. Hover over the App Store section. The Preflight button slides in next to Submit to App Store.
  3. Click Preflight. This runs the /appstore-preflight skill in your chat, and you can also run it there yourself at any time.
  4. The agent works through the checklist, fixes what it can, and reports what’s left

Submit With Expo Launch

1

Start the submission

In the web app, click Deploy (or Deployments) at the top right, choose Submit to App Store, and click Get Started. In the Vibecode iPhone app, tap Publish at the top of your project; the same steps open in a sheet.
2

Confirm the prerequisites

Check the four boxes: you’ve paid for the Apple Developer Program, signed the agreements in App Store Connect, have an Expo account, and have an Apple device ready for 2FA codes. Quick links help you finish any you haven’t.
3

Add your Expo access token

Click Get access token from Expo, sign in to Expo, go to Settings → Access Tokens, create a token, and paste it into Vibecode. Check for extra spaces when you paste.
4

Confirm your app details and icon

Vibecode prefills the App Name (2 to 30 characters), the Version Number (such as 1.0.0), and Support iPad (if on, Apple also requires iPad screenshots). Review your app icon too; you can generate one in Vibecode.
5

Choose a bundle ID (first build only)

A bundle ID is your app’s unique identifier, like com.yourcompany.appname. Vibecode suggests one and you can change it, but treat it as permanent once your first build is submitted.
6

Start Expo Launch

Click Start Expo Launch. It opens in a new tab, handles Apple sign-in and build setup, starts the cloud build, and uploads the build to App Store Connect. Builds usually take about 20 minutes, longer at busy times. You can close the Vibecode dialog once the build has started and follow it in the Expo Dashboard.
7

Submit for review

When the build finishes, it’s in App Store Connect and available in TestFlight. Complete your listing and submit it.

Later Builds

You won’t need a new bundle ID. Start Expo Launch again with a higher version number, then follow the new build in Expo and App Store Connect.

Complete Your Listing and Submit

Before Apple reviews your app, its App Store listing must be complete. For Mobile apps you fill this in at App Store Connect → Apps → your app. For iOS apps, the agent fills in what it can on your first publish and tells you what’s left.
Apple has announced that from April 2027, apps built with the iOS 27.1 SDK or later also need iPhone Duo screenshots, 1398 × 2034 for the outer display and 2007 × 2853 for the inner one (Apple). Also from April 2027, iPhone apps uploaded to App Store Connect must be built with the iOS 27 SDK or later and target iOS 15 or later (Apple).
For Mobile apps, then submit in App Store Connect:
  1. Open your app and the version you’re preparing (for example 1.0 Prepare for Submission)
  2. Under Build, select the build Expo Launch uploaded
  3. Choose how to release it: manually, automatically after approval, or on a date
  4. Click Add for Review, then submit it to App Review
Apple emails you when the status changes. You can also follow it in App Store Connect or the App Store Connect app.

Questions Apple Asks on Your First Submission

Besides the listing, Apple asks a few questions before it takes a new app. For iOS apps, the agent answers App Privacy, the age rating and encryption from your app’s code. EU trader status is yours to set.
  • App Privacy. What data the app collects and whether it tracks people. Your answers become the privacy label on your App Store page, and Apple needs them for every new app and update (Apple). Mochi keeps everything on the phone, so we answered Data Not Collected.
  • Age rating. A questionnaire about your app’s content and features. The ratings are 4+, 9+, 13+, 16+ and 18+, and AI chat features count toward the answers (Apple). It also asks about social media features, and Apple has required those answers for new apps and updates since September 2026 (Apple). For iOS apps, the agent answers from your app’s code. When nothing applies, it answers None or No to every question, which gives a 4+ rating.
  • Encryption (export compliance). Whether the app uses encryption beyond what Apple’s system provides, such as HTTPS. Vibecode’s iOS apps answer No in the app’s Info.plist file (ITSAppUsesNonExemptEncryption), which is right unless you add your own encryption (Apple).
  • EU trader status. Under the EU’s Digital Services Act, every developer says whether they’re a trader, even if they don’t sell in the EU. A trader’s address, phone number and email appear on the app’s App Store page in the EU. The Account Holder or an Admin sets this once for your account, in App Store Connect under Business → Agreements (Apple).
  • Accessibility (optional). You can list the accessibility features your app supports, like VoiceOver or larger text (Apple).

After You Submit

  • Review: see How Long Does App Store Review Take? for timelines and expedited reviews.
  • Rejections: paste Apple’s message from App Store Connect into your project chat, ask the agent to fix it, and submit again. The App Store rejections checklist covers the common reasons.
  • Release: if you chose manual release, click Release This Version in App Store Connect. Your app appears on the App Store shortly after.
  • Updates: make changes in Vibecode, then publish again. For an iOS app, open Publish and click Publish a new version. Vibecode builds your changes, raises the version number (1.0 becomes 1.0.1), keeps your listing and submits the update for review. For a Mobile app, start Expo Launch again with a higher version number. Every update goes through App Review.
  • TestFlight: builds that reach App Store Connect are available in TestFlight, so you can share a beta before release.
  • Keep your membership active: if your Apple Developer membership expires, your apps are no longer available for download, and you can’t submit new apps or updates (Apple).

Why Apps Get Rejected

Apple says that “over 40% of unresolved issues are related to guideline 2.1: App Completeness, which covers crashes, placeholder content, incomplete information, and more” (App Review). Apple’s list of common issues points to these guidelines: For Mobile app projects, run Preflight before you submit. For iOS apps, the agent runs a readiness check before it submits. If Apple rejects your app anyway, paste Apple’s message into your project chat and ask the agent to fix it. The rejections checklist covers more.

Troubleshooting

Asked to sign in with your Apple ID?
  • Vibecode needs a fresh Apple ID sign-in to create a new app in App Store Connect and answer Apple’s privacy questions. Your App Store Connect key can’t do those two steps, and Apple’s sign-ins expire.
  • Open the link the agent sends, sign in, and enter the code Apple sends to your devices. The agent picks the publish back up after you sign in. If it doesn’t, send it a message.
  • If your Apple ID belongs to more than one developer team, pick the team you publish with.
  • Created the app yourself in App Store Connect? Tell the agent. On a first release it still needs your sign-in to confirm the App Privacy answers before it submits.
Apple says you need to accept an agreement?
  • Until the Account Holder accepts Apple’s latest agreements, Apple blocks your team’s App Store Connect key, so Vibecode can’t publish. The Account Holder accepts every pending agreement in App Store Connect under Business → Agreements, and any banner at developer.apple.com/account. If this came up while you connected your Apple account, sign in again on the Connect Apple Account page. If the agent asked during a publish, tell it once you’ve accepted, and it carries on.
App name already taken?
  • Names are unique across the App Store, so a common name may be gone. When the agent creates the app, it adds a short suffix to a taken name and tells you the final name. If you create the app yourself, try a short description after a colon, such as “Mochi: Habit Tracker”.
Expo build failed?
  • Verify your Expo token is valid and hasn’t expired
  • Make sure you’ve accepted all agreements in App Store Connect
  • If Expo Launch opens but can’t continue, complete any Apple authentication or team selection steps there
  • Contact support via Intercom chat in the app if you need help
Version number issues?
  • A new App Store version needs a higher version number than your last approved one. Vibecode raises the build number on every upload.
  • For iOS apps, Publish a new version raises the version number for you. For Mobile apps, enter a higher version number when you start Expo Launch.
Bundle ID errors?
  • Make sure your bundle ID is unique and not already taken
  • Follow the format com.company.appname
  • Use only lowercase letters, numbers, hyphens, and periods
In-app purchases not showing? See the RevenueCat troubleshooting section. The Paid Apps Agreement is the usual cause.

Frequently Asked Questions

Yes, Vibecode does. For an iOS app, Vibecode builds, signs, uploads and submits it for Apple’s review with your Apple Developer account, after one Apple ID sign-in on a new app’s first release. Of the other builders we checked on October 29, 2026, Rork, Replit, FlutterFlow and Adalo upload the build, and you submit it yourself in App Store Connect. With Bolt you run the build yourself, with Base44 you upload the file yourself, and Lovable has no App Store flow. See the comparison.
$99 per year for the Apple Developer Program, which every App Store app needs. Apple takes 15% of sales if you're in the [App Store Small Business Program](https://developer.apple.com/app-store/small-business-program/) (up to $1 million in proceeds a year), or the standard commission above that. App Store submission in Vibecode is included from the Plus plan ($20/month), and builds use credits. See what an Apple Developer account costs.
In our test, the agent had done everything it could on its own 27 minutes after we pressed Send. A new app’s first release then needs a phone number for Apple’s reviewers and your Apple ID sign-in, and for a different app we submitted on October 27, the final build, upload and submission took under 5 minutes. Apple then reviews at least 50% of submissions within 24 hours and 90% within 48 hours (Apple). Apple says apps with little or no review history can take longer (Apple). On your first app, also allow time for Apple to approve your developer account (guide).
No. Apple requires a paid Apple Developer Program membership ($99/year) to publish, even for free apps. Nonprofits, accredited schools, and government entities can request a fee waiver. Your app itself can be free to download.
Not with Vibecode, which builds your app in the cloud. You only need an Apple device to receive two-factor authentication codes. See How to Publish an iPhone App Without a Mac.On a Windows PC? There’s no Xcode for Windows, so a cloud Mac has to do its job.
Yes, on a new app’s first release. Vibecode uploads and submits with your App Store Connect key, but creating the app in App Store Connect and confirming its App Privacy answers need an Apple ID sign-in. The agent sends you a link when it needs one, and Apple sends a code to your iPhone or Mac. Updates to an approved app keep its App Privacy answers.
Yes. Tell the agent which release you want: manual, automatic after Apple approves it, or on a date. With manual release, the approved app waits until you click Release This Version in App Store Connect, or ask the agent to release it.
Yes. Open your project and tap Publish at the top. iOS app projects offer Install and the App Store; Mobile app projects open the same App Store submission steps as the web app.
No. The Vibecode iPhone app has been on the App Store since June 17, 2025 and was never removed. In early 2026 Apple held updates to several vibe coding apps while it reviewed them under App Review Guideline 2.5.2. It approved Vibecode’s next update on March 18, 2026, and Vibecode has shipped regular updates since. See App Store status.
Yes. You describe the app in Vibecode, the agent builds it, and the publish flow handles building, signing, and uploading. You’ll still make the decisions Apple asks for, like your app’s name, price, privacy answers, and age rating.
Yours. Vibecode publishes with your Apple Developer account, so the seller is your legal name (individual accounts) or your organization’s legal name (organization accounts).
Vibecode’s built-in publishing flow is for the Apple App Store. Mobile app (React Native) projects also run on Android: on the Pro and Max plans you can download the code and publish it on Google Play with your own Play Console account ($25 one-time).
Apple tells you which guideline the app didn’t meet in App Store Connect. Fix the issue (paste the message into your project chat and ask the agent), then submit again. If you think the reviewer misunderstood your app, you can reply in App Store Connect or appeal to the App Review Board.

Need Help?

Request support via Intercom chat in the app. You can also join our Discord community. Ready to make the app first? Describe your app and Vibecode builds it.

Apple Developer Account

Create your account and pay the $99 fee

Review Guidelines Checklist

Avoid the most common rejections

App Store Review Time

How long Apple takes and how to speed it up

Best AI Mobile App Builders

Which builders can publish to the App Store
Last modified on November 11, 2026