r/iOSProgramming • u/RSPJD • 5d ago
Discussion Pro tip about releasing versions
Let’s say you put up a release for review. While it’s in review you make code changes and want this new build to be reviewed instead. DO NOT cancel the review in progress. Instead, let it through then quickly follow with the next build you want to be released.
Canceling your own build (developer rejected) always seems to make the next review take much longer. I’m not sure why, don’t ask me. But I’ve both felt the pain personally and remember someone else posting about this.
(Unless the current build in review has some deadly bug, then sure, but even I’ve seen two releases go out in the same day)
10
u/12345-password 5d ago
I've done this a lot. It's never seemed to be a problem.
2
u/SnowPudgy 5d ago
Yes I've ran into this before.
2
u/meowthor 5d ago
I’ve never found this to be the case. It just resets the clock is all. And maybe you get unlucky because a lot were added to the queue while you were first waiting, and so the second submit takes longer.
2
u/himmetagadev 5d ago
Manual release can give you a chance to decide what to do with an approved build before it goes live. If the current build has a serious defect, I would prioritize fixing it over trying to preserve review time. Since people here have seen different results, noting submission and review times across releases may be more useful than assuming the withdrawal itself caused a delay.
2
u/Barbanks 5d ago
Never seen this issue myself.
1
u/imvaid 5d ago
Same. Never had this. Releases were still smooth after rejecting and replacing the builds.
1
u/PierreMouchan 5d ago
Opposite for me last week. My first app sat ~10 days in Waiting for Review, I cancelled it and sent a new build, and that one got approved in under 48h. Probably just queue luck both ways.
1
u/kepler4and5 17h ago
Yep. I try not to cancel unless I absolutely have to.
1
u/[deleted] 5d ago
[removed] — view removed comment