No response to a Resolution Center reply on a 2.1 Information Needed rejection (7 days)

Question

Henry_Fan OP

Created 1d

Replies 2

Boosts 0

Participants 2

Timeline

Submitted: August 10, 2026 - first submission of a new app

Rejected: August 14, 2026 - Guideline 2.1 Information Needed - New App Submission

Replied: August 14, 2026, about 17 hours later, in the same thread

Current status: Unresolved Issues / Rejected, 7 days with no response Submission ID: 5aa5647f-7c12-4949-ba8e-dfba1bad3047

What happened

The rejection asked us to reply in App Store Connect with seven specific items, including a recording captured on a physical device running the latest OS.

We replied on the App Review page the same day, about 17 hours after the rejection. All seven items were answered in order and the recording was attached to the reply. Both the reply and the attachment are visible in the thread. We also copied the same seven answers into the Notes field of the App Review Information section, as the message asked.

Seven days later there has been no response, and the submission is still showing Unresolved Issues.

We have not resubmitted. The rejection asked us to reply rather than resubmit, and resubmitting would close the open thread.

Questions

Does replying on the App Review page put the item back in front of a reviewer on its own, or is a further step required on the developer side?
Is seven days without a response typical once an information request has been answered in full?
If it is not, what is the correct way to have the reply picked up?

App name, Apple ID and Team ID available on request.

Answer 1

Tomato OP

1d

I would find an excuse to make changes and submit a new Build if I were you. They rarely reply through Resolution Center after you give them information.

Answer 2

Henry_Fan OP

14h

Thanks — that matches what happened, and it turned out to be the right instinct.

An update, in case someone finds this thread later.

Something moved shortly after I posted here. Whether the post had anything to do with it, or a support case I had opened elsewhere simply came due, I cannot tell. A response did arrive — just not the one I was waiting for. Instead of an answer on the information request, the submission came back rejected under Guideline 4.3(a).

So the Resolution Center thread was never answered on its own terms. In practice the advice above was correct: once you have replied to an information request in full, the thing that moves the case forward is a new build, not more waiting.

I did not argue the 4.3(a) call. My honest read is that it may not have been meant for an app like this one, but disputing a spam finding is a slow way to spend a week, and rebuilding is not. So the app was rebuilt rather than defended: a different idea of what the product is, the code written again from the protocol documentation rather than reworked, and a new interface, icon, listing and screenshots to go with it.

I also took out the features that nearly every app in this category carries — the ones built on the same widely used side protocols — so that what remains is only the thing this app actually does. That was not asked for. It seemed better to remove the common ground than to explain it.

Timeline so far, since 4.3(a) threads tend to go quiet:

August 10 — first submission
August 14 — rejected, 2.1 Information Needed
August 14 — replied in full the same day, recording attached
August 21 — seven days of silence, this thread posted
August 22 — rejected under 4.3(a)
August 22 — app rebuilt, new build submitted, Waiting for Review

I will post whatever comes back, approval or rejection — threads like this are only useful if someone finishes the story.