The Adalo App Store Problem
Getting an Adalo app approved by Apple's App Store is harder than most builders expect. Apple's review team tests on iPads (even if your app is iPhone-only), scrutinizes privacy policies, and rejects apps that feel like webview wrappers - which is exactly what Adalo generates under the hood.
As certified Adalo Experts who've published dozens of apps, we've developed a pre-submission checklist that catches the most common rejection triggers before Apple sees your app.
Top 7 Rejection Reasons for Adalo Apps
1. Guideline 2.1 - App Completeness (iPad Layout)
This is the #1 rejection reason for Adalo apps. Apple tests every iPhone app on iPad, and Adalo doesn't offer native iPad layout support. The result: stretched screens, overlapping elements, and broken navigation on iPad.
Fix: Contact Adalo support and request they enable the iPad compatibility backend setting for your app. This forces the app to display in iPhone aspect ratio when running on iPad, preventing layout issues. Do this BEFORE submitting.
2. Missing or Inadequate Privacy Policy
Symptom: Rejection citing Guideline 5.1.1 - Data Collection and Storage.
Fix: Your privacy policy must be accessible both in the App Store listing AND within the app itself. It must disclose: what data you collect, how you use it, how you store it, and how users can request deletion. Host it on a public URL and link it in both Adalo's app settings and your App Store Connect listing.
3. Crashes During Review
Symptom: Apple reports the app crashed during testing.
Cause: Heavy home screens, broken external collections, or custom components that fail on iPad resolution. The review team may test on device configurations you never tested.
Fix: Reduce home screen complexity. Test on physical devices - not just the previewer. Remove any external collection that requires authentication to load (if the reviewer can't log in, the screen fails). Provide demo credentials in the App Review notes.
4. Placeholder Content
Symptom: Rejection citing incomplete or placeholder content.
Fix: Remove ALL placeholder text ("Lorem ipsum", "Coming soon", "Test"). Populate all screens with real or realistic content. Every feature visible in the app must be functional - don't submit with features behind "coming soon" labels.
5. In-App Purchase Misconfiguration
Symptom: Rejection related to in-app purchases not loading or not being submitted for review.
Fix: If your app uses Stripe for payments, Apple may reject it - apps sold through the App Store must use Apple's in-app purchase system for digital goods. Physical goods and services can use Stripe. Submit your IAPs for review alongside the app binary.
6. Missing App Tracking Transparency
Symptom: Rejection citing Guideline 5.1.2 - App Tracking Transparency.
Fix: If your app uses any analytics SDK (including OneSignal or Facebook), you must implement Apple's ATT prompt. In Adalo, this is configured through the native build settings. Declare all third-party SDKs in your App Store Connect privacy section.
7. Insufficient Functionality
Symptom: Apple says your app doesn't offer enough functionality to justify being a native app.
Cause: If your Adalo app is essentially a wrapper around a website or contains only a few screens with basic CRUD, Apple may reject it as better suited for a web app.
Fix: make sure your app offers genuine native functionality: push notifications, offline capability, device-specific features. Add enough screens and features to demonstrate value beyond what a mobile website could offer.
Pre-Submission Checklist
- ☐ iPad compatibility setting enabled via Adalo support
- ☐ Privacy policy hosted and linked in-app AND App Store Connect
- ☐ All placeholder content removed
- ☐ Demo credentials provided in App Review notes
- ☐ Tested on physical iPhone AND iPad
- ☐ All external collections have error handling
- ☐ ATT prompt implemented if using analytics
- ☐ Screenshots match the actual app (not mockups)
- ☐ All IAPs submitted alongside the binary
- ☐ App description accurately describes all features
Google Play Differences
Google Play is generally more lenient than Apple, but Adalo apps face specific issues:
- Data Safety form: You must accurately declare all data collection in the Play Console
- Target API level: Google requires targeting recent Android API levels. Adalo handles this in their build pipeline, but outdated Adalo versions may fall behind
- 20 Tester requirement: New developer accounts must have 20 testers for 14 continuous days before publishing publicly
When to Hire an Expert
If your app has been rejected twice for the same reason, or if Apple requests changes you can't make within Adalo's builder, you need expert help. Rehost handles the entire App Store submission process - from pre-submission audit to approval. Get Expert Rescue →
FAQ
How long does Apple take to review an Adalo app?
Typically 24–48 hours for the first review. Resubmissions after rejection usually take another 24–48 hours. Expedited reviews are available for critical fixes but require justification.
Can Adalo apps pass Apple's review?
Yes, absolutely. Thousands of Adalo apps are live on the App Store. The key is addressing iPad compatibility, privacy compliance, and content completeness before submitting.
Should I publish on Google Play first?
Many builders do. Google Play's review is faster and more lenient, which lets you validate the app with real users while preparing for Apple's stricter review.