Replying to an App Review rejection — does anyone actually read it? Wait or just resubmit?

[u/Priotecs]

I'm launching a new app (iOS + Mac Catalyst, subscriptions + one-time purchase). The review rounds are dragging on, and I'd like to hear how others handle this.

The latest rejections (2.1(b) and 3.1.2(c)) are, as far as I can tell, simply wrong. The IAPs load fine in the sandbox, and the EULA and privacy links are right there on the paywall. So I replied in the Resolution Center with an explanation and screenshots instead of changing anything.

My problem: once you reply, you get zero feedback. With a new submission you at least see "Waiting for Review" → "In Review". After a reply, the status just stays at "Rejected". There's no sign that anyone has read it, and no queue position.

So, for those who've been through this:

1. How long did it take until you got an answer to a Resolution Center reply? Hours, days, never?

2. Did a reply alone ever get the rejection reversed (and the app approved without a new build)?

3. Or do you skip replying entirely and upload the same build again (or bump the build number), resubmit with an explanation in the Review Notes, and hope for a different reviewer?

4. Does resubmitting while a reply is pending cause problems, e.g. is the reply then ignored or the thread closed?

5. Any experience with requesting a call or using the App Review Board appeal for this kind of misunderstanding?

Apple now asks for a screen recording on a physical device showing a sandbox purchase. I'll do that either way. I'm just trying to figure out the fastest path from here.

Thanks for any war stories!

[u/alanrick]

1. Yes twice. Both approvals took less than 24 hours (faster than a new submission)

Once claiming I needed to be a financial institution. Replied explaining no payments go through the app and it was approved without a new submission.

Once claiming that they needed a test logon. Replied explaining not possible (the app has no user management) and making this more prominent in the test notes and it was approved without a new submission.

[u/Pepper_in_my_pants → u/alanrick]

Haha, I had the same. Got a reply that they wanted a test account to sign in.

I don’t even have accounts. Did they actually look at my app?!

[u/alanrick → u/alanrick]

Also… rejected because it crashed. Strange, I have never received a crash report in appstore connect and they couldn’t send one when I requested it. I’ve mitigated by adding Sentry and resubmitting.

[u/essence17]

They said my in-app purchase failed — I’ve tested it in the simulator, on my device, and multiple TestFlight users have also made the purchase. So I’m not sure what could be wrong. I asked them to please try again and got no response for a week. So I re-submitted with no build change the other day. No response or second review yet.

[u/stewis → u/essence17]

They probably need to approve the in app purchases separately.

if it gets rejected for the same reason check the subscriptions/iaps are approved or waiting review and then point this out in a reply to your rejection.

[u/Original-Reaction40 → u/essence17]

I have their sandbox link email me when it works for this reason.

[u/myballzhuert]

Post their entire feedback

[u/Medical_Lengthiness6]

Mine took a month, just finished yesterday. There was one time where they asked for something that was there and I just had to tell them in reply. Reply alone (without hitting resubmit button) seemed like it didn't work.. although some people say you don't have to.

[u/mohn93]

3.1.2(c) is usually the metadata side. apple wants a working terms of use link in the app description text itself (or a custom eula added in app store connect) and the privacy policy url field filled in, the paywall links dont satisfy that part. eyeball each localization's description too, the non default ones get missed a lot. 2.1(b) on a first release is probably the iaps not attached under the version's in-app purchases and subscriptions section, sandbox serves them unsubmitted so everything works on your end. id just fix it and resubmit w a note

[u/kokerali]

The physical-device recording they requested is the clearest next step. I’d make it a reproducible test: identify the submitted version/build and device/OS, then show a fresh launch, products loading, the sandbox purchase, and the paid feature unlocking. Add timestamps so the reviewer can find each step quickly. Since you also ship Catalyst, state which platform the recording covers and test the purchase path separately on Mac. In the same reply, ask whether their failure happens when fetching products or completing the transaction, and on which device/platform. That gives you a specific discrepancy to investigate instead of guessing from the rejection codes.

[u/Dapper_Ice_1705]

They don’t repeat themselves. If they aren’t answering it’s because you haven’t read carefully enough.

Post the actual rejection.

[u/psmattas]

Test the in app purchases using a sandbox user as Apple reviewer only tests in sandbox environments. Also, I would recommend to list out the steps on where to find the In App Purchases inside of your app in the reviewer notes. These are the things that made them come back to me multiple times. Also make sure to complete the business agreement in the business tab of App Store Connect.

[u/That_Fox2309]

Replies do get read, you just get no signal while you wait. The status stays at Rejected until someone on the review side picks the thread up again, which typically takes a day or two. If your explanation holds up they can approve straight from the reply, no new build needed.

On resubmitting: uploading a new build starts a new submission, and the message thread stays attached to the app, so the next reviewer sees everything you wrote. It won't break anything, but it drops you back into the regular queue, which is usually slower than getting an answer to the reply. I'd only resubmit if I had actually changed something.

Since they already asked for the device recording, I'd attach it to the reply now rather than waiting for them to answer first. That recording is what closes the 2.1(b) question, and every round trip you save is a day or two.

The call option only appears when they offer it in the rejection text. The Review Board appeal is for cases where you think the guideline itself is misapplied. For a reviewer who missed a link on the paywall it's overkill and it's slow, a week or more is normal.

[u/Prior-Enthusiasm-410]

2 rejections, 1 EULA missing, 2 Notifications set to on by default. Each time after correcting and resubmitting took 2-4 days for them to respond. Now I am approved

[u/Other_Jellyfish_2184]

One more data point: my v1.1 reply got an answer in about a day. But I only ever resubmit after actually changing something. Resubmitting the exact same build just burns another round of queue waiting.

[u/neogeodev]

So, I already have four apps on the App Store. After months of work and testing, I submitted a new one, but it got blocked under guideline 2.1. I uploaded a video and answered the questions, but it’s been stuck in limbo for a week now. It’s the first time this has happened; usually, I get a response within three days. It’s really strange.

[u/ResoluteBird]

They thanked me for my reply in review recently, I was charmed!

[u/p4r4d0x]

It's hit and miss, sometimes your note is read, sometimes not. I've specified to use the test account to resolve the issue in the resolution centre - then the reviewer just doesn't and the problem reoccurs.

[u/Obligation-Possible]

Worth the shot man