App Store guides

Rejected for missing Sign in with Apple? Here's what Guideline 4.8 requires

A 4.8 rejection almost always means the app offers a third-party login without offering Sign in with Apple alongside it. The fix is usually smaller than the rejection message makes it sound.

Guideline 4.8
2 min readUpdated August 2026 Official Apple source
Sign in with Apple

When Guideline 4.8 actually applies

It only applies if your app already offers a third-party or social login — Google, Facebook, X, or similar — as a way to create an account or sign in.

If your app only uses its own email/password system, or doesn't require an account at all, Sign in with Apple is not required.

The moment any third-party login option exists, Sign in with Apple must be offered as an equivalent — this is the part developers most often miss.

What counts as an 'equivalent' option

Sign in with Apple needs comparable visual prominence to your other login options — not smaller, not buried below a scroll, not listed last with less weight.

It must support Apple's private email relay so users can hide their real email address, same as your other providers let them limit shared data.

Whatever your app requires other social logins to work (name, email) should not ask for more from Apple sign-in than it needs.

Account deletion has to work for Apple-authenticated accounts too, not just accounts created through other providers.

False-positive triggers worth checking first

Sign in with Apple exists in the build but the reviewer couldn't reach it — check it isn't hidden behind a flow only accessible after another login step.

The capability wasn't actually enabled for this build — verify the Sign In with Apple entitlement is checked in Xcode and configured in App Store Connect, not just coded.

Review notes described a login flow but didn't mention Sign in with Apple exists, so the reviewer had no reason to look for it.

How to fix it

Implement Sign in with Apple using AuthenticationServices if it isn't there yet, or fix visibility/entitlement if it already is.

Give it equal or higher placement among login options — Apple's own guidance is to list it at least as prominently as other third-party providers.

Add review notes that explicitly point to where Sign in with Apple appears, plus demo credentials for your other login method so the reviewer can confirm parity.

Replying in Resolution Center

Confirm the build number the fix shipped in.

Describe the exact screen and button where Sign in with Apple now appears.

State plainly that no other third-party login remains without an Apple equivalent.

Get a reviewer-safe reply drafted for you

Sign in to AcceptMyApp, paste your 4.8 rejection message, and get a guideline-aware Resolution Center reply — plus a check that no other login provider is missing its Apple counterpart.

Get started