• English

    • Publish on the App Store

    Before You Start

    Complete TestFlight / App Store packaging, create the matching app record in App Store Connect, and upload a build. Test the exact release candidate on a real device before selecting it for review.

    As of April 28, 2026, uploads must use Xcode 26 or later and the iOS 26 / iPadOS 26 SDK or later. Check Apple’s upcoming requirements again before every release.

    1. Complete Account and Commercial Setup

    • Keep the Apple Developer Program membership active.
    • Accept current agreements in the Apple Developer account and App Store Connect.
    • For paid apps or in-app purchases, complete the paid-app agreement, tax forms, and banking information.
    • Confirm that the seller identity is correct. Individual enrollment displays the person’s legal name; organization enrollment displays the legal entity name.
    • Assign the people preparing and submitting the app the minimum necessary App Store Connect roles.

    2. Create or Verify the App Record

    In App Store Connect, create an app record before the first MeDo upload.

    PropertyRequirementGuidance
    PlatformsRequiredSelect iOS and any other supported Apple platforms.
    NameRequired2–30 characters. Localize it for each storefront where appropriate.
    Primary languageRequiredUsed when a storefront lacks localized metadata.
    Bundle IDRequired and effectively permanentMust exactly match the MeDo build. It cannot be changed after a build is uploaded.
    SKURequired and permanentInternal identifier; customers do not see it.
    User accessRequiredLimit the record to the appropriate App Store Connect users when necessary.

    The App Store display name does not need to match the iPhone home-screen name exactly, but it must accurately represent the same app. The Bundle ID must match exactly.

    3. Prepare the Product Page

    Go to the app’s version page and complete the primary-language metadata. Add localized metadata rather than using machine-translated text for important markets.

    App Store Connect — Fill in App Information

    FieldRequirementCurrent guidance
    NameRequired2–30 characters. Do not add unverifiable claims or keyword stuffing.
    SubtitleOptionalUp to 30 characters; summarize the app’s main value.
    DescriptionRequiredUp to 4,000 characters; explain the real functionality and any subscriptions or paid features.
    KeywordsRequired for iOSUp to 100 bytes, comma-separated. Avoid duplicates already covered by the name or category.
    Promotional textOptionalUp to 170 characters and editable without a new version review.
    Primary categoryRequiredChoose the category that best matches the app’s main purpose.
    Secondary categoryOptionalAdd only when it accurately represents the app.
    Support URLRequiredMust lead to functioning support or contact information.
    Marketing URLOptionalProduct or campaign website.
    CopyrightRequiredUse the current year and rights-holder name, for example 2026 Example, Inc.
    ScreenshotsRequired1–10 screenshots per required device set. Show the actual app; localize when the UI or claims differ.
    App previewsOptionalUp to three videos per supported device size and language.
    App iconRequired in the buildProvide the 1024 × 1024 marketing icon through the app asset catalog; no transparency.
    Version and What’s NewRequired for updatesVersion must match the build. Describe meaningful user-facing changes.

    Screenshots must represent the current app experience. If the interface is the same across device sizes, App Store Connect can scale the highest-resolution required screenshots to smaller sizes.

    4. Privacy and Platform Compliance

    Privacy Policy and App Privacy

    Every iOS app needs a public privacy-policy URL in App Store Connect and an easily accessible privacy-policy link inside the app. The policy must match the released build, including third-party SDK behavior.

    In App Privacy, declare:

    • Every data type collected by the app or its third-party partners
    • Whether each data type is linked to the user
    • Whether it is used for tracking
    • Collection purposes such as app functionality, analytics, personalization, or advertising
    • A user-privacy-choices URL when you provide a web page for access, correction, consent withdrawal, or deletion requests

    Do not publish an unchanged template. Customize any MeDo-generated draft with the real app owner, contact method, collected data, purposes, processors, retention, deletion process, and applicable regions.

    Permissions, Tracking, and Accounts

    • Add clear usage descriptions for camera, microphone, photos, location, contacts, Bluetooth, and other protected resources actually used by the app.
    • Request permissions only when the related feature is invoked, and provide a reasonable alternative where possible.
    • If data is used to track users across other companies’ apps or websites, implement App Tracking Transparency before accessing IDFA or performing tracking.
    • If the app supports account creation, users must be able to initiate account deletion inside the app.
    • If a third-party or social login is used for the user’s primary account, check whether App Review Guideline 4.8 requires an equivalent privacy-preserving login option such as Sign in with Apple.

    SDK Privacy Manifests and Required-Reason APIs

    You are responsible for all third-party code in the app. Before uploading:

    • Review Xcode’s privacy report and the data use of every SDK.
    • Ensure SDKs on Apple’s list include the required privacy manifest and, for binary dependencies, a valid signature.
    • Declare approved reasons for covered required-reason APIs.
    • Remove unused SDKs and permissions.

    Encryption and Export Compliance

    Answer App Store Connect’s encryption questions for the build. Even apps that only use standard operating-system encryption must make the correct determination. If no documentation is required, set the appropriate Info.plist value so the same questions do not recur. If documentation is required, obtain clearance and attach it before TestFlight Beta App Review or App Review.

    5. Complete App-Level and Regional Declarations

    Global or Feature-Dependent

    DeclarationWhen it applies
    Updated age ratingRequired for every app. Answer the current questionnaire based on content, user-generated content, messaging, advertising, gambling, medical information, and parental controls.
    Content rightsRequired when the app displays, streams, or accesses third-party content.
    Regulated medical-device statusRequired for relevant Medical or Health & Fitness apps distributed in the EU/EEA, UK, or U.S.
    Digital Services Act trader statusEvery developer must declare status. Traders distributing in the EU must provide verified contact details that Apple displays on the product page.
    In-app purchases and subscriptionsSubmit products needed by the app, make them visible and testable, and explain non-obvious flows in Review Notes.
    Game CenterInclude the entitlement and complete App Store Connect configuration when the app offers Game Center features.

    Country and Region Examples

    Regional requirements apply only when you select the relevant storefront and app type. Verify them in App Store Connect instead of copying another app’s checklist.

    • China mainland — A valid ICP filing number is required for apps made available there. Games need the applicable publication approval number and supporting documents. Additional licenses may apply to news, books, audio/video, religion, finance, healthcare, mapping, and other regulated content. Organizations based in China mainland must also confirm identity information that Apple displays. A software copyright certificate may be needed for local filing or industry processes, but it is not a universal App Store requirement outside China.
    • European Union — Declare DSA trader status. If you are a trader, verify the address, phone number, and email Apple will display.
    • Republic of Korea — Some games require a GRAC rating-classification number. Organization developers may have additional business-contact requirements.
    • Vietnam — Games may require a game-license number and URL.
    • Brazil and other storefronts — Tax, content, or commercial documentation can affect availability, especially for paid distribution.

    6. Supply Review Information

    Fill in review information step 1 Fill in review information step 2 Fill in review information step 3

    FieldRequirementGuidance
    BuildRequiredSelect the processed, fully tested MeDo build.
    Review contactRequiredProvide a monitored name, phone number, and email address.
    Sign-in informationConditionalIf login is required, provide a durable demo account with all reviewable features enabled.
    Review NotesStrongly recommendedExplain navigation, non-obvious features, permissions, hardware needs, sample QR codes, region restrictions, and in-app purchases.
    AttachmentsConditionalProvide supporting documents or videos when Apple cannot reproduce a workflow. Do not include unnecessary secrets.

    Keep backend services and the demo account working throughout review. Remove placeholders, test banners, broken links, empty pages, and disabled production features.

    7. Pre-Submission Checklist

    • The release build launches and completes every core flow on supported devices.
    • Bundle ID, version number, and build number are correct.
    • Xcode 26 / iOS 26 SDK or later was used.
    • All URLs use HTTPS and work without employee-only access.
    • Product-page metadata and screenshots match the build.
    • Privacy policy, App Privacy answers, permission prompts, and SDK behavior agree.
    • Account deletion, login, purchases, restore purchases, and subscriptions work where applicable.
    • Age rating, content rights, encryption, DSA, medical, and regional declarations are complete.
    • Demo credentials, review notes, and any required hardware or sample data are available.
    • TestFlight feedback and crash reports have been addressed.

    8. Submit and Release

    1. Add the version and build to the submission.
    2. Add any in-app purchases, subscriptions, custom product pages, or other review items that must ship together.
    3. Resolve every warning shown by App Store Connect.
    4. Submit for review and monitor App Store Connect messages.
    5. If Apple asks a question, reply with exact reproduction steps and supporting evidence.
    6. If rejected, fix the cited issue rather than submitting the same build with only a note unless Apple explicitly asks for clarification.

    Choose the release mode deliberately:

    • Automatic — Releases after approval.
    • Manual — You release after approval; useful for coordinated launches.
    • Scheduled — Releases no earlier than the selected date after approval.
    • Phased release — Gradually rolls an update to existing users; it does not replace monitoring or rollback planning.

    After release, monitor crashes, reviews, support requests, subscription and purchase status, and regional availability. Keep privacy declarations and support URLs current when the app or its SDKs change.

    Official Apple References