• English

    • iOS Publishing Guide

    Overview

    This guide combines the MeDo packaging workflow with Apple’s current international distribution requirements. It covers the path from first device testing to App Store release, including the decisions, account setup, signing, privacy declarations, regional compliance, beta testing, and review information that are easy to miss.

    Apple changes submission requirements over time. The requirements in this guide were verified on July 20, 2026. Before a production submission, also check Apple’s upcoming requirements and the App Review Guidelines.

    Current Submission Baseline

    As of April 28, 2026, iOS and iPadOS apps uploaded to App Store Connect must be built with Xcode 26 or later and the iOS 26 / iPadOS 26 SDK or later. Your deployment target can still support older operating-system versions when the app and its dependencies allow it.

    Apple’s updated age-rating system is also in effect. Complete the current age-rating questionnaire in App Store Connect instead of relying on an older rating carried over from a previous version.

    Prepare the App

    1. Build and Verify in MeDo

    • Choose the app type — Create or open the iOS-capable project in MeDo.
    • Complete the core experience — Remove placeholder content, unfinished controls, sample accounts, and dead links.
    • Test on a real device — Verify sign-in, permissions, deep links, purchases, notifications, camera/photo access, background behavior, and poor-network handling where applicable.
    • Check the Bundle ID — Treat it as permanent. The App Store Connect app record and uploaded build must use the same Bundle ID.
    • Audit third-party SDKs — Record what every SDK collects and why. Listed SDKs may require privacy manifests and signatures, and required-reason APIs must declare an approved reason.

    2. Prepare the Apple Account

    Public App Store, TestFlight, and Ad Hoc distribution require an active Apple Developer Program membership. Enroll as the entity that should appear as the seller:

    • Individual — The person’s legal name appears as the seller.
    • Organization — The legal entity name appears as the seller; enrollment normally requires a D-U-N-S Number and authority to bind the organization.

    Accept current agreements in the Apple Developer account and App Store Connect. Paid apps and in-app purchases also require the appropriate paid-app agreement, tax forms, and banking details.

    Choose a Distribution Route

    RouteBest forMembershipApple reviewAudience and limits
    Personal Team / local debugDevelopment on your own devicesFree Apple AccountNoUp to 3 devices and 3 installed apps per device; provisioning expires after 7 days
    Ad HocKnown devices, demos, and acceptance testingPaid programNo beta reviewRegistered UDIDs only; up to 100 devices per product family per membership year
    TestFlight internalTeam testingPaid programNormally no TestFlight reviewUp to 100 App Store Connect users; builds remain testable for 90 days
    TestFlight externalCustomer or public betaPaid programBeta App Review may be requiredUp to 10,000 testers by email or public link; builds remain testable for 90 days
    Public App StoreDiscoverable public releasePaid programApp ReviewCountries and regions selected in App Store Connect
    Unlisted AppLimited audience with a direct App Store linkPaid programApp Review plus an unlisted-distribution requestAnyone with the link; not shown in search, charts, or categories
    Custom AppSpecific organizations using Apple Business Manager or Apple School ManagerPaid programApp ReviewPrivate distribution to named organizations

    MeDo directly documents local debug, Ad Hoc, TestFlight, and public App Store packaging. Unlisted and Custom App distribution are configured in App Store Connect after you have a review-ready build.

    Follow the Guide

    1. Choose a packaging and distribution route.
    2. For Local Debug, generate the unsigned IPA in MeDo, then sign and install it with Sideloadly or AltStore Classic. Use this only for short-lived development testing.
    3. For Specified Device Install, configure Apple authorization, register every target device, and create an Ad Hoc package.
    4. For Public Release / Invite Testing, configure Apple authorization, upload the build, and run the TestFlight test.
    5. When the release candidate is ready, prepare the App Store product page, privacy information, compliance declarations, and review submission.

    For most apps, the safest sequence is:

    Local device testing → TestFlight internal → TestFlight external → staged or manual App Store release

    Use Ad Hoc when you must test on a small, known device list without TestFlight review. Use an unlisted or Custom App instead of Ad Hoc when the audience needs a durable production installation.

    Official Apple References