Sign in with Apple Requirement (2026): Avoid App Store Rejection
If your iOS app offers any third-party or social sign-in option — Google, Facebook, GitHub, Apple's own Game Center, or anything else — Apple generally requires you to also offer Sign in with Apple under App Store Review Guideline 4.8. The rule is straightforward in principle, but the edge cases cause rejections every week. This article covers the decision tree, the exact setup steps, and the most common mistakes that get apps rejected.
Quick checklist: Do you need Sign in with Apple?
| Your app has… | Sign in with Apple required? |
|---|---|
| Google, Facebook, or other social sign-in | Yes |
| Only email/password (no third-party providers) | No |
| Only Sign in with Apple | No (already have it) |
| Apple Game Center login | Check current guideline — Game Center alone may not trigger the requirement |
| No login at all (anonymous/guest app) | No |
| Enterprise app (not on public App Store) | No |
What Guideline 4.8 actually says
Apple's review guideline for Sign in with Apple states that if your app offers account creation through third-party services (like social media platforms), you must also offer Sign in with Apple as an equivalent option. The key phrase is "as an equivalent option" — it must be presented with the same prominence and ease of use as your other sign-in buttons. You cannot bury it below a "More options" link while making Google sign-in prominent.
The requirement applies to apps that offer third-party sign-in. If your app only uses email/password, phone-based authentication, or no authentication at all, Sign in with Apple is not required. However, many developers add Google or Facebook sign-in later and forget to add Sign in with Apple in the same release.
Implementation checklist
1. Enable the capability in Xcode
Open your project in Xcode, go to the Signing & Capabilities tab for your target, click "+ Capability", and add "Sign in with Apple". Ensure the capability is present in your App ID in the Apple Developer Portal.
2. Add the Sign in with Apple button
For Flutter apps, use the sign_in_with_apple package. Present the button with the same visual prominence as your other sign-in options. The button should use Apple's official ASAuthorizationAppleIDButton styling on iOS.
3. Handle the authorization flow
The authorization flow returns a user identifier, full name, and email (on first authorization only). Store the user identifier server-side — do not rely on the email or name, as the user can change them in Apple Settings. Implement the authorization request, handle cancellation, and manage the authorization state.
4. Add Sign in with Apple to your privacy policy
Your privacy policy must disclose that you use Sign in with Apple and what data you receive from it (user identifier, name, email if provided). This aligns with the privacy labels you declare in App Store Connect.
5. Test the flow in a release build
Test Sign in with Apple in a release build before submitting. Sign in, verify the token works with your backend, sign out, and sign back in. Apple reviewers will test this flow, so make sure it works end-to-end.
Common rejection mistakes
- Asymmetric prominence: Google sign-in button is large and centered, Sign in with Apple is small or below the fold. Apple expects equal treatment.
- Missing capability: The Sign in with Apple capability is not added in Xcode, so the button crashes when tapped.
- No backend validation: The app sends the authorization code to your server but your server doesn't verify it with Apple. This is a security risk.
- Not handling email relay: Apple's private email relay forwards to the user's real email. If your app sends emails, test that relay addresses work.
- Forgetting to revoke: Users can revoke Sign in with Apple access from Settings. Your app should handle revoked access gracefully.
Before you submit
If your app uses Sign in with Apple or any third-party sign-in, run a free Launch Score check before submitting to App Store review. The scan catches missing capabilities, untested auth flows, and other rejection risks in a few minutes.
Frequently asked questions
When is Sign in with Apple required?
Sign in with Apple is required when your iOS app offers any third-party or social sign-in option (Google, Facebook, GitHub, etc.). If your app only uses email/password or no authentication, it is not required. Apple App Store Review Guideline 4.8 covers this requirement.
Does Sign in with Apple need to be as prominent as Google sign-in?
Yes. Apple requires Sign in with Apple to be presented with the same visual prominence and ease of use as other sign-in options. You cannot bury it below a More Options link while making Google sign-in prominent.
How do I add Sign in with Apple in Flutter?
Use the sign_in_with_apple Flutter package. Enable the Sign in with Apple capability in Xcode, add the sign-in button with equal prominence to other providers, handle the authorization flow, and verify the token server-side. Test in a release build before submitting.