Post

Replies

Boosts

Views

Activity

Reply to No response to a Resolution Center reply on a 2.1 Information Needed rejection (7 days)
A quick status update, since I promised to keep the timeline going. Day three of the new submission: nothing has changed. The rebuilt app went in on August 22 and has been sitting in Waiting for Review since — no movement as of August 25. I will just note that the widely quoted figure — 90% of submissions reviewed within 48 hours — has not matched my experience once in this process. The first submission waited four days for its first response, and this one is now past 72 hours untouched. Either that statistic hides a long tail, or I keep drawing the short straw. Timeline so far: August 10 — first submission August 14 — rejected, 2.1 Information Needed; replied in full the same day August 21 — seven days of silence, this thread posted August 22 — rejected under 4.3(a) August 22 — app rebuilt from scratch, new build submitted, Waiting for Review August 25 — still Waiting for Review, three days in Nothing to do but wait. I will post the outcome either way.
3w
Reply to No response to a Resolution Center reply on a 2.1 Information Needed rejection (7 days)
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.
3w
Reply to No response to a Resolution Center reply on a 2.1 Information Needed rejection (7 days)
A quick status update, since I promised to keep the timeline going. Day three of the new submission: nothing has changed. The rebuilt app went in on August 22 and has been sitting in Waiting for Review since — no movement as of August 25. I will just note that the widely quoted figure — 90% of submissions reviewed within 48 hours — has not matched my experience once in this process. The first submission waited four days for its first response, and this one is now past 72 hours untouched. Either that statistic hides a long tail, or I keep drawing the short straw. Timeline so far: August 10 — first submission August 14 — rejected, 2.1 Information Needed; replied in full the same day August 21 — seven days of silence, this thread posted August 22 — rejected under 4.3(a) August 22 — app rebuilt from scratch, new build submitted, Waiting for Review August 25 — still Waiting for Review, three days in Nothing to do but wait. I will post the outcome either way.
Replies
Boosts
Views
Activity
3w
Reply to No response to a Resolution Center reply on a 2.1 Information Needed rejection (7 days)
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.
Replies
Boosts
Views
Activity
3w