Guideline 4.8 rejection: Login Services — Sign in with Apple
How the rejection usually reads: "Your app uses a third-party login service but does not offer Sign in with Apple as an equivalent option"
Why it happens
If the app offers Google, Facebook or any other third-party social login, Apple requires an equivalent privacy-focused option — Sign in with Apple, or another service that limits data collection. The scan checks for the third-party SDKs and for ASAuthorizationAppleIDProvider; if the first is there and the second is not, expect this rejection.
What can be checked before you submit
1 of RejectProof’s checks map to Guideline 4.8. Each one reads your .ipa — no upload — and reports the evidence with a fix.
- Third-party social login without Sign in with Apple
PB-19 · guideline 4.8 · probable
If you offer Facebook/Google login you must also offer Sign in with Apple with equal prominence. Expo: add expo-apple-authentication. Swift: AuthenticationServices framework + ASAuthorizationAppleIDButton.
What a scan cannot tell you
Static checks read the build; they do not run it. Whether a reviewer likes your design, agrees with your content, or considers the app “sufficiently different” is their call. Fix the mechanical layer first so the human review is about your product, not about a missing plist key.