The rejection list
- 4.2
Minimum Functionality
The app looks like the website. Fix: push notifications, offline screen, native share or biometrics via WebViewGold; hide website-only elements in the app; describe the native features in the review notes.
- 2.1
App Completeness / crashes
Blank screen on launch (slow backend, mixed content), dead links, placeholder text, or the reviewer could not log in. Fix: splash screen plus loading indicator, HTTPS everywhere, remove placeholders, provide a demo account.
- 5.1.1
Privacy – data collection and account deletion
Missing privacy policy URL, or sign-up without in-app account deletion. Fix: add /privacy, add a Delete account button that removes the account.
- 4.8
Login Services
Google/Facebook login offered without Sign in with Apple (or equivalent). Fix: enable the Apple provider in Supabase/Firebase/Base44 and add the button; WebViewGold handles the flow.
- 3.1.1
In-App Purchase
Digital subscription or credits sold via Stripe inside the app. Fix: RevenueCat-based IAP in WebViewGold for the iOS app; keep Stripe on the web.
- 2.3
Accurate Metadata
Screenshots that show the website, mentions of Android or "beta", description that promises features that are not there. Fix: screenshots from the real app, honest copy.
- 2.5.4
Background modes / unused permissions
Permission strings for location or camera the app never uses. Fix: delete unused permission texts in the WebViewGold project.
- 1.2
User-generated content
Community or AI-generated content without reporting or moderation. Fix: report button, block option, moderation note in the privacy policy.
- 4.0
Design
Content hidden behind the notch or home indicator, tiny tap targets. Fix: safe-area padding in your CSS (WebViewGold respects safe areas), 44 px targets.
The three-minute pre-submission check
- Open the app in airplane mode: offline screen, not a white page?
- Open every menu item: no dead links, no placeholder content?
- Log in with the demo account you will give Apple: works on the first try?
- Sign-up exists → Delete account exists?
- Social login exists → Sign in with Apple exists?
- Prices for digital goods inside the app → IAP enabled?
- Privacy policy link opens inside the app?
- Run the automated readiness check on your URL.
How to respond to a rejection
Rejections are not final. Reply in Resolution Center, state what you changed (or explain what the reviewer missed, politely and with screenshots), and submit a new build. Most follow-up reviews are faster than the first. If the reason is a non-content issue, the WebViewGold approval guarantee applies: claim within 14 days of purchase and you get a refund. Our 24/7 support chat has seen every rejection text and will help you phrase the reply.
Frequently asked questions
Does Apple reject apps for being built with AI tools?
No. The builder is invisible to Apple. Rejections are about behavior, completeness, privacy and payments.
How many times can I resubmit?
As often as needed. Each submission is reviewed again, usually within a day or two.
Does the guarantee cover content rejections?
No. If Apple rejects your content (for example gambling, medical claims or copyrighted material), that is outside the guarantee, which covers non-content rejections of the WebViewGold-based app.