A Claude Code project reaches the App Store in one of three ways: as a native Swift or SwiftUI app, as a cross-platform app (Flutter or React Native), or as a web app wrapped in a native shell. In every case you need an Apple Developer Program membership (USD 99 per year), a signed archive built on a Mac with Xcode, a complete App Store Connect listing with privacy details, and an app that offers enough native value to pass Guideline 4.2.
On this page
Claude Code can write most of an iOS app, but it cannot press the buttons that Apple reserves for the account holder: enrolling in the Apple Developer Program, accepting agreements, creating the App Store Connect record and answering App Review. The fastest teams split the work clearly. The agent writes and tests code, prepares metadata drafts and scripts the build. A human owns the accounts, the signing identity and the final submission. This guide walks through that path from repository to live listing.
Step zero: know what kind of project you have
Before anything else, look at what Claude Code actually produced. The route to the store depends on it. A native project contains an .xcodeproj or Package.swift and Swift sources; it goes straight into Xcode. A cross-platform project (Flutter, React Native or Expo) has its own build tooling that generates an iOS project for you. A web app (React, Next.js, Vue or plain HTML served from a URL) has no iOS project at all and needs a native container around it.
For the third case, a template such as WebViewGold wraps an existing web app into a native iOS app with push notifications, biometric login and offline handling. Whether wrapping or rewriting is the better choice is covered in our comparison of wrapping versus rewriting an AI-built web app.
Accounts and prerequisites
You need an Apple Developer Program membership, which currently costs USD 99 per year. Enroll as an organization if a company will own the app; this requires a D-U-N-S number and can take several days, so start early. You also need a Mac with a current version of Xcode, because App Store builds must be produced with Apple's toolchain. Claude Code runs comfortably in a terminal on that Mac and can call xcodebuild, xcrun simctl and the test runner directly.
Decide now who holds the signing certificate. We recommend that the agent never sees private keys or App Store Connect API credentials in plain text. Keep them in the macOS keychain or in your CI secret store and let scripts reference them.
The path from repository to submission
- Set the bundle identifier and version. Ask Claude Code to set a reverse-domain bundle ID (for example
com.yourcompany.appname), a marketing version such as 1.0.0 and a build number. The same bundle ID must be registered in your developer account. - Add required assets. An app icon in the asset catalog, a launch screen and correct display name. Missing icons are a common archive validation failure.
- Complete privacy files. Add a
PrivacyInfo.xcprivacyprivacy manifest and the usage description strings (NSCameraUsageDescriptionand similar) for every permission the app requests. - Run the tests and a device build. Have the agent run the unit and UI tests, then install a build on a physical iPhone. Simulators hide performance and permission issues.
- Create the App Store Connect record. Register the app with name, primary language, bundle ID and SKU.
- Archive and upload. Use Xcode's Product, Archive, or a scripted
xcodebuild archiveplus export, then upload the build. - Test through TestFlight. Invite internal testers first, then external testers once the build passes Beta App Review.
- Fill in the listing and submit. Screenshots, description, keywords, support URL, privacy policy URL, age rating and privacy nutrition labels, then submit for review.
Where Claude Code helps most, and where it does not
The agent is strong at the repetitive, error-prone parts: generating the privacy manifest from an inventory of APIs the code actually uses, writing usage description strings that explain the real purpose, drafting store descriptions in several languages, producing screenshot scenes with UI tests and writing a release script. Ask it to list every third-party SDK in the project with its data collection behavior; that list feeds the privacy nutrition labels.
It is weaker at judgment calls that depend on Apple's current review practice. It may claim a feature is "native enough" when a reviewer would disagree, or it may add a login wall without a demo account for the reviewer. Treat its output as a draft. Our App Store submission checklist for Claude Code and Codex projects lists the checks that catch these issues before Apple does.
Passing App Review on the first attempt
Most rejections of agent-built apps fall into a few groups. Guideline 2.1 (App Completeness) catches crashes, placeholder text and broken links. Guideline 4.2 (Minimum Functionality) catches apps that feel like a website in a frame. Guideline 5.1.1 catches missing privacy policies, unclear permission prompts and apps that let users create an account but not delete it in the app. If your app offers third-party social login, check the current rules on offering an equivalent privacy-focused login option such as Sign in with Apple.
Always provide working demo credentials in the review notes, explain any feature that requires special hardware or a paid backend, and make sure the backend is reachable from outside your network. Reviewers test on real devices, often on a network you have not tested.
When to get hands-on help
Publishing is a one-off process for most teams, so the learning curve rarely pays back. AppSubmitter.io takes over the publishing process itself: account setup, listings, screenshots, privacy forms and the communication with App Review, including handling rejections until the app is live. If your team wants to build the release skills internally instead, the Claude Code workshops at neoOutput cover agent-driven build and release workflows. Either way, the goal is the same one we pursue when we build and launch digital products ourselves: an app that is not just accepted, but ready to operate. For the Android side of the same project, see publishing a Claude Code app on Google Play.
Frequently asked questions
Can Claude Code submit my app to the App Store by itself?
Not end to end. It can build, test, upload builds through scripts and prepare metadata, but enrolling in the developer program, accepting agreements and owning the submission remain tasks for the account holder.
Do I need a Mac to publish a Claude Code iOS app?
Yes, or a macOS build service. App Store builds must be produced with Xcode, which only runs on macOS. Hosted macOS CI runners or Xcode Cloud can replace a local Mac.
My Claude Code project is a web app. Can it still go to the App Store?
Yes, through a native wrapper, but it needs real native value such as push notifications, offline handling or device features to pass Guideline 4.2. A plain website in a frame is usually rejected.
How long does the whole process take?
With accounts already in place, a well-prepared app can go from archive to live in a few days. Organization enrollment, first-time rejections and missing assets are what usually stretch it to weeks.