Pending Developer Release means your app has already passed App Review and is approved, and it is now waiting for you to release it, because you chose to release this version manually rather than automatically. It will not go live on its own, which is exactly the point of this status: the manual release option hands you control of the moment your app appears on the App Store. So there is nothing wrong and nothing to fix, and no risk of an accidental launch. When you are ready, you click Release This Version in App Store Connect and the app goes live shortly after. Until then, it stays in Pending Developer Release, waiting for you, with no rush.
Short answer
Pending Developer Release means the app is approved and waiting for you to release it manually. Per Apple's App Store Connect help, when you choose to release a version manually, it enters this status after App Review approves it, and it goes live only when you click Release This Version. It does not auto-launch, so there is no risk of an accidental release, and it can stay pending until you release it, so there is no immediate deadline. To go live, release it in App Store Connect; to change the behavior next time, select automatic release instead. This is a normal, expected status, not a stuck one.
What Pending Developer Release means
Pending Developer Release is the status your app shows when App Review has approved your version and you previously selected to release it manually. The word pending here refers to the release, not the review: the review is done and the app passed, and what is pending is your action to make it live. So seeing this status is good news, because it means your app cleared review, and it is now simply waiting for you to decide when it appears on the store.
This status exists because App Store Connect offers a choice of how an approved version is released, and one option is manual release, where you control the exact moment. When you picked that option and the app was approved, it moved into Pending Developer Release rather than going live automatically. Understanding that this is the intended result of a choice you made, not an error or a stall, removes the worry: nothing is broken, the app is ready, and the next step is entirely yours whenever you choose to take it.
Does it auto-launch?
No, an app in Pending Developer Release does not auto-launch, and this is the whole purpose of the status. Because you chose manual release, the app will not appear on the App Store until you explicitly release it, so there is no risk that it goes live on its own the moment Apple approves it. If you were worried about an accidental or unexpected launch, this status is precisely the safeguard against that: it holds the approved app until you act.
This is the difference between the release options. Had you chosen automatic release, the app would have gone live as soon as it was approved, without a Pending Developer Release step. By choosing manual, you traded that automatic behavior for control, and Pending Developer Release is that control in action. So you can leave the app in this status with confidence that it will stay there, and coordinate your launch, a marketing date, an announcement, or a specific time, knowing the app will not jump ahead of you and release itself.
How long can it stay pending?
An app can stay in Pending Developer Release for as long as you leave it there, because the status waits for your action rather than counting down to a deadline. There is no short forced timeout that pushes an approved-but-unreleased version live or expires it after a day or two, so you can hold it for hours, days, or longer while you prepare your launch. In practical terms, the app remains pending until you release it, which is what makes it a reliable launch-timing tool.
That said, do not treat pending as permanent indefinitely. If you leave an approved version unreleased for a very long time, it can eventually become stale, and best practice is to release a version reasonably soon after approval so it reflects current requirements and does not sit indefinitely. But for the normal case of holding an approved app for a launch, there is no pressure of an imminent expiry, and you should release when your timing is right rather than rushing because you fear the status will lapse. It waits for you.
How to release the version
Releasing the version is a single action in App Store Connect. Open your app, go to the approved version in Pending Developer Release, and click Release This Version, which tells Apple to make the app live. After you release it, the app moves to processing and then goes live, and it typically becomes available on the store within a few hours, sometimes sooner, as the release propagates. So the moment you decide to launch, releasing is quick, and the short propagation time is the only wait after your click.
You can also release programmatically if you manage releases through automation, but for most developers the button in App Store Connect is the direct way. Once released, the version is on the store and the status becomes Ready for Sale. If you are coordinating a precise launch, release at your chosen moment and allow for the short propagation window so the app appears when you intend. There is nothing else you need to do to launch an app in Pending Developer Release beyond this release step.
Why you see this status: release options
You see Pending Developer Release because of the release option you selected when you submitted or configured the version, so it helps to know the options. App Store Connect lets you choose to release a version automatically as soon as it is approved, to release it manually at a time you choose, or to schedule it for automatic release on a specific date. Choosing manual release is what produces the Pending Developer Release status after approval.
Knowing this lets you change the behavior for the future. If you would prefer your next approved version to go live automatically, select automatic release when you submit it, and it will not sit in Pending Developer Release. If you value controlling the launch moment, keep choosing manual release, and expect this status each time. The status is therefore a direct reflection of your release setting, and adjusting that setting is how you decide whether future versions wait for you or launch on approval, according to what suits each release.
Does resubmitting reset review?
You do not need to resubmit an app in Pending Developer Release, because it is already approved, and resubmitting would restart the process unnecessarily. Since the review is complete and the app passed, the only remaining step is releasing it, so uploading a new build or submitting again would send you back into review rather than move you forward. Treat Pending Developer Release as the finish line of review, not a point to resubmit from.
Resubmitting is only appropriate if you actually need to change the app before it goes live, in which case a new build would go through review again as a new submission. But if the approved version is the one you want to ship, there is no reason to resubmit; you simply release it. So the answer is that you should not resubmit to escape or advance this status, because releasing, not resubmitting, is what launches an approved app, and resubmitting would forfeit the approval you already have.
Release statuses at a glance
Placing Pending Developer Release among the surrounding statuses clarifies where it sits. The table below compares them.
| Status | What it means | What happens next |
|---|---|---|
| Pending Developer Release | Approved, you chose manual release | It waits for you to release it |
| Processing for App Store | You released the version | It goes live shortly |
| Ready for Sale | The version is live | It is available on the store |
| Waiting for Review or In Review | Not yet approved | Review must finish first |
Read the table by sequence: Pending Developer Release comes after approval and before you release, so it is a waiting-on-you status, not a waiting-on-Apple one.
Release decision
Matching your situation to the right move keeps the launch under control. The table below maps common cases.
| Your situation | Best move | Why |
|---|---|---|
| Want to control the launch moment | Leave it pending, release when ready | It will not auto-launch |
| Ready to go live now | Click Release This Version | It sends the app live |
| Want automatic release next time | Change the release option at submission | Avoids the manual step |
| Worried it will launch by itself | Do nothing, it will not | Manual release is a safeguard |
Read the guide by intent: the status is designed for control, so most situations call for releasing when you are ready rather than any corrective action.
Verify the approved build before releasing
Because Pending Developer Release gives you a moment of control before the app goes live, it is a good point to confirm the build is sound, since after you release it, it is on the store and any issue reaches users.
A scanner like PTKD.com analyzes your build and reports issues such as leaked keys and secrets, over-broad permissions, and insecure data handling by severity, mapped to OWASP MASVS, so you can verify the approved build before you release it live. To be clear about the boundary: PTKD does not release your app, change its status, or review it for Apple. It checks the build itself, so the version you release from Pending Developer Release is one you have confirmed is secure before it reaches your users.
What to take away
- Pending Developer Release means your app is approved and waiting for you to release it manually, so the review is done and the release is what is pending.
- It does not auto-launch, which is the point of the manual release option, so there is no risk of an accidental or unexpected launch.
- It can stay pending until you release it, with no short forced deadline, though releasing a version reasonably soon after approval is good practice.
- Release it by clicking Release This Version in App Store Connect, after which it goes live within a few hours, and change the release option to automatic if you prefer that next time.
- Do not resubmit an approved app in this status, and use the moment to verify the build with a tool like PTKD.com before releasing.
