Guides ChatGPT published aug 30, 2026
In this guide, you will learn how to take a SwiftUI app from Xcode to App Review with ChatGPT Work and App Store Connect. You will prepare the listing, upload the build, set a one-time price, and submit it without hunting through every screen.
You will move a finished SwiftUI app from an Xcode archive into App Store Connect, complete its product page, set a one-time price, and submit it to App Review.
Turn the workflow into a reusable release checklist for future versions. Keep the listing assets in one folder, increment the version and build numbers, create a fresh archive, upload it, and ask Codex to stop before the final App Review action.
Prepare the next App Store release for [APP NAME]. Review the current listing assets, update only the fields that changed, verify the version and build numbers, archive and upload the new build, and return a final submission checklist. Stop before Add for Review or Submit for Review.Use the returned checklist to verify the listing, build, pricing, and review answers before you submit.
Start with a working SwiftUI app. If you still need to build, test, and prepare yours in Xcode, follow Part 1 (https://app.therundown.ai/guides/build-test-publish-ios-app-without-leaving-codex) first.
Next, gather the product page assets. Ask Codex to run the app in the simulator, capture the main workflow, and draft the copy and screenshots for App Store Connect.
Prepare everything I need for this app's App Store listing. Open the simulator and capture six to ten screenshots that show the main workflow with safe demo data. Draft the description, subtitle, and keywords. Use my existing privacy-policy and support URLs, plus [MARKETING_URL] if available. Stop before uploading or submitting anything.We used this workflow for OurDays, a weekend-planning app. The finished asset set included simulator screenshots, a description, keywords, and the URLs needed for the listing.
Review the screenshots at full size before uploading them. Remove private names, contact details, notifications, or real account data.
The app needs an App Store Connect record before Xcode can upload it. In our test, Xcode offered to create the record from the app name, SKU, primary language, and bundle ID. Review those identity fields before continuing.
Open the project in Codex and give it a direct upload instruction:
Upload this app to App Store Connect for the first time. Create the build, archive it in Xcode, and push the first build. Stop if any app identity, signing, version, or upload decision needs my approval.Codex created the build and opened Xcode's Archives organizer. From there, choose Distribute App > App Store Connect > Next. Keep Xcode visible so you can approve system prompts and inspect the archive before distribution.
Several names were already taken. Codex updated the app identity to OurDays Planner and completed the upload. If you change the identity during this step, recheck the app name, bundle ID, App Store record, version, and build number before trying again.
Open the Browser panel in Codex and sign into App Store Connect. Select the app, open version 1.0, and ask Codex to use the assets from Step 1:
In App Store Connect, fill in the description and the other listing fields, then upload the screenshots and other assets we prepared. Ask before changing pricing, release behavior, review answers, or any private contact information.Codex filled the description, keywords, support URL, and screenshots. Read every entry and correct anything that exceeds its character limit or does not match the app.
Choose whether the app should release automatically after approval or wait for a manual release. We chose automatic release for OurDays.
Pro tip: Sign into App Store Connect in Codex's built-in browser before starting the form. General computer use wandered in our test; the signed-in browser filled the listing and uploaded screenshots much faster.
Open Pricing and Availability, confirm the app's tax category, and add its price. We used a $2.99 U.S. base price for OurDays. If you charge for the app, make sure Apple's Paid Apps Agreement (https://developer.apple.com/help/app-store-connect/manage-app-pricing/set-a-price/) has been accepted before submission.
Return to version 1.0 and finish the required review fields:
Click Add for Review. App Store Connect caught two missing sections in our test: Age Rating and Content Rights. We completed them for the scheduling app, returned to the submission, and clicked Submit for Review.
The successful result is a submitted item waiting for Apple to review it. It is not approval or a live App Store listing.
Keep going
Members get all guides, courses, live sessions, and $1,000+ in partner perks.