Guide
How to schedule an App Store release
Choose automatic, manual, or after-approval release timing for your App Store version, then pair it with phased release when you want a safer rollout.Approval day should not be the first time you decide how the version goes live. App Store Connect lets you choose automatic, manual, or after approval (sometimes framed as releasing immediately when approved). This guide explains the tradeoffs, how to set timing before review finishes, and how Helm releases keep the choice visible next to your launch checklist.
The three release behaviors
Automatic (scheduled)
You pick a date and time in the future. After App Review approves the version, Apple holds it until that moment, then releases. Use this when marketing, docs, and partner comms share a fixed launch window.
Watch time zones. Confirm the schedule in the territory context you care about, and give yourself buffer if approval slips.
Manual
The version waits in a pending developer release state after approval. You press release when the team is ready. Best when:
- You need a final QA pass on the live binary state
- Press embargos or storefront moments are not date-certain
- You might still reject and replace before customers see it
Manual is flexible. It is also easy to forget on a Friday. Put a calendar reminder on the owner, not “the team.”
After approval (immediate)
When Apple approves, the version becomes available without another click. Ideal for hotfixes and small updates where speed beats ceremony. Riskier for large launches that need coordinated messaging.
Decide this before you submit. Changing your mind mid-review is possible in many cases, but it is a poor time to invent policy.
Pick based on risk, not habit
| Situation | Prefer |
|---|---|
| Hotfix for an active incident | After approval |
| Marketed 1.0 or major rebrand | Automatic date or manual with a war room |
| Large migration or risky refactor | Manual or automatic, plus phased release |
| Routine bug fix | After approval or short automatic window |
If you need both timing control and blast-radius control, combine a release type with phased release. Timing answers when. Phased release answers how many automatic updaters get it first.
Pair with phased release
Phased release rolls the update out to a percentage of automatic updaters over seven days. Manual updaters can still grab the new version from the product page immediately. Read manage a phased release for pause and release-to-all tactics.
Set phased release intent before approval day so you are not debating rollout policy while the version flips to Ready for Sale.
Operational sequence
- Freeze scope and write What’s New.
- Select the build and finish compliance and review notes.
- Choose automatic, manual, or after-approval in the version.
- Decide whether phased release is on.
- Submit for review (submit guide).
- Monitor approval, then execute the release action your mode requires.
- Watch crashes, reviews, and support for the first day.
How Helm helps
On Mac, Helm lets you set automatic, manual, or after-approval release behavior, with app-level defaults in Settings so every version does not start from a blank policy. Track phased release progress and release to all users when you are ready. The launch checklist surfaces missing What’s New, build, encryption, and listing gaps before you submit. The iOS companion keeps versions and phased releases moving when you are away from your desk.
Checklist
- Release type chosen and documented for the team
- Schedule time zone confirmed if automatic
- Owner assigned for manual release clicks
- Phased release on or off with a reason
- Marketing and support aligned to the same moment
- Hotfix branch ready if the rollout wobbles
