App Store Rejection 4.2: How to Get Your WebView App Approved

You submitted your app. About a day later, App Store Connect showed a rejection along these lines (each reviewer words it differently):

If you're reading this, you probably just got rejected for Guideline 4.2. Don't panic — this is the most common rejection for web-wrapper apps, and it's usually fixable.

4.2 rejections come in a handful of shapes, and the reviewer's note almost always tells you which one you got. Here is what each shape means, and what actually clears it.

What is Guideline 4.2?

Guideline 4.2 is part of Apple's App Store Review Guidelines. The guideline opens:

"Your app should include features, content, and UI that elevate it beyond a repackaged website. If your app is not particularly useful, unique, or 'app-like,' it doesn't belong on the App Store."

It goes on: “If your App doesn't provide some sort of lasting entertainment value or adequate utility, it may not be accepted.” Two of its subsections matter most for WebView apps. 4.2.2: “Other than catalogs, apps shouldn't primarily be marketing materials, advertisements, web clippings, content aggregators, or a collection of links.” 4.2.6: “Apps created from a commercialized template or app generation service will be rejected unless they are submitted directly by the provider of the app's content.” If you build with a service such as Code2Native, submit from your own Apple Developer account; Code2Native does not submit apps for you. Apple last revised the guidelines on June 8, 2026; section 4.2 was not among the changes.

In plain English: Apple doesn't want the App Store filled with apps that are just WebViews loading websites. They want apps that provide value beyond what Safari can offer.

Why Apple Rejects WebView Apps

Before we talk solutions, let's understand Apple's perspective:

• User experience: Safari already exists. If your app does nothing Safari can't do, why should users download it?
• Store quality: Apple wants to curate a high-quality app ecosystem. Low-effort wrappers dilute that.
• Security: WebView apps that load arbitrary content can be exploited for phishing or malware distribution.

Understanding these concerns helps you address them proactively in your submission.

7 Changes That Address a 4.2 Rejection

Each of these answers a specific thing reviewers look for. Implement as many as apply to your app.

Pre-Submission Checklist

Before resubmitting, check which of these your app really has. Apple sets no number; what matters is whether the app does something useful beyond your website.

A Reply to App Review When You Resubmit

If you changed the app, say so in the App Review section of the app's page in App Store Connect when you resubmit. Be specific and list only features your build has (Code2Native's iOS builds do not include push). If you made no changes because you believe the reviewer misunderstood the app, you can appeal to the App Review Board instead: give specific reasons the app complies, and submit only one appeal per rejected submission.

When to Consider Web Clips

If your app genuinely has no native features to add (e.g., it's a static content site), consider using a Web Clip instead:

• Web Clips are bookmark shortcuts that appear as app icons on the home screen
• They don't require App Store approval
• They are not App Store submissions, so App Review and Guideline 4.2 do not apply to them

This is a legitimate alternative for informational sites that don't need app functionality.

Final Thoughts

Guideline 4.2 rejections are frustrating, but they're Apple's way of maintaining quality. The solution isn't to trick the review process — it's to genuinely add value.

Ask yourself: What can my app do that Safari can't?

If you can answer that with specific features people use, describe them in your review notes. If you can't, maybe a web clip or PWA is the right solution.