From Claude Code to the App Store: A Complete Release Workflow

Claude Code is fast at producing a working iOS app. The App Store does not care how fast you wrote it; it cares whether the binary is signed, complete, honest about data and useful. This article lays out a release workflow in eight phases, with a clear line between what you can delegate to the agent and what a person on your team has to own.

The division of labor at a glance

The pattern: the agent produces artifacts, people own identities, secrets and statements made to Apple.

Phase 1–2: Account and machine

Phase 1, the account. Enroll in the Apple Developer Program (USD 99 per year). Organizations need a D-U-N-S number, and verification can take days to weeks, so start this before the app is finished. Invite team members through App Store Connect roles instead of sharing a login.

Phase 2, the build machine. iOS apps are built and signed with Xcode on macOS. Claude Code runs well on a Mac and can drive xcodebuild, the simulator and Fastlane from the terminal. If your team develops on Linux or in the cloud, you still need a Mac somewhere: a local machine, a hosted macOS CI runner, or a cloud Mac. Apple raises the minimum Xcode and SDK version for uploads periodically, so check the current requirement before you plan the release.

Phase 3–4: Make the project release-ready

Phase 3, project hygiene. Ask Claude Code to audit the project against a written checklist and record the results in the repository. A useful prompt is: "Review this Xcode project for release readiness. Check bundle identifier, version and build numbers, deployment target, app icons in all required sizes, launch screen, Info.plist usage descriptions for every permission requested, and the privacy manifest. List issues; do not fix anything yet." Then fix issues one by one in separate commits.

Phase 4, privacy. Apps and SDKs that use certain "required reason" APIs need a privacy manifest (PrivacyInfo.xcprivacy), and every app needs accurate privacy labels in App Store Connect. The agent can list SDKs and the data they collect, but someone who knows your backend and analytics setup must confirm the answers. If users can create accounts, guideline 5.1.1 expects in-app account deletion – an item worth adding to your CLAUDE.md so the agent never forgets it.

Phase 5–6: Signing and TestFlight

Phase 5, signing. Use an App Store Connect API key and either Xcode's automatic signing or Fastlane match for shared certificates. Keep the key and certificate passwords in your CI secret store, never in the repository and never in a prompt. Claude Code can write the Fastfile and the CI workflow; it should not see the secrets themselves. Background on certificates and profiles is in iOS code signing explained, and automation details are in mobile CI/CD for Claude Code projects.

Phase 6, TestFlight. Upload a build, test internally first, then invite external testers. External TestFlight builds go through a lighter review, which is an early warning system for problems the full review would catch. Have testers follow a written script: install, sign up, core task, purchase if applicable, delete account.

Phase 7: Store listing

Claude Code can generate screenshot automation (Fastlane snapshot with UI tests) and draft the description, keywords and promotional text. Review everything against guideline 2.3 (Accurate Metadata): no features that are not in the build, no pricing claims you cannot keep, no other platforms' names in screenshots. Provide a working demo account in the review notes if the app requires login.

Phase 8: Submission and review

Before you press submit, run this short pre-flight list:

• The build was tested on a physical device, not only the simulator.
• No placeholder text, "lorem ipsum", test buttons or debug menus remain (guideline 2.1).
• The app offers real native value beyond a website (guideline 4.2).
• If you offer third-party login, you comply with the current rules of guideline 4.8.
• Digital goods use In-App Purchase where required (guideline 3.1.1; regional rules differ, so check the current version).
• Review notes explain anything non-obvious: demo credentials, hardware requirements, region locks.

If the app is rejected, paste the rejection text into Claude Code and ask it to map each point to code or metadata changes. Answer the reviewer yourself, briefly and factually. The App Store submission checklist goes deeper on each item.

Where outside help pays off

Most teams handle the code side with Claude Code comfortably and lose time on the parts that are new to them: signing, CI, privacy forms and reviewer back-and-forth. appsubmitter.io covers exactly that gap. It sets up CI/CD, signs and submits your builds in your own developer accounts and guides you through rejections, so ownership stays with you. If your team wants to learn the agent side more systematically, neooutput runs hands-on trainings on agentic coding and app development. For details on the coding phase itself, see building an iOS app with Claude Code.