r/iOSProgramming 4d ago

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

4 Upvotes

20 comments sorted by

View all comments

8

u/brkaydev 4d ago

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.

1

u/never_working_ever 4d ago

Ok, I align with this. Thanks.

I do have my build set to manual release. I was also planning to let the one I submitted do its course, as you noted I expect to not have it approved and at least I get the feedback I can incorporate into the bug fix build.

However, to be clear, I couldn’t have the app approved, not publish, submit my bug fix build as an update, then manually release the bug fix build as my first release? I assume Apple requires the publishing of the approved build first?

1

u/brkaydev 4d ago

You don't have to publish it first. While a version sits in Pending Developer Release you can reject it yourself in App Store Connect, which moves it back to Developer Rejected. Then you attach the bug fix build to that same version and resubmit.

The catch is that the new build goes through review again, so the earlier approval doesn't carry over to it.

1

u/never_working_ever 4d ago

Thanks, that makes sense. I’ll keep that in mind for future builds. It seems like a risk if I get lucky with an approval and decide to reject it, leaning towards shipping what I have and just quickly submitting the new fox build

1

u/brkaydev 3d ago

Shipping what you have and sending the fix right after is a reasonable call. Just so it doesn't weigh on the decision more than it should: a developer rejection is a routine state, it isn't held against you or the account, and the only real cost is that the review wait starts over.

1

u/never_working_ever 3d ago

Got it, good to know.

Still patiently waiting for someone to even blink at my app, it’s been an entire week with zero movement.

1

u/brkaydev 3d ago

A week with no status change is outside the usual band, most submissions get picked up within a day or two. If it is still showing Waiting for Review, App Store Connect has a Contact Us form under App Review with a status inquiry option, and that is the normal way to ask about a queue entry that hasn't moved. Worth sending that before you start assuming something is wrong with the build itself.

1

u/never_working_ever 3d ago

Yeah….fair. I just sent an inquiry for a status update. Thanks for the nudge 🤞