"Pending Developer Release": approved, not live, waiting on you

Pending Developer Release means Apple approved your version and it is sitting there, finished, waiting for a human to press a button. It will not go live on its own. Not tomorrow, not next week.

If your app has been "approved" for days and is not on the store, this is almost always why.

How you got here

When you submit a version, you choose how it releases. Three options, and the wording is easy to skim past:

Automatically release this version: goes live as soon as it is approved
Manually release this version: approval parks the version in PENDING_DEVELOPER_RELEASE until you release it
Automatically release after a specific date: scheduled; approval waits for the clock

Manual release is the sensible default for anything with a launch plan attached, and it is what most teams pick once and then forget about. The state is working as designed. It just does not announce itself loudly.

How to release it

In App Store Connect, open the app, open the version showing this state, and use the release control on that page.

That is the whole action. There is no second review. The version moves to READY_FOR_SALE and starts propagating.

Two things to know about the moment after you press it:

Propagation is not instant. The status flips to live quickly, but the App Store's regional caches take longer to catch up, direct links tend to work before search does, and search across all territories takes longest. Seeing your old version in the store an hour later is normal.

There is no undo. Releasing is one-directional. If you need to pull it back, you are into removing the version from sale or shipping a replacement, both of which are much slower and messier than not pressing the button in the first place.

Changing your mind before releasing

You can leave a version in PENDING_DEVELOPER_RELEASE indefinitely. Nothing expires it.

What you cannot do is edit it. The version is locked in this state exactly like it was in review, description, screenshots, build, all frozen. If you have decided the approved build is wrong, your options are:

Release it anyway and immediately start a new version, or
Remove this version and submit a replacement, which means a fresh trip through review

There is no "approved but let me swap the screenshots" path. That is the trade you accepted when you chose manual release, and it is usually still the right trade.

Using it deliberately

PENDING_DEVELOPER_RELEASE is the single most useful state Apple gives you, because it converts an unknowable wait into a scheduled event.

Submit early. Let it queue and review on Apple's timescale. Get approved. Then hold, and release when your marketing is ready, when your backend migration is done, when the Android build is also approved, or simply when it is a Tuesday morning rather than a Friday night.

Every launch plan that promises a date should be built on this state. Plans built on "we'll submit on the 12th and it'll be live on the 14th" are guesses about a queue you do not control.

Coordinating with Google Play

Play has no equivalent single button, but it has the same shape: a release can be created and held in draft on a track, then rolled out when you choose. So a coordinated cross-store launch is: get Apple to PENDING_DEVELOPER_RELEASE, get Play to a committed release you have not rolled out, then do both within a few minutes of each other.

Apple's propagation lag means the App Store side will still be catching up when Play is already serving the update. Nothing to do about that; just do not panic at the difference.

Spotting it before it costs you a week

The state is visible in the API, so anything watching your app can tell you the moment approval lands and the release button becomes live.

AppSubmit surfaces "Ready to release" on the app's card the moment a version enters this state, precisely because an approved-and-forgotten version is the failure mode nobody notices. Checking the version status in the console does the same job. You just have to remember to look.