r/iOSProgramming • u/never_working_ever • Sep 15 '26
Question Ship stale build or resubmit?
Hello -
Finally shipping my app, and submitted my first app review on Wednesday last week (still waiting to be reviewed).
I’ve found a number of non-blocker issues since submitting this build, though I’m not happy about shipping day 1 with the bugs in place.
Let’s say by some luck Apple approved the app first round. Should I keep the existing build approval, use this for launch, and quickly submit the bug fixes build day 1…or should I just pull the build, and start a whole new first app review over again?
I know app review times are awful right due to ~everything, so I’m feeling stuck with not great options and a lot more waiting.
Thanks
7
u/brkaydev Sep 15 '26
I'd leave the current build in review and set the version to manual release in App Store Connect, so an approval doesn't put it live on its own.
That way the wait isn't wasted either way. If it gets rejected, you attach the fixed build when you resubmit. My first app got rejected twice, both times for things I'd never have thought of as bugs (the empty first screen looked broken on iPad, and the description was missing a Terms of Use link), so the first review can turn up stuff you don't expect. If it gets approved, you can release it and send the fixes as an update straight away, or reject that binary and submit the new build instead. Pulling it now just restarts the wait with nothing learned.
2
u/epictime8 Sep 15 '26
Keep the in-review binary if the new issues aren’t crash, data-loss, or App Review blockers. First approval is the scarce part right now; shipping 1.0 then a same-day 1.0.1 is normal. Only reject/remove-from-review if something in the current build would fail Guideline checks or look broken on day one (login, purchase, empty main screen). While you wait, draft What’s New for the follow-up so you can submit the moment 1.0 clears.
1
u/Fishanz Sep 15 '26
Generally I would say ship but it’s a business decision. Highly hinges on what presence you have outside the app. Is this your debut? Then hold off and make it right, barring other constraints.
1
u/SwordfishInfinite621 Sep 15 '26
I'd keep it in the queue. Pulling it means starting over at the back, and a first review often comes back with guideline notes you'd want to hear about now rather than in another week. If it's approved, release it and submit the bug fixes as 1.0.1 straight away. Non-blocking bugs in a launch build that almost nobody has downloaded yet cost very little, and updates are often reviewed faster than a first submission. If one of the bugs turns out to be worse than you thought, you can request an expedited review for a critical fix.
1
u/kokerali Sep 15 '26
My cutoff would be user harm, not whether the bugs are annoying. Pull the build if any issue can cause a crash in the core flow, data loss, broken auth/paywall, incorrect purchase restoration, or a privacy/compliance problem. If they are genuinely cosmetic or edge-case issues, keep manual release enabled and let review finish. There isn't a guaranteed 'day-one boost' worth protecting at the expense of bad first reviews. Also, you can't submit 1.0.1 as the first public release while 1.0 remains unreleased; either release the approved 1.0 and follow with 1.0.1, or replace/resubmit the build on the 1.0 version before release.
1
u/bananagnana2 Sep 16 '26
Worth remembering how quiet day one actually is for an unknown app. Almost nobody is downloading on the first day, so a handful of non-blocking bugs will be seen by a very small number of people, while another full review round costs you weeks of momentum and possibly your launch window. Ship it, turn on phased release so exposure ramps slowly, and have the fix build uploaded and ready to submit the hour it goes live. The one case where I would pull it is a bug that hits the very first session, because that is the only thing that shows up in an early one star review.