社区拒绝存档

苹果应用商店和谷歌商店拒绝的恐怖故事

收集苹果应用商店和谷歌商店拒绝循环的最坏部分，作为截图和纯文本，供移动团队学习审查队列的真正成本。

提交规则

1到5张图片加上故事文本。

故事中不允许内链。请使用本地图片。保持拒绝痛苦、具体和有用。

已种子故事

覆盖的商店

最大5个

每个故事的图片数量

The archive

一项花费超过一个糟糕冲刺的拒绝

每个故事都是以文本为首，图像为辅，且故意避免外部链接，以确保存档可读性

苹果App Store 荒谬由Adrien分享

苹果无法识别的用户

"这个应用的用户将是谁？"

Adrien提交了版本1.0，苹果在指南2.1中停止了审查。没有崩溃报告，没有破坏的功能，也没有在消息中请求二进制修复。唯一的阻塞是苹果要求详细说明这个应用是为谁而设计的，才能继续审查

App: iPad app版本1.0
延迟: 2026年5月29日，审查暂停
结果: 苹果要求开发者解释目标用户之前继续审查。

苹果应用商店痛苦由Adrien分享

苹果认为的应用程序不够不同

"App Store上已经有足够的这些应用程序了。"

Adrien因苹果没有看到与类似应用程序相比的足够独特价值而获得了设计-垃圾拒绝。审查说，应用程序主要是一个大便或打嗝应用程序，即使它有区别的功能，苹果也认为该功能足够突出，以至于将整个应用程序视为一个饱和类别中的重复内容。

应用程序: Entertainment sound app
Delay: Rejected on May 15, 2026
Outcome: Apple rejected it under Guideline 4.3(b), saying the app duplicated a saturated category.

App review guide screen used to represent an Apple App Store rejection workflow

App Store publishing interface used to represent a delayed Apple review

Apple App Store Launch blocker

The metadata loop that ate launch week

"The build was fine. The rejection kept moving from the app to the words around the app."

The team shipped a clean build, then spent more than a week cycling through metadata objections. Each resubmission answered the previous note, but the next reply focused on another phrase, screenshot, or explanation. No code was changed. The launch calendar, press window, and paid acquisition plan were all held hostage by review copy.

App: 用户生产力应用
延迟: 9 天
结果: 重新编辑截图、字幕和审阅笔记后，仍未进行二进制更改，审批通过。

苹果应用商店荒谬

审批通过，然后被一个额外的合规问题阻塞

"审批邮件到达之前，阻塞就已经到位了。"

The build reached approval, but release was still blocked by a compliance prompt the team thought had already been answered. The release owner had to stop rollout, gather legal wording, update the App Store Connect response, and wait again. Customers saw the announcement before the app was actually available.

App: B2B商业客户端应用
Delay: 4天
Outcome: 在重新回答出口控制并等待下一次审查后发布了。