Guideline4.8
Login Services
4.8 is narrow. If you offer a third-party social login, Apple expects Sign in with Apple on the same screen, with equivalent features, unless you qualify for an exception.
§ 01What this rejection usually means
- Google, Facebook, WeChat, Line, or similar on the login screen is the usual trigger.
- A company-owned login (your own email OTP, your own account system) is not automatically 4.8.
- Hiding Sign in with Apple behind “More options” while Google is prominent still fails.
§ 02Common causes
- Google or Facebook login shipped, Sign in with Apple did not.
- Sign in with Apple exists but fails, or does not create the same account.
- The button is not on the same screen as the other social buttons.
- You collect name and email from Google but not from Apple’s hidden-email relay.
§ 03How to diagnose your case
- Screenshot the login screen as a reviewer would see it on first launch.
- If a third-party login is there and Sign in with Apple is not, you need a new build. A reply will not substitute.
- If Sign in with Apple is there and broken, treat it like 2.1 plus 4.8: fix the binary, then describe the path.
§ 05What to inspect in your project
Checklist
- Sign in with Apple capability on the App ID
- Button on the same screen as other third-party logins
- Existing users can bind an Apple ID without losing data
- Hide My Email is handled; the relay address is stored
- Review Notes mention a test Apple ID if the flow is gated
§ 06What not to do
Do not
- Do not remove Google login as a dodge if you still need it — add Apple or drop all third-party logins.
- Do not put Sign in with Apple only in Settings.
- Do not appeal 4.8 by quoting an exception that does not apply to a consumer social login.
§ 07Questions people ask next
- Is email-and-password login enough to skip Sign in with Apple?
- Yes, if that is the only login. 4.8 triggers when another third-party login is offered. Email OTP you own is not a third-party login.