What Apple needs before you start
Apple needs four things from you before a build can reach review: a membership, a signing identity on a Mac, an App Store Connect record, and public pages for privacy and support.
| Item | What Apple asks | Where it goes |
|---|---|---|
| Apple Account | Two-factor authentication on; your legal name in the name fields | developer.apple.com enrolment |
| Membership type | Individual (your name shows as seller) or organization (the legal entity shows as seller) | Enrolment form |
| Organization proof | Dun & Bradstreet's D-U-N-S Number, a public website on the organization's domain, a work email on that domain, authority to sign for it | Enrolment form |
| Build tools | Xcode 26 or later with the iOS 26 SDK, required for uploads since 28 April 2026 | Your Mac |
| Privacy policy URL | Public, and also reachable inside the app | App Store Connect, App Privacy |
| Support URL and contact | A working page and a reviewer contact | Version page and App Review Information |
Keeping the stream alive when the screen locks
Background playback depends on two parts of the build working together: the Background Modes capability with Audio, AirPlay, and Picture in Picture selected, and an audio session set to the playback category. Apple's documentation is plain about the default: without that setup, a locked device or the Silent switch silences the app.
- The capability adds
UIBackgroundModeswith the valueaudioto the app's Info.plist. You see it in Xcode under the target's Signing & Capabilities tab. - The
playbackcategory tells iOS that media is the app's main job, so the Ring/Silent switch does not mute it. - Guideline 2.5.4 allows background services only for their intended purpose. Keep background audio for what it is for: playing the station.
How to confirm it: run the build on a real iPhone, start the stream, lock the phone and wait a minute. Then unlock, open another app, and flip the Silent switch. The stream should keep playing through all three.
The project our panel generates is meant to be opened and signed, not reconfigured. If the background mode looks missing in Signing & Capabilities, send support a screenshot rather than editing the project by hand.
Where App Review looks hardest at a radio app
Radio apps usually stumble on who submitted them, what they stream, or what the reviewer could not hear.
| Guideline | What it means for a station | What to do |
|---|---|---|
| 4.2.6, template apps | Generated or templated apps are refused when anyone but the content's owner sends them in | Submit from the station's own account; never let a vendor submit for you |
| 4.2, minimum functionality | A website wrapped in an app, or a page of links, is not enough | Show live audio, schedule and podcasts in the screenshots and review notes |
| 5.2.3, streaming rights | Apple can ask for proof you are authorized to stream the content | Have your music licensing paperwork ready to attach |
| 2.1, completeness | Placeholder content, dead links or an offline service lead to rejection | Keep the stream live during review; check every URL in the metadata |
| 5.1.1, privacy policy | A policy link is required in the metadata and inside the app | Use a policy that names what the app collects, if anything |
Use the Notes box under App Review Information to say what the reviewer will hear and when. If you broadcast only at set hours, give them, and make sure something plays outside them, such as AutoDJ. Licence documents go in the Attachment section.
The privacy label and the privacy manifest
The App Store privacy label is your declaration, in App Store Connect, of the data the app and every third-party SDK inside it collects. Apple requires it before any new app or update goes in, and you can change the answers later without a new build.
- Collected means sent off the device and kept longer than it takes to answer the request. Data processed only on the phone is not collected.
- Any analytics, advertising or crash SDK you add counts as your collection. Declare it.
- The privacy manifest,
PrivacyInfo.xcprivacy, records the same story inside the build: collected data types, tracking, and the reasons for certain system APIs. - The label, the manifest and your written policy should say the same thing. A mismatch is something a reviewer can find.
The iOS app generated from our panel has no accounts, compiles a privacy manifest that declares no data collected, and comes with a privacy policy URL generated for that app. In that case the App Privacy answer is that the app does not collect data, and the product page shows Data Not Collected.
The submission, in order
The order matters because each step needs something from the one before. Our App Store runbook for the iOS radio app has every screen and button; this is the outline.
- Enrol in the Apple Developer Program with an account the station will keep. Organization approval usually takes longer than individual.
- Install Xcode 26 or later and add the developer account in Xcode's account settings so automatic signing can create certificates.
- Download the generated Xcode project from the panel, open it, choose your team under Signing & Capabilities, and leave the rest of the build settings as they are.
- Create the app record in App Store Connect with the bundle ID from the panel, a name, a primary language and a private SKU.
- Archive for a generic iOS device and distribute to App Store Connect. The app sets
ITSAppUsesNonExemptEncryptionto NO, so the export compliance questions should not hold the build. - Fill the listing: category, availability, App Privacy, description, keywords, support URL, age rating and screenshots.
- Write the App Review notes, untick sign-in required, add the build to the version and submit it for review.
How to confirm each stage: a processed build appears under the version's Build section and Apple emails you; after submission, App Store Connect shows the review status and Apple emails you at each change.
Screenshots: App Store Connect needs at least one image for iPhone with Dynamic Island (medium display), and one for iPad 13-inch if the app runs on iPad, which the generated app does. Up to 10 per size, in JPEG or PNG without transparency.
When review comes back
By Apple's own figures, App Review typically decides 50% of submissions inside a day and 90% inside two days. Incomplete submissions wait longer.
- Questions: answer them in the App Review section of App Store Connect. Many need only a reply or an attachment, not a new build.
- Rejection: the message cites the guideline. Fix that exact point, reply, and resubmit.
- Disagreement: you can appeal once per rejected submission to the App Review Board, with specific reasons why the app complies.
- Deadline: an expedited review can be requested for a critical bug or an event the station is directly part of, such as a launch broadcast.
Our support takes signing errors, missing bundle IDs and rejection messages by 24/7 live chat or ticket. Send the full text of what Apple wrote.
After launch: updates and CarPlay
Most changes a station makes never need a new App Store version. The generated app reads its streams, schedule, podcasts and links from the station's feed, so you change them in the panel and the app follows.
- New build needed: when the panel produces a new iOS project. Repeat the archive, upload and submit cycle under a new version number.
- CarPlay: an audio app in CarPlay needs an entitlement only Apple grants. The team's Account Holder requests it from Apple's CarPlay page; switch it on in the panel only after Apple approves, or automatic signing fails.
- Android too: the same station app ships to Google Play with its own rules, covered in the Google Play guide.
The Premium plan on our radio streaming plans includes your own station app. All the store runbooks, including the TV apps, are on the app publishing page.