Real-World Cases

Rejected by App Review: Asking for credentials but I only use Sign in with Apple

Fix: Added explanation in App Review notes that the app only uses Sign in with Apple and the reviewer should use their own Apple ID to test.

Guideline 4.8 - Design - Sign in with Apple. Your Sign in with Apple implementation does not properly handle the credential revocation notification.

Fix: Added listener for credential revocation notification. When received, log the user out and show re-authentication screen. Check credential state on each app launch using getCredentialState(forUserID:)...

Guideline 4.8 - Design - Sign in with Apple. Your Sign in with Apple implementation does not handle the private relay email correctly.

Fix: Updated email validation to accept Apple private relay email addresses. Configured email forwarding through Apple to ensure transactional emails reach users. Never require users to provide a non-relay...

Guideline 4.8 - Design - Sign in with Apple. Your app uses only email/password authentication. Sign in with Apple must be offered when any third-party or social login is available.

Fix: Added Sign in with Apple as a login option. Even though no other social login was present, Apple now recommends it for all apps. Implementation was straightforward with the react-native-apple-authenti...

Guideline 4.8 - Design - Sign in with Apple. Your Sign in with Apple button size and placement does not meet the Human Interface Guidelines.

Fix: Made Sign in with Apple button the same size as Google and Facebook buttons. Placed all three at the top of the login screen with equal visual prominence. Used the official ASAuthorizationAppleIDButto...

Guideline 4.8 - Design - Sign in with Apple. Your app offers Continue with Phone Number as the only login option. Sign in with Apple must be available.

Fix: Added Sign in with Apple alongside phone number login. Both are presented as equal options. The phone number flow still works for users who prefer it but Apple sign-in must be available.

Guideline 4.8 - Design - Sign in with Apple. Your app uses Google Sign-In and email login but does not offer Sign in with Apple as an option.

Fix: Added Sign in with Apple using AuthenticationServices framework. Placed it as the first option on the login screen. Made sure it handles the private relay email properly. Common mistake for first-time...

Guideline 4.8 - Your app requires email/password registration but does not offer Sign in with Apple as an alternative.

Fix: Added Sign in with Apple as an option alongside email registration. For enterprise users, they can still use company SSO. For individual users or trial signups, Sign in with Apple provides a quick onb...

Guideline 4.8 - Design - Sign in with Apple. Apps that exclusively use a third-party login service must also offer Sign in with Apple.

Fix: Added Sign in with Apple alongside Okta SSO. For enterprise users, they still use Okta. For individual users or trial accounts, Sign in with Apple is the primary option. Both paths lead to the same au...

App requires users to provide their name after using Sign in with Apple

Fix: Made name field optional after Sign in with Apple. Used the name provided by Apple if user chose to share it.

Guideline 4.8 - Design - Sign in with Apple. Your game uses Game Center but does not offer Sign in with Apple for non-Game Center features.

Fix: Added Sign in with Apple as an option for the account system alongside Game Center. Users can link both for the complete experience. Sign in with Apple handles identity while Game Center handles gamin...

Guideline 4.8 - Sign in with Apple - Your app uses Google and Facebook login but does not offer Sign in with Apple as an equivalent option.

Fix: Added Sign in with Apple alongside Google and Facebook. Ensured it appears as the first option and has equal prominence. Handled the private email relay correctly and supported the name-sharing prefer...

Must include Sign in with Apple alongside other third-party logins

Fix: Implemented Sign in with Apple using AuthenticationServices framework. Created proper backend handling for Apple's relay email addresses.

Guideline 4.8 - Your app offers Sign in with Google but the Sign in with Apple option is hidden in a secondary menu. Both login options must have equal prominence.

Fix: Redesigned the login screen to show Sign in with Apple and Sign in with Google as equally sized buttons side by side. Sign in with Apple uses Apples official button style and is positioned first. Both...

Rejected because registration form asks for information after Sign in with Apple

Fix: Made all additional profile fields optional. Only used the data Apple provides through SIWA (name and email if shared). Stopped requiring users to fill in extra information.

Guideline 4.8 - Design - Sign in with Apple. Your app includes a Sign up with email option that creates an account but does not offer Sign in with Apple.

Fix: Added sign_in_with_apple Flutter package. Implemented Sign in with Apple as the first login option. Handled both real and private relay email addresses. Added account linking for users who sign in wit...

Your app uses Sign in with Apple as a login option but does not use Sign in with Apple button design, branding and/or user interface elements.

Fix: Replaced custom SIWA button with ASAuthorizationAppleIDButton which automatically uses Apple's official design.