A repeatable workflow for publishing an iOS app through App Store Connect. It covers a first release and the checks to repeat for later versions.
Last verified: 14 November 2026. Apple changes App Store Connect screens, submission requirements and device specifications. Use the linked Apple documentation as the authority when a field or workflow changes.
This guide does not guarantee approval. It is a release procedure, not a substitute for Apple's current App Review Guidelines.
At a glance
- Prepare the app, Apple Developer account and release assets.
- Create the App Store Connect app record.
- Archive and upload a release build.
- Complete the product page and compliance information.
- Test the exact uploaded build through TestFlight.
- Submit the version for App Review.
- Release the approved version and verify it is live.
Allow time for agreements, build processing, beta testing and App Review. A successful upload is not the same as an approved or publicly available app.
1. Prepare before opening App Store Connect
Have these ready:
- An Apple Account with two-factor authentication enabled, and you must be the legal age of majority in your region.
- An active Apple Developer Program membership and App Store Connect access. The programme costs US$99 per membership year, with local-currency pricing where available; eligible nonprofits, accredited educational institutions and government entities can request a fee waiver. The waiver is for qualifying organisations only—not individuals or sole proprietors—and is unavailable if the organisation has signed the Paid Apps Agreement or sells digital goods or services through its apps.
- The correct enrolment type. An individual or sole proprietor account displays the individual's legal name as the seller. An organisation account displays the legal entity name and requires a legal entity, a D‑U‑N‑S Number (except eligible government entities), a work email on the organisation's domain, a public functional website on that domain and an enrollee with legal authority to bind the organisation to Apple's agreements. D‑U‑N‑S numbers are free in most jurisdictions.
- Identity verification and the membership agreement completed. Apple verifies organisation details before allowing the membership purchase; allow time for this before planning a launch.
- The correct developer team and required account agreements accepted. If you will sell a paid app or in-app purchases, accept the Paid Apps Agreement and complete the required tax and banking information before expecting payments.
- The final app name and a unique bundle identifier.
- A release version and build-number plan.
- A working release scheme and signing configuration in Xcode.
- An app icon configured in the Xcode asset catalog. For iOS, include the 1024 × 1024 App Store icon image; Xcode can generate the required system variations from a single high-resolution source.
- Genuine screenshots from the current app.
- A public support page and privacy policy URL.
- Accurate information about data collection, analytics, advertising and third-party SDKs.
- A reviewer contact and working demo account if the app requires sign-in.
- In-app purchase and subscription configuration, if applicable.
Lock the bundle identifier early. It identifies the app and must match the App Store Connect record and Xcode target. Do not create a second identifier to work around a naming mistake.
Current Apple build requirements
As of 13 November 2026:
- Since 28 April 2026, apps uploaded to App Store Connect must be built with Xcode 26 or later, using an SDK for iOS 26 or later (or the corresponding current platform SDK for other Apple platforms).
- Since 9 September 2026, iOS and iPadOS apps uploaded to App Store Connect must target iOS 13 or later.
- The current published minimum is Xcode 26 with an iOS 26 (or corresponding platform) SDK. Use a currently supported Xcode release and recheck Apple's requirements immediately before uploading; do not treat a future Xcode version or beta SDK as accepted unless Apple lists it.
These are different settings: the SDK/Xcode requirement concerns the tools used to build the upload; the deployment target controls the oldest OS version the app supports. Check Apple's upcoming requirements before each release.
2. Create the App Store Connect app record
- Open Apps.
- Select the Add (+) button and choose New App.
- Select the platform.
- Enter the app name and primary language.
- Select the registered bundle ID.
- Enter an internal SKU for your own records.
- Choose the user access setting.
- Create the app record.
Apple requires an app record before you can upload a build. The Account Holder must have accepted any required agreements before creating the record.
Check immediately:
- The app name is correct.
- The bundle ID matches the Xcode target exactly.
- The platform and primary language are correct.
- The SKU is recorded somewhere retrievable.
- The record belongs to the intended developer team.
Official instructions: Add a new app.
3. Archive and upload the release build
In Xcode:
- Open the correct project and release scheme.
- Select a generic iOS device destination suitable for archiving.
- Confirm the bundle identifier, version and build number.
- Confirm the correct developer team and distribution signing configuration.
- Select Product → Archive.
- Wait for the archive to complete.
- In Organizer, select the archive and choose Distribute App.
- Choose App Store Connect and follow the validation and upload steps.
- Wait for Apple's build processing to finish.
Use a version number that reflects the release and increment the build number for every uploaded binary. The marketing version is the version users see; the build number distinguishes uploads for that version.
After upload:
- Confirm the build appears under the correct app and platform.
- Wait until processing finishes.
- Resolve processing warnings or invalid-binary errors.
- Confirm the processed build is the one you intend to test and submit.
Use the current Xcode distribution workflow. Do not switch upload tools to work around a signing or archive problem without understanding the cause.
Official workflow: App Store Connect workflow.
4. Complete the App Store product page
Open the app version under the correct platform in App Store Connect.
Complete the app information and version metadata with accurate, localised content where needed:
- App name: up to 30 characters.
- Subtitle: up to 30 characters; a concise explanation of the app.
- Promotional text: up to 170 characters. Optional and editable without submitting a new app version.
- Description: up to 4,000 characters; explain the real functionality and audience.
- Keywords: up to 100 bytes in total. Separate terms with commas; avoid duplicate words, category names, irrelevant terms and competing app names.
- What's New: explain meaningful changes in this version. This field is not available for the first app version and is required for subsequent versions.
- Support URL: required. Provide a working support page with actual contact information (such as a legal address, email address or telephone number, as applicable) so users can reach you about app issues, feedback and feature requests.
- Marketing URL: optional.
- Primary category: required; select the category that best describes the app. A secondary category is optional.
- Copyright: required; enter the year and name of the person or entity that owns the app's exclusive rights. App Store Connect adds the copyright symbol.
- Any other required app information shown for the platform.
- Screenshots: required; show the actual current app and follow the current device-size specifications.
- App previews: optional short videos; you can provide up to three for each localisation and device size.
Do not make claims about features, pricing, awards or device support that the submitted build cannot substantiate.
Screenshots
Capture the release build and check Apple's current screenshot specifications before exporting assets.
As currently specified, provide at least one screenshot for an iPhone with Dynamic Island (medium display). If the app supports iPadOS, provide at least one screenshot for the 13-inch iPad display. You can upload up to 10 screenshots per device size. App Store Connect can scale screenshots down when the interface is consistent, but this does not remove the required device-size coverage. Check the live specifications for accepted pixel dimensions, orientation and any platform-specific requirements before exporting. Screenshots must not contain transparency.
Before upload:
- Capture genuine screens from the current release build.
- Make sure text is legible at store-page size.
- Remove debug overlays, placeholder content and personal information.
- Check that the images represent the actual submitted version.
- Confirm there are no prohibited claims or misleading UI.
5. Complete privacy, age rating and compliance
These declarations must describe the app as submitted, including the behaviour of integrated services.
App Privacy
In App Store Connect, open App Privacy.
- Add the public privacy policy URL in App Store Connect.
- Make the privacy policy easy to find inside the app as well. The store listing URL alone is not enough.
- Determine whether the app or any third-party partner collects data.
- Declare every applicable data type.
- Answer the purpose, linkage and tracking questions accurately.
- Review the product-page preview.
- Publish the privacy responses.
Include data collected by analytics, crash reporting, advertising, attribution, authentication, payment and support SDKs. Do not answer only for code written by you. Apple's privacy answers are provided at app level and must cover the app's practices across its platforms. If the app or its SDKs change, review the declaration again.
The privacy policy URL is required. A privacy choices URL is optional. Keep the policy accurate, publicly reachable and consistent with the app's actual behaviour. The App Privacy answers are separate from the privacy policy: both must be accurate.
Privacy manifests and required-reason APIs
App Store privacy declarations are not the only privacy requirement. Check whether your app or any included third-party SDK must provide a privacy manifest, declare approved reasons for required-reason APIs, or include a privacy manifest for a listed SDK. Review Apple's current privacy manifest and SDK requirements and required-reason API list. Validate the final archive, not just your source project. These requirements depend on the APIs and SDKs your app actually uses.
Official instructions: Manage app privacy.
Age rating
Complete the current age-rating questionnaire in App Store Connect. Apple's updated age-rating questions took effect in 2026; developers were required to provide responses by 31 January 2026 to avoid interruptions when submitting updates. Check the current rating shown for the app and answer the latest questions rather than reusing an old rating.
Tracking and App Tracking Transparency
If the app or an included SDK tracks people across other companies' apps, websites or offline properties for advertising or measurement, or shares data with a data broker, request permission using Apple's App Tracking Transparency (ATT) framework before tracking. Do not track when permission is denied, use fingerprinting as a workaround, or make unrelated app functionality conditional on agreeing to tracking. Your responsibility includes third-party SDKs.
Official guidance: User Privacy and Data Use and App Tracking Transparency.
Other compliance
Depending on the app, also check:
- Content rights for third-party material.
- Export compliance and encryption questions.
- Pricing and availability.
- Paid Apps Agreement, tax forms and banking details if you sell apps or in-app purchases.
- EU Digital Services Act trader status: all developers must declare trader or non-trader status in App Store Connect. If distributing in the EU as a trader, Apple must verify and display the required trader contact information. Complete the declaration before submission; do not assume this only applies to organisations.
- Digital Goods and Services questionnaire: if this section appears in App Store Connect, complete it to declare how users pay for or access digital goods and services. If it does not appear, no action is required. Review your answers carefully: choices for the European Union are locked for 12 months after submission.
- Regulated medical device status: if your app meets Apple's criteria for a regulated medical device in the EU/EEA, UK or US, complete the required status declaration and any supporting use statement or safety information.
- Account deletion: if users can create an account, provide a way to initiate account deletion from within the app. Explain any legally required retention separately; simply disabling an account is not deletion.
- Sign in with Apple: check whether the guideline requires an equivalent privacy-preserving login option when you use a third-party or social login provider. Exceptions apply.
- In-app purchases and subscriptions: configure products, pricing, availability and review information. Digital features or content unlocked in the app generally need Apple's in-app purchase system unless a specific guideline exception applies. Submit applicable IAP products for review with their required screenshots and review notes; an app binary being approved does not automatically approve every product. Test purchases and restore flows in Sandbox/TestFlight. Subscription screens must clearly disclose the subscription name, duration, price and what the user receives; explain renewal and cancellation, and provide ongoing value for auto-renewing subscriptions.
- Any additional declarations presented by App Store Connect.
Do not guess an answer to get past a form. Resolve uncertainty before submission.
6. Prepare App Review information
Open App Review Information for the version.
Provide:
- A working contact name, email address and phone number.
- A concise explanation of the app's concept, features and intended audience.
- Demo credentials if account-based features require sign-in.
- Instructions for features hidden behind onboarding, location, hardware or other requirements.
- Sample data or setup information needed to test the app.
- Relevant documentation for regulated functionality, where required.
For updates, explain what changed and where reviewers can find significant new features. List the device models and operating-system versions you tested.
If login is required, reviewers must be able to access the app. Do not provide credentials that expire before review or depend on an approval flow you cannot reliably complete. Keep required backend services available during review. If the app has multiple account types or subscription states, provide working credentials and explain how to reach each relevant state. For auto-renewable subscriptions, Apple specifically asks for a demo account with an expired subscription so reviewers can examine the full purchase flow. Explain external services, required hardware, regional differences and non-obvious functionality in the review notes.
Read Apple's App Review Guidelines before submission, particularly the sections relevant to functionality, privacy, payments, user-generated content and account access.
Apple's review preparation guidance: Provide information for a complete review.
7. Test the exact uploaded build with TestFlight
A successful Xcode run does not prove that the uploaded release is ready.
- Open the app in App Store Connect.
- Select TestFlight.
- Wait for the uploaded build to finish processing.
- Add internal testers or configure external testing as appropriate.
- Complete any beta review steps shown for external testing.
- Install the uploaded build through TestFlight.
- Test the full release path on real supported devices.
Internal testing supports up to 100 App Store Connect users; external testing supports up to 10,000 testers per app. The first external build submitted for testing requires TestFlight App Review. TestFlight builds are available for up to 90 days. Treat beta review as separate from App Store review: TestFlight approval does not approve the public release.
Minimum checks:
- Fresh install and first launch.
- Upgrade from the previous version, if one exists.
- Core user journeys.
- Permissions granted and denied.
- Network loss and recovery.
- Purchases, restore and subscription states, if applicable.
- Ads and consent flows, if applicable.
- Account access, logout and deletion, if applicable.
- Accessibility, text scaling and supported screen sizes.
- No test data, debug controls or placeholder copy in the release.
Record the build number tested. If you upload a replacement build, repeat the relevant checks against that build.
8. Submit the version for App Review
Before submission, verify:
- The correct app and platform are selected.
- The correct processed build is attached to the version.
- Required metadata is complete.
- Screenshots match the submitted app.
- App Privacy responses are accurate and published.
- The current age rating and compliance declarations are complete.
- Review notes and credentials work.
- Pricing and availability are correct.
- No unresolved submission errors remain.
Then complete both submission actions:
- Select Add for Review and add the version to an existing draft submission or create a new submission.
- Review the submission contents.
- Select Submit for Review.
Add for Review does not submit the app. It moves the item into a ready-to-submit state. The review starts only after you explicitly submit the draft.
Official instructions: Submit an app.
9. Handle review and release
Monitor the submission status in App Store Connect.
- Waiting for Review: Apple has received the submission.
- In Review: review is underway.
- Rejected / Unresolved Issues: read the complete message and identify whether the correction requires metadata, settings or a new binary.
- Accepted: the item has been accepted; confirm the release status and selected release method.
If rejected:
- Read the full resolution-centre message.
- Reproduce the reported issue.
- Fix the underlying cause.
- Upload a new build if code or binary changes are required.
- Update review notes to explain the correction.
- Resubmit.
Choose the available release method: manual release, automatic release or automatic release no earlier than a selected date. For eligible version updates, you can also choose a phased release; this distributes automatic updates over seven days to a percentage of users. Phased release is not available for the first version and does not prevent users from manually downloading the update. After approval and release, verify the public App Store product page and install the public version. Apple says it can take up to 24 hours for an app to appear across all selected storefronts. Monitor crash reports, ratings and reviews, support requests, sales and subscription performance; do not treat acceptance as proof that the app is already visible.
Official overview: Publishing an app on the App Store.
Release checks to repeat
Use these checks before each release.
- Correct Apple Developer team and App Store Connect app record
- Bundle identifier matches the Xcode target
- Xcode and SDK meet Apple's current upload requirement
- Deployment target checked against current platform requirements
- Marketing version and build number checked
- Release archive built and uploaded
- Build processing completed
- Exact uploaded build tested through TestFlight
- Description and What's New checked
- Screenshots match the current app, required device sizes and current specifications
- App name, subtitle, promotional text, description, keywords, categories and copyright are accurate and within field limits
- Support URL works and privacy policy is accessible from the listing and within the app
- App Privacy declarations reviewed and published
- Current age-rating questionnaire completed, including current content descriptors and capabilities
- Privacy manifests, required-reason API declarations and third-party SDK requirements checked where applicable
- Account deletion and Sign in with Apple requirements checked where applicable
- Export, content-rights, IAP and other compliance declarations complete
- Pricing and availability checked
- Review contact and demo credentials verified
- Review notes explain non-obvious functionality
- Correct build attached to the version
- Added for Review, then explicitly Submitted for Review
- Review outcome checked
- Release method confirmed
- Live App Store listing and public install verified
Common mistakes
- Uploading with the wrong bundle ID or developer team.
- Forgetting to increment the build number.
- Building with an Xcode or SDK version that no longer meets Apple's upload requirement.
- Assuming a successful upload means processing is complete.
- Declaring privacy only for your own code and ignoring SDK partners.
- Leaving the updated age-rating questions incomplete.
- Using screenshots from an old interface or unsupported device size.
- Providing reviewer credentials that do not work.
- Leaving a backend, purchase flow or test account unavailable during review.
- Clicking Add for Review but not completing Submit for Review.
- Assuming approval means the app is already visible to every user.
Official sources
- Apple Developer Program enrolment and fees
- Apple Developer Program fee waivers
- Upcoming Apple submission requirements
- App Store Connect workflow
- Add a new app
- Manage app privacy
- User Privacy and Data Use
- App Tracking Transparency
- EU Digital Services Act trader requirements
- Digital Goods and Services questionnaire
- Regulated medical device status
- Submit an In-App Purchase for review
- Privacy manifests
- Required-reason APIs
- Required, localizable and editable app properties
- App information and metadata
- Add an app icon
- Configure your app icon using an asset catalog
- Set an app age rating
- TestFlight overview
- Provide information for a complete review
- Pricing and availability
- Screenshot specifications
- App Review Guidelines
- Provide information for a complete review
- Submit an app
- Publishing an app on the App Store
Maintenance rule: check Apple's official requirements before each release. If Apple changes a requirement or workflow, update this guide and its verification date before reusing it.