# Guideline 4.0 Design rejection: sign-in in Safari

> Rejected under Guideline 4.0 Design because sign-in opens Safari or the layout breaks on iPad? How to keep users in the app, and what to reply.

**Guideline 4.0 — Design: a poor experience, often sign-in in Safari.** Guideline 4.0 is the general design bar. For wrapped apps it usually means sign-in, sign-up or a purchase opens in Safari instead of staying in the app, or the layout is crowded or cut off on iPad.

- App Store · Guideline 4.0. Design: a poor experience, often sign-in in Safari.
- Interactive page: https://capwr.app/free-tools/app-store-rejection-explainer/guideline-4-0-design
- Rejection explainer: https://capwr.app/free-tools/app-store-rejection-explainer
- Last updated: 2026-10-14

## What this rejection means

Guideline 4.0 is the general design bar. For wrapped apps it usually means sign-in, sign-up or a purchase opens in Safari instead of staying in the app, or the layout is crowded or cut off on iPad.

## Why reviewers send it

Apple expects an app to feel finished on every device it runs on. Sending people to Safari to sign in or pay breaks the flow, and a layout that is cramped or cut off on an iPad — where iPhone apps also run — looks unfinished.

## The message App Review sends

```
Guideline 4.0 - Design

We noticed that the user is taken to the default web browser to sign in or register for an account, which provides a poor user experience.
```

The exact wording changes from one review to the next; the guideline number is what to look for.

## How to fix it

1. Keep sign-in in the app: an in-app browser sheet (@capacitor/browser) or a native sign-in plugin, returning to the app with a deep link.
2. Don’t send people to your website to finish anything they started in the app.
3. Check every screen at iPad size. An iPhone-only app still has to work when it runs on an iPad.
4. Upload a new build and describe what changed.

## Fix it with Lovable, Bolt or Cursor

If the app was built with an AI builder, paste this into it, then check the result on a phone:

```
Keep sign-in, sign-up and checkout inside the app: open OAuth in an in-app browser sheet with @capacitor/browser and come back with a deep link, never in Safari. Make every screen lay out cleanly at iPad sizes.
```

## What to reply in App Store Connect

Replace the [brackets] with what you actually changed:

```
Guideline 4.0 — Sign-in now happens inside the app [with an in-app sheet / Sign in with Apple] and returns to the app automatically. We also fixed the layout of [screens] on iPad.
```

## Got a different message?

Paste the whole rejection into the [rejection explainer](https://capwr.app/free-tools/app-store-rejection-explainer). It recognises this one and 26 others, in your browser — nothing is uploaded.

## Other App Store rejections

- [App Store Guideline 4.3 Spam rejection](https://capwr.app/free-tools/app-store-rejection-explainer/guideline-4-3-spam)
- [Guideline 4.2 Minimum Functionality rejection](https://capwr.app/free-tools/app-store-rejection-explainer/guideline-4-2-minimum-functionality)
- [Guideline 2.1 App Completeness rejection](https://capwr.app/free-tools/app-store-rejection-explainer/guideline-2-1-app-completeness)
- [Guideline 2.1 Information Needed: demo account](https://capwr.app/free-tools/app-store-rejection-explainer/guideline-2-1-information-needed-demo-account)
- [Guideline 2.3.3 Accurate Metadata: screenshots](https://capwr.app/free-tools/app-store-rejection-explainer/guideline-2-3-3-screenshots)
- [Guideline 2.3.10: Android mentioned in the app](https://capwr.app/free-tools/app-store-rejection-explainer/guideline-2-3-10-other-platforms)
- [Guideline 2.3.8: app icon or name doesn’t match](https://capwr.app/free-tools/app-store-rejection-explainer/guideline-2-3-8-app-icon)
- [Guideline 4.8 Login Services: Sign in with Apple](https://capwr.app/free-tools/app-store-rejection-explainer/guideline-4-8-sign-in-with-apple)
- [Guideline 5.1.1(v): account deletion required](https://capwr.app/free-tools/app-store-rejection-explainer/guideline-5-1-1-v-account-deletion)
- [Guideline 5.1.1: permission purpose string](https://capwr.app/free-tools/app-store-rejection-explainer/guideline-5-1-1-purpose-string)
- [Guideline 5.1.1: sign-up required to use the app](https://capwr.app/free-tools/app-store-rejection-explainer/guideline-5-1-1-sign-up-required)
- [Guideline 5.1.1(i): privacy policy link missing](https://capwr.app/free-tools/app-store-rejection-explainer/guideline-5-1-1-i-privacy-policy)
- [Guideline 5.1.2: App Tracking Transparency](https://capwr.app/free-tools/app-store-rejection-explainer/guideline-5-1-2-app-tracking-transparency)
- [Guideline 3.1.1: digital goods without In-App Purchase](https://capwr.app/free-tools/app-store-rejection-explainer/guideline-3-1-1-in-app-purchase)
- [Guideline 3.1.2: subscription information missing](https://capwr.app/free-tools/app-store-rejection-explainer/guideline-3-1-2-subscriptions)
- [Guideline 1.5: support URL doesn’t work](https://capwr.app/free-tools/app-store-rejection-explainer/guideline-1-5-support-url)

## Fixed it? Send the build back to App Review

CapWrapp builds the fixed commit on GitHub’s Mac machines, uploads it to TestFlight, and sends the build you pick to App Review from one page — no Xcode.

[Get started free](https://capwr.app/login).

## About CapWrapp

CapWrapp turns a web app on GitHub — built with Lovable, Bolt, Base44, Cursor or by hand — into iPhone and Android apps. It adds Capacitor if the repo needs it, signs the builds, and ships them to TestFlight and Google Play from GitHub Actions, with no Mac or Xcode on your side. [Get started free](https://capwr.app/login) · [Lovable to App Store guide](https://capwr.app/guides/lovable-to-app-store)
