Guideline 4.8

Guideline 4.8 - Design: Sign in with Apple Required

Medium FixTypical Fix: 1-3 days1 Report
Also known as:App uses third-party login but doesn't offer Sign in with AppleSign in with Apple not offered as equivalent login optionLogin service does not meet all privacy requirementsMissing equivalent login option with required privacy features

Our Take

Apple is rejecting your app because it offers third-party login (Google, Facebook, email, etc.) but does not also offer Sign in with Apple as an equivalent login option. Since iOS 13, any app that offers third-party authentication must also offer Sign in with Apple. Additionally, the Sign in with Apple option must meet specific requirements: it must limit data collection to user name and email, allow users to keep their email private (via Apple's relay), keep the user's account private from all parties, and not collect interactions with the app for advertising purposes without consent. Importantly, Sign in with Apple must be a login service — meaning it meets all the requirements in guideline 4.8. If it's already implemented but doesn't meet all requirements, Apple may ask you to identify which login service meets them via App Store Connect.

Resolution Guide

01

Add Sign in with Apple capability

In Xcode, go to your target → Signing & Capabilities → + Capability → Sign in with Apple.

02

Implement AuthenticationServices

Use Apple's AuthenticationServices framework. Add an ASAuthorizationAppleIDButton to your login screen.

03

Handle the full flow

Implement the authorization request, handle the credential response (user ID, email, full name), and create/link accounts on your backend.

04

Handle email relay

Users may choose to hide their email. Your app receives a relay address (xyz@privaterelay.appleid.com). Make sure your backend and email systems support this.

05

Give it equal prominence

Sign in with Apple should be visually equivalent to other login options — same size, same prominence, same screen.

06

Handle account linking

If a user already signed up with email/Google and later signs in with Apple using the same email, handle the account merge gracefully.

07

Make Sign in with Apple the first option

Apple requires that their auth be the first option among your list of login/signup options.

Prevention


  • Add Sign in with Apple from the start if you have any social login
  • Test the full flow including email relay
  • Follow Apple's HIG for button placement and styling
  • Note: apps that exclusively use your own account system (no third-party auth) may not need Sign in with Apple
  • Example Rejection Email

    From:Apple App Review Team
    Subject:Guideline 4.8 - Design: Sign in with Apple Required
    The app uses a third party login service, but does not appear to offer as an equivalent login option another login service with all of the following features: - The login option limits data collection to the user's name and email address. - The login option allows users to keep their email address private from all parties as part of setting up their account. - The login option does not collect interactions with the app for advertising purposes without consent. Revise the app to offer as an equivalent login option another login service that meets all of the above requirements. If the app already includes another login service that meets all of the above requirements, identify which login service meets all of the requirements, and explain why it meets all of the requirements in App Review in App Store Connect. Note that Sign in with Apple is a login service that meets all the requirements specified in guideline 4.8.

    Before & After

    Before — Rejected

    Login screen with 'Continue with Google' and 'Continue with Facebook' buttons, no Apple option

    After — Approved

    Login screen with 'Sign in with Apple' button at the same size and prominence as Google and Facebook options

    What changed: Any app offering third-party authentication must also offer Sign in with Apple as an equivalent option

    Community Solutions · 0

    Sign in to share your solution.

    More Guideline 4 (Design) rejections

    View all Guideline 4 rejections