App Rejected for Third-Party Login: Sign in with Apple Requirements

When Sign in with Apple Is Required

Apple's Guideline 4.8 requires Sign in with Apple whenever your app uses third-party login services as the primary authentication mechanism. This includes: Google Sign-In, Facebook Login, Twitter/X Login, any OAuth-based third-party login. Exceptions exist for apps that exclusively use company-specific or education accounts, apps that use government or industry-backed identity systems, and apps where third-party login is for a specific third-party account (e.g., a banking app using the bank's login).

Implementation Requirements

Sign in with Apple must be presented as an option at least as prominent as other login methods. It cannot be hidden in a secondary screen or made harder to find than alternatives. The button must use Apple's official design templates. You must handle the relay email service (users can choose to hide their email). You must support the opaque user identifier Apple provides.

Common Implementation Mistakes

Sign in with Apple button is smaller or less prominent than other options (must be equal or larger). App requires additional account setup after Sign in with Apple that is not required for other methods. App does not handle the relay email properly (emails bounce). App crashes when user hides their email address. Sign in with Apple is present but not functional during review.

Frequently Asked Questions

Related Resources