iOS
Why Apple rejects wrapped web apps (and how to get approved)
November 17, 2026 · 6 min read

Apple usually rejects wrapped web apps under guideline 4.2, because the app feels like a website in a frame rather than an app. The fix is rarely a rebuild. It is usually a handful of changes that make the app feel at home on iPhone.
Those changes are predictable, because the same few problems cause most rejections. Below you will find each problem, the change that fixes it, and a checklist to run before you resubmit. No tool can guarantee approval, but this list removes the most common reasons.
The short answer: guideline 4.2
Guideline 4.2, Minimum Functionality, asks that an app offer more than the website it comes from. So when a reviewer opens your app and sees your website in a frame, they reject it under this rule.
Apple's own words are clear. An app should include features, content and interface that "elevate it beyond a repackaged website". You can read the full text in the App Store Review Guidelines.
That does not mean Apple bans web technology, because many approved apps use web views inside. What the reviewer judges is whether your app feels like an app.
What makes a reviewer think "just a website"
- A browser-style header, cookie banner or "Download our app" prompt inside the app.
- Links that open your marketing pages, blog or footer menus.
- Pages that need pinch-zoom or scroll sideways on a phone.
- A white screen or spinner while the site loads.
- Content that is the same as your public website, with nothing extra.
- No offline message when the connection drops.
How to pass guideline 4.2
To pass, you do not need to rebuild your product; you need to show that it works like an app on iPhone. The four changes below do that, so pick the ones that fit your product.
1. Remove the website parts
Start by hiding your marketing header, footer and cookie banner inside the app. Then open the app on a useful screen, such as the dashboard or sign-in, instead of your landing page.
2. Add real mobile value
Next, add features that use the phone, because they show the reviewer something a website cannot. Push notifications, camera upload, sharing and saving files are good examples. Even one or two well-made features can change the reviewer's view.
3. Handle offline and slow connections
A website shows a browser error when the connection drops; an app should show a clear offline screen instead. Caching your app shell also makes that first screen appear fast. Our PWA readiness checklist covers both.
4. Fix the layout for iPhone
Finally, check how your layout fits the iPhone itself. Content should stay clear of the notch and home bar, the keyboard should not cover buttons, and tap targets should be large enough for thumbs.
Other common rejection reasons
Guideline 4.2 is the most common reason, but other rules also catch web-based apps. These come up often:
- 2.1 App completeness. The reviewer could not sign in, or hit a broken page. Always provide a working demo account in App Store Connect.
- 4.8 Login services. If you offer Google or Facebook sign-in, Apple usually expects an equivalent private option, such as Sign in with Apple.
- 5.1.1 Account deletion. If users can create an account in your app, they must also be able to delete it from inside the app.
- 3.1.1 In-app purchase. Selling digital content or subscriptions inside an iPhone app usually requires Apple's in-app purchase. Rules differ by country, so check before launch.
- Metadata. Screenshots must show the real app, and the description must match what it does.
For a wider overview, read Apple's requirements for web apps in the App Store.
How to reply to a rejection
If you are rejected, start with the message in App Store Connect, because it names the guideline you broke. Fix that exact issue first.
Once it is fixed, reply in the Resolution Center. Keep the reply short and factual: say what you changed and where the reviewer can see it. Screenshots or a short screen recording make that easy to check.
If you believe the reviewer misunderstood your app, you can explain politely or file an appeal. Even then, showing the change works better than arguing.
A checklist before you resubmit
- The app opens on a useful screen, not a landing page.
- No browser bars, cookie banners or "get the app" prompts.
- At least one feature that uses the phone well.
- A clear offline screen.
- A working demo account, written in the review notes.
- Account deletion inside the app, if you have accounts.
- Sign in with Apple, if you offer other social logins.
- Real screenshots from the iPhone app.
Where PWAtoApp fits
PWAtoApp turns your web app into a signed iOS IPA and Android builds, for €49.99 once with unlimited builds. That removes the packaging work, but it does not change your website's content or decide Apple's review. So make the changes above in your web app, test the build with TestFlight, then submit.
FAQ
Can a web app be approved on the App Store at all?
Yes. Many approved apps use web technology inside. Apple checks what the user experiences, not how you built it. An app that feels useful and complete on iPhone has a fair chance.
How long does it take after I resubmit?
Apple reviews most resubmissions within a day or two. A complex case, or an appeal, can take longer.
Will PWAtoApp change my app so Apple accepts it?
No. PWAtoApp packages and signs your existing web app. The content and features come from your web app, so the changes in this guide happen there.
Ready to build for Android and iOS?
€49.99 once includes unlimited Android APK and AAB plus iOS IPA builds, all from one dashboard.
Build my app