Guideline 2.4.1 rejection: iPad compatibility
How the rejection usually reads: "We found that your app did not run at iPad resolution" / "the app does not support all orientations on iPad"
Why it happens
If your Info.plist says the app runs on iPad (UIDeviceFamily includes 2), the reviewer tests it on an iPad and expects the multitasking rules to be met: either all four orientations, or UIRequiresFullScreen set to true. Most React Native and Flutter apps declare iPad by default without ever being designed for it. Either opt out of iPad entirely, or set UIRequiresFullScreen and test the layout once.
What can be checked before you submit
1 of RejectProof’s checks map to Guideline 2.4.1. Each one reads your .ipa — no upload — and reports the evidence with a fix.
- iPad supported but orientations incomplete without UIRequiresFullScreen
PB-31 · guideline 2.4.1 / iPad multitasking · warning
Apps that run on iPad must either support all four orientations (UISupportedInterfaceOrientations~ipad) or set UIRequiresFullScreen = true to opt out of multitasking. Expo: expo.ios.requireFullScreen = true, or expo.orientation = "default". Swift: General → Deployment Info.
What a scan cannot tell you
Static checks read the build; they do not run it. Whether a reviewer likes your design, agrees with your content, or considers the app “sufficiently different” is their call. Fix the mechanical layer first so the human review is about your product, not about a missing plist key.