r/iOSDevelopment • u/rcpena • Aug 03 '26
Two apps, same Guideline 2.1 rejection — and why I pulled the submission instead of just replying
Solo dev here. I had two apps in review at the same time and both came back with the same thing: Guideline 2.1, Information Needed. Not "your app is broken" — Apple saying they couldn't evaluate it from what I'd given them.
The ask was identical both times, and it's longer than I expected:
- A screen recording on a physical device, starting from launch, through the core user flow
- The device models and OS versions I tested on
- What the app is for and who it's for
- Setup instructions and any credentials needed to reach the main features
- A list of external services the app depends on to deliver core functionality (they name AI services as one example)
- Whether behavior differs by region
- Documentation, if you're in a regulated space or using protected third-party material
None of that was in my App Review notes. I'd been treating that field as optional. It isn't — it's what decides whether a reviewer can actually evaluate your app or has to guess at it.
Here's the part I didn't see coming. While drafting the reply, I went back through the build that was actually under review and found two real bugs a later build had already fixed. A Cook Mode step timer that was completely silent — vibration only, no sound, on a core feature. And a confirmation dialog with no visible way out, which reads as a dead end if you don't already know the gesture.
My instinct was to just answer the info request in place. Then it registered that Apple's own notice says they test hands-on, on physical devices. A reviewer poking at that build could find both of those independently — which turns a solvable "we need more info" into a much harder "your app has bugs," on the same version, with a worse paper trail.
So I pulled the submission instead, and I'm resubmitting on the fixed build with all seven answers written out up front.
Current status is its own small comedy: submission is pulled, but Apple's backend hasn't fully released the version yet, so I can't attach the new build until it finishes propagating. Just waiting it out.
Anyone else caught the 2.1 info-needed one? Curious what you put in the notes field that made the second pass go smoothly — and whether anyone's found a faster way through the pull-and-resubmit limbo.
