Guideline 4.8 rejection (Login Services (Sign in with Apple)): what it means and how to fix it
Your app offers Google, Facebook or another third-party login but no equivalent privacy-friendly option like Sign in with Apple.
What Apple is saying
If your app uses a third-party or social login (Google, Facebook, X and so on) as its main way to sign in, it must also offer another login option that limits data collection to name and email, lets users keep their email private, and doesn't track them for ads. Sign in with Apple meets all of that, so it's the usual fix.
Common causes
Google or Facebook sign-in is offered and Sign in with Apple isn't.
Sign in with Apple is offered but hidden or less prominent than other options.
Sign in with Apple is in the app but the capability or backend setup is broken, so it fails during review.
How to fix it
Enable the Sign in with Apple capability for your app ID and add the entitlement.
Add the Sign in with Apple button alongside the other login buttons, at a similar size and position.
Enable Apple as a provider in your auth backend (Firebase, Supabase, Auth0 and so on) using your app's bundle ID.
Test sign-in on a real device, then upload a new build.
Do you need a new build?
Yes.
Reply to App Review
Send this in Resolution Center (App Store Connect → your app → the rejected version) after fixing. Fill in the [brackets].
Hello,
Thank you for the review. We've added Sign in with Apple as a login option alongside [Google], at equal prominence. It's available on the sign-in screen in build [number].
Got a 4.8 rejection you'd rather not deal with?
I've shipped 7 apps of my own and fixed real rejections on them. Invite me to App Store Connect (no Apple ID password needed), and I'll fix it, reply to Apple and resubmit. From $45, with unlimited revisions until the original rejection is approved.