If your build cleared App Review but the status in App Store Connect still reads Pending Developer Release after several days, the binary is fine. The release is paused at your end, not at Apple's.
Short answer
Pending Developer Release means Apple approved your build but you picked Manual release at submission, so the version waits in App Store Connect until an Account Holder, Admin, or App Manager clicks Release This Version and confirms, per Apple's release option documentation. The status does not time out. After the click, the version can take up to 24 hours to appear on the App Store.
What you should know
- Pending Developer Release is Apple's status for an approved build that has not been released yet, per the App Store Connect status reference.
- The status appears only when you chose "Manually release this version" at submission time, per Apple's release option page.
- Only Account Holder, Admin, and App Manager roles can click Release This Version. Developer and other roles see the version but cannot trigger the release.
- Apple sends a single email reminder after 30 days, then leaves the version held indefinitely; the status does not expire.
- Each platform (iOS, macOS, tvOS, visionOS) is released separately. One click does not release every platform version at once.
- After you click Release This Version, propagation can take up to 24 hours before the version is visible to all users on the App Store.
How did my app land in Pending Developer Release in the first place?
When you set up the version in App Store Connect under Version Release, you chose Manually release this version instead of Automatically release this version or the scheduled-after-approval option. After App Review approves the build, Apple parks the version in Pending Developer Release rather than pushing it live. The choice is per-version, not per-app: the release setting carries over from the previous version by default, but the field is editable at any time before approval.
This is the intended workflow for teams that want to coordinate a launch with press coverage, a server-side feature flag flip, a marketing email, or a regulated go-live window in fintech or health. The version stays held because that is what you asked Apple to do, even if the original developer who set the field has since handed the project over.
How do I actually release a build that is stuck in Pending Developer Release?
The procedure from Apple's documentation is short. Open App Store Connect, pick the app, select the version with the Pending Developer Release status in the sidebar, and click Release This Version at the top right. Confirm in the dialog. The status moves to Processing for Distribution, then to Ready for Distribution. Apple states the version can take up to 24 hours to appear on the App Store after the release request.
If you set up phased release on the same version, the click starts the seven-day rollout described in Apple's phased release help page rather than an instant push, and the App Store version status reads Ready for Distribution with Phased Release appended. The Release This Version button is the trigger for both modes.
Why is the Release This Version button greyed out or missing?
Three reasons cover most of the cases reported in the Apple Developer Forums and visible from the App Store Connect UI itself.
First, the signed-in account does not have the right role. Apple restricts the release action to Account Holder, Admin, and App Manager roles on the page that documents the release flow. Developer, Marketing, Customer Support, Sales, and Finance roles see the version but cannot release it. The fix is to ask an Admin to release, or to have the Account Holder grant your account the App Manager role on the app.
Second, the platform you are looking at is not the platform you cleared. If your iPhone build is approved but you are viewing the tvOS or visionOS tab, the button does not light up because that platform version is still in another state. Use the platform switcher at the top of the version page.
Third, the version is in fact already released and the sidebar status is showing a stale paint of the page. A hard refresh or sign-out and back in usually clears it. If the status persists for more than a working day after Apple's up-to-24-hours window, Apple Developer Support is the right escalation path through the Contact Us flow.
What is the difference between Pending Developer Release and Pending Apple Release?
The two statuses sit next to each other in Apple's App Store Connect status reference, and the difference matters when you are staring at a delayed release.
Pending Developer Release means Apple has approved the build and is waiting on you. The button is in your App Store Connect view, the timer is yours.
Pending Apple Release means Apple has approved the build but is holding it until the operating system version your binary targets is publicly released. This happens when you submit a build linked against a developer beta of iOS or macOS before that operating system ships to consumers. Apple's documented fix is to check the deployment target, and if it is wrong, reject the current build and submit a new one targeting a publicly available OS version.
| Status in App Store Connect | What it means | Whose action is needed |
|---|---|---|
| Pending Developer Release | Approved, set to Manual release | You: click Release This Version |
| Pending Apple Release | Approved, waiting for the targeted OS to ship | Apple: nothing for you unless the deployment target is wrong |
| Processing for Distribution | Released, Apple is preparing distribution | None; resolves within 24 hours |
| Ready for Distribution | Live on the App Store (or running phased release) | None |
Can I keep an app in Pending Developer Release forever, or will Apple time it out?
Apple does not auto-release the version. The closest documented behaviour is a single reminder email sent once a version has been in Pending Developer Release for more than 30 days, noted in Apple's App Store Connect help on the release options page. The version itself does not flip to Ready for Distribution on a schedule.
Holding a version too long has practical costs. App Review approval is tied to the binary you submitted; if you wait several months and the iOS SDK requirements shift (Privacy Manifest scope, target API level, deprecated APIs), the next version you submit will face the newer bar. A shipped version in Pending Developer Release also blocks you from queuing a second version for review on the same platform, which can leave a team in a confused state where bug fixes pile up behind a marketing decision.
What to watch out for
Three traps appear repeatedly in builder workflows like FlutterFlow, Expo, and React Native, and in teams using fastlane or the App Store Connect API release request endpoint to automate releases.
Phased release with Pending Developer Release confuses some CI scripts. When the API tries to modify a phased release while the version is still in the PENDING_DEVELOPER_RELEASE state, the request fails because that state is not yet eligible for phased-release modification. The correct sequence is to release the version first, then modify the phased release state. The fastlane issue tracker has multiple reports of this misordering.
The 24-hour propagation window is not always 24 hours. Most versions surface within an hour, but some regions (mainland China, regions with strict telecom approvals) can take longer, and a freshly released version may still show Open rather than Update in the App Store for several hours on the same device because of CDN caching. Do not assume a release has failed because one team member sees the old version.
The release action is irreversible through the UI. You can pause a phased release. You cannot un-release a non-phased version. If the launch decision needs to be reversed, the only path is to remove the app from sale, which has its own propagation lag and looks bad to existing users.
For builders who want an external automated read of their compiled binary before they submit (and before they end up debating whether to release a flawed build that is already sitting in Pending Developer Release), PTKD.com (https://ptkd.com) is one of the platforms focused on pre-submission scanning aligned with OWASP MASVS, especially for no-code and AI-coded apps where the SDK list is hard to track by hand.
Key takeaways
- Pending Developer Release means the build is approved and the release switch is yours; the version sits there until an Account Holder, Admin, or App Manager clicks Release This Version, per Apple's App Store Connect documentation.
- Each platform is released separately; check the platform switcher before assuming the button is broken.
- The status does not expire, but holding a version for months can put you behind newer Apple submission requirements when you next submit.
- Some teams send compiled binaries through external scanning platforms such as PTKD.com (https://ptkd.com) before the version reaches App Review at all, which removes most of the "should I really release this?" hesitation that produces stuck Pending Developer Release states.
- If the button is greyed out, the most common cause is role permissions, not an Apple bug; ask your Account Holder before opening a support ticket.
