What this rejection means
The app offers Google, Facebook or another third-party login, but no equivalent option that limits data to name and email and lets people hide their email. Sign in with Apple is the usual fix. Apps that only use their own email and password accounts don’t need it.
Why reviewers send it
Apple requires a privacy-friendly alternative whenever an app’s main sign-in is a third-party or social login: one that only collects name and email and lets people hide their email. Sign in with Apple meets that by design.
The message App Review sends
Guideline 4.8 - Design - Login Services
The app uses a third-party login service, but does not appear to offer an equivalent login option with the required privacy features.The exact wording changes from one review to the next; the guideline number is what to look for.
How to fix it
- Add Sign in with Apple next to the other social logins, with the same size and position.
- Turn on the Sign in with Apple capability for the App ID and in the Xcode project, and enable the Apple provider in your auth service (Supabase, Firebase…).
- Upload a new build.
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:
Add Sign in with Apple to the sign-in screen next to Google, same size and position, using our auth provider’s Apple sign-in and a native Capacitor Sign in with Apple plugin on iOS.What to reply in App Store Connect
Replace the [brackets] with what you actually changed:
Guideline 4.8 — The sign-in screen now offers Sign in with Apple alongside [Google], as an equivalent option.Got a different message?
Paste the whole rejection into the 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
- Guideline 4.2 Minimum Functionality rejection
- Guideline 2.1 App Completeness rejection
- Guideline 2.1 Information Needed: demo account
- Guideline 4.0 Design rejection: sign-in in Safari
- Guideline 2.3.3 Accurate Metadata: screenshots
- Guideline 2.3.10: Android mentioned in the app
- Guideline 2.3.8: app icon or name doesn’t match
- Guideline 5.1.1(v): account deletion required
- Guideline 5.1.1: permission purpose string
- Guideline 5.1.1: sign-up required to use the app
- Guideline 5.1.1(i): privacy policy link missing
- Guideline 5.1.2: App Tracking Transparency
- Guideline 3.1.1: digital goods without In-App Purchase
- Guideline 3.1.2: subscription information missing
- Guideline 1.5: support URL doesn’t work