Apple's 4.3 spam check is a 30-second batch job. 22 rejections prove it
Originally published at tensorust.com . TL;DR: Apple App Review rejected 11 of my iPhone apps under Guideline 4.3 Spam . Then it did it again. Both times, all 11 rejections landed inside 30 seconds (30 s on October 5, 27 s on October 12), one email every 3 seconds, in an order that has nothing to do with the order I submitted them. Round two came 167.7 to 167.9 hours after I resubmitted, for…
Apple's recent App Review process has come under scrutiny after several developers reported experiencing a 30-second batch job for their app submissions. In total, 22 rejections were issued under Guideline 4.3 Spam, and these rejections occurred within a 30-second time frame on two separate occasions. The rejections came one email every three seconds, with no apparent correlation to the order in which the apps were submitted.
The process appears to be more focused on evaluating accounts rather than individual apps, as developers submit multiple apps at once and receive rejection notices simultaneously. Apple's official statement on the matter does not provide clear guidelines, instead focusing on the need to avoid submitting duplicate apps and ensuring that apps are distinguishable from existing ones.
Developers who have faced this issue have reported waiting for an extended period between resubmission and rejection, with some instances lasting as long as seven days. The consensus among developers is that Apple is implementing a holding queue system that triggers after a specific time frame, regardless of the individual app's merits.
This pattern of rejections has been observed across multiple developers, with some even noting that their previously approved apps are now being rejected under the same Guideline 4.3 Spam policy. While Apple has provided a short fix list for developers to follow, the lack of transparency and consistent explanations surrounding the issue has left many developers frustrated and seeking clarification from the App Review process.
Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.