Guideline 4.2 is Apple's minimum functionality rule. It rejects apps that don't go beyond a repackaged website, which is exactly what a wrapped Lovable web app looks like to a reviewer. To fix it, make the app look and work like an app: native screens and navigation, and nothing that behaves like a browser.
What Guideline 4.2 says
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.
Apple App Review Guideline 4.2
Other than catalogs, apps shouldn't primarily be marketing materials, advertisements, web clippings, content aggregators, or a collection of links.
Apple App Review Guideline 4.2.2
Why Lovable apps hit it
Lovable builds web apps, and the fastest way into the App Store is a wrapper that loads your published site (see your publishing options). That is what Guideline 4.2 is written to catch. Reviewers tend to notice things like:
- Pages that load like a website, with browser-style navigation and no native back gestures.
- Links that open your website, a cookie banner or a site footer inside the app.
- Sign-in that bounces through a web page.
- An app that is identical to the website, with nothing extra on the phone.
How to fix a 4.2 rejection
- Read the rejection note in App Store Connect. It cites the guideline and often says what the reviewer saw.
- Make navigation native: a tab bar or native stack, back gestures, and screens that don't reload like pages.
- Remove web leftovers: cookie banners, website footers, "open in browser" links and anything that sends people to your site.
- Add value that only an app can give, where it fits your product: push notifications, the camera, the share sheet, offline states.
- Make sure sign-in works and give reviewers a demo account (Guideline 2.1).
- Reply in App Store Connect explaining what changed, then resubmit.
If you keep patching a wrapper and it keeps coming back, it is usually faster to convert the app to React Native. See Can Lovable export to React Native or Expo?
Rejections that often come with 4.2
| Guideline | What it requires |
|---|---|
| 2.1 App Completeness | A final build, tested on a device, with demo account details if the app has a login |
| 3.1.1 In-App Purchase | Apple's in-app purchase to unlock features or content, not your own payment flow |
| 4.3 Spam | No duplicate copies of the same app, and nothing indistinguishable from apps already in the store (how to fix it) |
| 4.8 Login Services | If you offer Google or another social login, also offer a privacy-focused option such as Sign in with Apple |
| 5.1.1(v) Account Deletion | If people can create an account in the app, they must be able to delete it in the app |
Check the rest before you resubmit with the Lovable launch checklist.
How LetsDeployIt helps
Fixing rejections is a large part of what we do. We rebuild your Lovable app as a native React Native and Expo app, run a Guideline 4.2 compliance pass, fix what the reviewer flagged and resubmit as many times as it takes. If it complies with the store policies and we can't get it approved, you get your money back. See plans and pricing.
Try a free native preview of your app on your phone: letsdeploy.it.
Common questions about Guideline 4.2
What does Apple Guideline 4.2 mean?
It is the minimum functionality rule. Apple wants apps to offer features, content and UI that go beyond a repackaged website. Apps that are just a website in a shell are rejected under it.
Why was my Lovable app rejected under 4.2?
Usually because it is a wrapper around the Lovable website. To a reviewer it looks and behaves like a website inside an app, which is what 4.2 rejects.
Will adding push notifications fix a 4.2 rejection?
It helps, but rarely on its own. Reviewers look at the whole app: native navigation, no web leftovers and a reason to use the app over the website.
Can I talk to the reviewer?
Yes. You can reply to App Review in App Store Connect to explain your changes or ask what they need, then resubmit.
Should I convert my Lovable app to native instead?
If the app has been rejected more than once, usually yes. A native React Native app avoids the wrapper problem entirely and gives you room to add phone features.
Can you fix my rejected Lovable app?
Yes. We fix what was flagged, resubmit and handle the reviewer replies until it's approved, with unlimited resubmissions included.
Sources
Originally published on letsdeploy.it. Facts checked 2026-10-12.
Top comments (0)