Third-party social login without Sign in with Apple
Check PB-19 · App Store Review Guideline 4.8 · Probable rejection · verified 2026-09-16
Why App Review rejects under Guideline 4.8
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.
How to fix it
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.
How RejectProof detects it
The scan reads your .ipa in the browser (or locally with npx rejectproof): Info.plist, entitlements, the privacy manifest, embedded frameworks and the executable itself. Check PB-19 reports the exact evidence it found — the key, the symbol, the file or the URL — so you can confirm it in your own project before changing anything. Nothing is uploaded; only a small redacted summary is sent to build the report, and you see it first.