App Rejected: Apple Guideline 2.1 - iPad Support
Crashes and iPad Layout Issues
Apple’s Guideline 2.1, App Completeness, is one of the most common reasons apps are rejected during review. For Adalo apps, the two issues Apple flags most often are crashes and layout problems on iPad. Since Apple reviews all universal iOS apps on both iPhone and iPad, an app must run without crashing and must present a stable layout on iPad to pass review.
This guide explains what Apple is expecting, why these issues happen, and how to resolve them before resubmitting your build.
Why Apple Tests on iPad
Even if your app is designed for iPhone only, Apple will still review it on iPad. All Adalo apps are built as universal iOS apps, which means the app can technically launch on iPad. Apple requires the app to run without crashing and to present a usable layout on that device.
Adalo does not offer native iPad layout support, but we can enable a backend setting that improves how the app appears on iPad for the review process.
Issue One: Crashing During Review
Apple will reject your app immediately if it crashes on launch or during normal interaction on any device they test.
Common causes
• Screens or components that work in Preview but break on device • Incomplete data or missing linked records • Complex actions triggering at the same time • Screens that rely on values that are empty or null • Custom lists or third party components that behave differently on a device
How to fix
• Test your app on an actual iPhone and on an iPad if possible • Check your lists, filters, and actions for assumptions about missing data • Temporarily simplify complex navigations during review • Make sure every screen that Apple can reach is functional with no empty states • If a crash is happening on load, check your Home or first navigation screen for actions that require data immediately
Issue Two: Layout or UI Problems on iPad
Even though Adalo does not support designing layout specifically for iPad, Apple still reviews the app on that device. If the layout breaks, stretches, overlaps, or becomes unusable, Apple will reject it under Guideline 2.1.
Why it happens
• Components expand or shrink differently on larger viewports • Absolute positioning that looks correct on iPhone becomes misaligned on iPad • Margins and spacing designed for a small screen do not scale • Elements appear off screen or become unreachable • Apple considers the layout incomplete or not usable
How Adalo can help
We can enable an internal setting that improves how your app displays on iPad specifically for App Review. This does not give your app full iPad optimization, but it usually stabilizes the layout enough for approval.
To request this, Submit a Ticket including details and a screenshot of the rejection email from Apple and our team will assist with the update.
Before You Resubmit to Apple
Reproduce the issue described in Apple’s rejection notes.
Fix any crashing or navigation errors.
Test your app on real devices when possible.
If the issue is related to iPad layout, contact support and request the iPad display adjustment.
Submit a new build and include a short review note explaining that your app is optimized for iPhone, with layout improved for iPad as needed.
Last updated
Was this helpful?