# Guideline 4.8 Login Services: Sign in with Apple > Rejected under Guideline 4.8 for offering Google or Facebook login without Sign in with Apple? When it’s required, how to add it, and what to reply. **Guideline 4.8 — Login Services: add Sign in with Apple.** The app offers Google, Facebook or another third-party login, but no equivalent option that limits data to name and email and lets people hide their email. Sign in with Apple is the usual fix. Apps that only use their own email and password accounts don’t need it. - App Store · Guideline 4.8. Login Services: add Sign in with Apple. - Interactive page: https://capwr.app/free-tools/app-store-rejection-explainer/guideline-4-8-sign-in-with-apple - Rejection explainer: https://capwr.app/free-tools/app-store-rejection-explainer - Last updated: 2026-10-14 ## What this rejection means The app offers Google, Facebook or another third-party login, but no equivalent option that limits data to name and email and lets people hide their email. Sign in with Apple is the usual fix. Apps that only use their own email and password accounts don’t need it. ## Why reviewers send it Apple requires a privacy-friendly alternative whenever an app’s main sign-in is a third-party or social login: one that only collects name and email and lets people hide their email. Sign in with Apple meets that by design. ## The message App Review sends ``` Guideline 4.8 - Design - Login Services The app uses a third-party login service, but does not appear to offer an equivalent login option with the required privacy features. ``` The exact wording changes from one review to the next; the guideline number is what to look for. ## How to fix it 1. Add Sign in with Apple next to the other social logins, with the same size and position. 2. Turn on the Sign in with Apple capability for the App ID and in the Xcode project, and enable the Apple provider in your auth service (Supabase, Firebase…). 3. Upload a new build. ## Fix it with Lovable, Bolt or Cursor If the app was built with an AI builder, paste this into it, then check the result on a phone: ``` Add Sign in with Apple to the sign-in screen next to Google, same size and position, using our auth provider’s Apple sign-in and a native Capacitor Sign in with Apple plugin on iOS. ``` ## What to reply in App Store Connect Replace the [brackets] with what you actually changed: ``` Guideline 4.8 — The sign-in screen now offers Sign in with Apple alongside [Google], as an equivalent option. ``` ## Got a different message? Paste the whole rejection into the [rejection explainer](https://capwr.app/free-tools/app-store-rejection-explainer). It recognises this one and 26 others, in your browser — nothing is uploaded. ## Other App Store rejections - [App Store Guideline 4.3 Spam rejection](https://capwr.app/free-tools/app-store-rejection-explainer/guideline-4-3-spam) - [Guideline 4.2 Minimum Functionality rejection](https://capwr.app/free-tools/app-store-rejection-explainer/guideline-4-2-minimum-functionality) - [Guideline 2.1 App Completeness rejection](https://capwr.app/free-tools/app-store-rejection-explainer/guideline-2-1-app-completeness) - [Guideline 2.1 Information Needed: demo account](https://capwr.app/free-tools/app-store-rejection-explainer/guideline-2-1-information-needed-demo-account) - [Guideline 4.0 Design rejection: sign-in in Safari](https://capwr.app/free-tools/app-store-rejection-explainer/guideline-4-0-design) - [Guideline 2.3.3 Accurate Metadata: screenshots](https://capwr.app/free-tools/app-store-rejection-explainer/guideline-2-3-3-screenshots) - [Guideline 2.3.10: Android mentioned in the app](https://capwr.app/free-tools/app-store-rejection-explainer/guideline-2-3-10-other-platforms) - [Guideline 2.3.8: app icon or name doesn’t match](https://capwr.app/free-tools/app-store-rejection-explainer/guideline-2-3-8-app-icon) - [Guideline 5.1.1(v): account deletion required](https://capwr.app/free-tools/app-store-rejection-explainer/guideline-5-1-1-v-account-deletion) - [Guideline 5.1.1: permission purpose string](https://capwr.app/free-tools/app-store-rejection-explainer/guideline-5-1-1-purpose-string) - [Guideline 5.1.1: sign-up required to use the app](https://capwr.app/free-tools/app-store-rejection-explainer/guideline-5-1-1-sign-up-required) - [Guideline 5.1.1(i): privacy policy link missing](https://capwr.app/free-tools/app-store-rejection-explainer/guideline-5-1-1-i-privacy-policy) - [Guideline 5.1.2: App Tracking Transparency](https://capwr.app/free-tools/app-store-rejection-explainer/guideline-5-1-2-app-tracking-transparency) - [Guideline 3.1.1: digital goods without In-App Purchase](https://capwr.app/free-tools/app-store-rejection-explainer/guideline-3-1-1-in-app-purchase) - [Guideline 3.1.2: subscription information missing](https://capwr.app/free-tools/app-store-rejection-explainer/guideline-3-1-2-subscriptions) - [Guideline 1.5: support URL doesn’t work](https://capwr.app/free-tools/app-store-rejection-explainer/guideline-1-5-support-url) ## Fixed it? Send the build back to App Review CapWrapp builds the fixed commit on GitHub’s Mac machines, uploads it to TestFlight, and sends the build you pick to App Review from one page — no Xcode. [Get started free](https://capwr.app/login). ## About CapWrapp CapWrapp turns a web app on GitHub — built with Lovable, Bolt, Base44, Cursor or by hand — into iPhone and Android apps. It adds Capacitor if the repo needs it, signs the builds, and ships them to TestFlight and Google Play from GitHub Actions, with no Mac or Xcode on your side. [Get started free](https://capwr.app/login) · [Lovable to App Store guide](https://capwr.app/guides/lovable-to-app-store)