App Store
Rejected under Guideline 4.8 (Login Services): when Sign in with Apple is required and how to add it with Supabase
If your app lets people create or sign in to their account with Google, Facebook or another third-party login, Guideline 4.8 says it must also offer an equivalent login that limits data to name and email, lets people hide their email, and does not track them for ads. Sign in with Apple is the option Apple built for this, and Supabase supports it both in the browser and natively on iOS. Guideline text below is quoted from the version last updated on 2026-10-16.
What you are seeing
The rejection arrives in App Store Connect, on the App Review page of your app. It cites Guideline 4.8 (Login Services, in the Design section) and says that the app uses a third-party login service but does not offer an equivalent login option with the privacy features Apple lists. Read the full message in App Store Connect, not the notification email - the wording varies. Situations that lead to it:
- The login screen offers "Continue with Google" and nothing else.
- The app offers Google plus email and password, and the reviewer still cites 4.8. Having your own email login next to Google does not remove the requirement - see the check below.
- Sign in with Apple exists on your website, but the iOS build does not show it, or it shows it below the fold where the reviewer has to scroll.
- The Sign in with Apple button is there, but tapping it fails in the iOS app, so to the reviewer the option does not exist.
How to check it yourself
Start with the rule itself. Guideline 4.8 does not mention Sign in with Apple by name. It describes the features the other login must have:
“Apps that use a third-party or social login service (such as Facebook Login, Google Sign-In, Log in with X, Sign In with LinkedIn, Login with Amazon, or WeChat Login) to set up or authenticate the user's primary account with the app must also offer as an equivalent option another login service with the following features: the login service limits data collection to the user's name and email address; the login service allows users to keep their email address private as part of setting up their account; and the login service does not collect interactions with your app for advertising purposes without consent.”
The same guideline lists five cases where no other login service is needed. Your app is exempt only if one of them fits:
- The app exclusively uses your company's own account setup and sign-in systems - for example only email and password, with no Google button at all.
- It is an alternative app marketplace (or distributed from one) that uses a marketplace-specific login.
- It is an education, enterprise or business app that requires an existing education or enterprise account.
- It authenticates users with a government or industry-backed citizen ID or electronic ID.
- It is a client for a specific third-party service, and users sign in to their mail, social media or other account there to access their own content.
Note the word "exclusively" in the first exception. If Google is one of the ways to create the main account, your own email login next to it does not make the app exempt, and a plain email-and-password form does not let people keep their email address private. In practice the fix is a login that has all three features, and Sign in with Apple is the one Apple provides for it: the only data an app can request through it are the name and the email address (ASAuthorization.Scope), people can share a random relay address instead of their real one, and Apple says it does not use Sign in with Apple to profile people or their activity in apps (Human Interface Guidelines).
Then check your own app and your own Supabase project. Everything below is read-only.
1. Which sign-in methods does the app offer?
Search the project for social sign-in calls. Run this from the project root (for an app built with an AI tool, from the repository it synced to GitHub):
grep -rnE "signInWithOAuth|signInWithIdToken|provider: *['\"](google|apple|facebook|azure|twitter|github|discord|linkedin_oidc)" \
--exclude-dir=node_modules --exclude-dir=.git --exclude-dir=dist .google (or another provider) and none for apple is the 4.8 situation. A match for apple only in web code means the iOS build may not have a working Apple sign-in - test it on a device.You can also ask your Supabase project which providers are switched on. This uses the public key that is already in your app and returns only on/off flags (Supabase: checking enabled providers):
curl -s "https://YOUR-PROJECT-REF.supabase.co/auth/v1/settings" \
-H "apikey: YOUR_PUBLIC_KEY"external object: "google": true with "apple": false means Apple sign-in is not enabled on the backend yet. In the dashboard the same switches are under Authentication > Sign In / Providers.2. How do your current users sign in?
Supabase stores each sign-in method of a user as an identity in the auth.identities table, with the provider name in the provider column (Identities, User Management). In the dashboard open SQL Editor and run:
select provider, count(distinct user_id) as users
from auth.identities
group by provider
order by users desc;google row tells you how many people the new option has to work for alongside the old one.And the users who can only get in with a social login - the ones who would be stuck if that login broke:
select u.id, u.email, u.created_at
from auth.users u
where exists (
select 1 from auth.identities i
where i.user_id = u.id and i.provider = 'google'
)
and not exists (
select 1 from auth.identities i
where i.user_id = u.id and i.provider in ('email', 'apple')
)
order by u.created_at desc
limit 50;3. What does the reviewer see on the login screen?
- Install the build you submitted (through TestFlight) on a real iPhone and open the login screen without signing in.
- Check that a Sign in with Apple button is visible without scrolling and is no smaller than the Google button. Apple's Human Interface Guidelines ask for exactly that (Displaying buttons).
- Tap it and finish the sign-in, once sharing your email and once with Hide My Email. Both must end signed in to the app.
- Check that the same option is offered wherever an account can be created, not only on the sign-in screen.
Why it happens
AI app builders and starter templates set up whichever login is quickest on the web, and "Continue with Google" is often one of the defaults - Lovable, for example, sets up email and password, Google and Sign in with Lovable unless you ask for other methods (Lovable: users and authentication). On a website nobody asks for anything else. Once the same app is wrapped for iOS, 4.8 applies to it, and App Review checks the login screen on the first pass.
When Sign in with Apple is added but still fails review, the reasons are usually technical:
- The web OAuth flow is used inside the iOS app's WebView and does not return to the app. Supabase recommends native Sign in with Apple on iOS instead of the OAuth flow (Supabase: Sign in with Apple).
- The iOS App ID has no Sign in with Apple capability, so the native sheet never opens.
- The app's bundle ID is not in the Client IDs list of the Apple provider in Supabase, so Supabase rejects the token Apple issued to the app.
- The web OAuth flow worked for months and then stopped: Apple requires a new secret key every 6 months for the OAuth flow, and an expired one causes authentication failures (Supabase: Sign in with Apple).
How to fix it
Which path you take depends on where the app runs. Wrapped web apps (Capacitor) and Expo apps on iOS should use native Sign in with Apple and pass Apple's token to Supabase. The browser version of the app can keep using the OAuth redirect flow. Lovable Cloud projects have their own settings - see step 5.
Step 1: Apple Developer account
- In Certificates, Identifiers & Profiles, open your app's App ID and enable the Sign in with Apple capability. Supabase says to leave the Server-to-Server notification endpoint blank, because Supabase Auth does not support it (Supabase: Sign in with Apple).
- In Xcode, add the Sign in with Apple capability to the app target under Signing & Capabilities (Adding capabilities). In Expo, set
ios.usesAppleSignIntotruein app.json instead (Expo AppleAuthentication). - Only if the browser version of the app needs Apple sign-in too: create a Services ID with your domain and the return URL
https://YOUR-PROJECT-REF.supabase.co/auth/v1/callback, and a signing key (a.p8file). Keep the.p8file safe - you need it every 6 months to generate a new secret (Configuring your environment). - If your app sends email (receipts, password resets, newsletters), register your sending domain or address as an email source for the Private Email Relay Service and authenticate it with SPF, and DKIM where possible. Apple's relay only delivers mail to Hide My Email addresses from registered sources (Private email relay).
Step 2: Supabase
In the dashboard go to Authentication > Sign In / Providers > Apple and enable it. In Client IDs, add your iOS app's bundle ID (for example com.example.app). If you also use the web flow, put the Services ID first in that list: Supabase uses the first client ID for the web signInWithOAuth flow and accepts any listed ID for native sign-in, and a native App ID in first place makes Apple reject the web sign-in (Supabase: Sign in with Apple). The secret key field is needed only for the web OAuth flow.
.p8 file every 6 months, and sign-in with Apple fails when it expires.Step 3: native sign-in in a Capacitor app
For a web app wrapped with Capacitor, the community plugin @capacitor-community/apple-sign-in opens Apple's native sheet on iOS and returns an identity token. You hand that token to Supabase with signInWithIdToken (reference). Install it with npm i @capacitor-community/apple-sign-in and npx cap update, then:
import { Capacitor } from "@capacitor/core";
import { SignInWithApple } from "@capacitor-community/apple-sign-in";
import { supabase } from "./supabaseClient"; // your existing client
async function sha256Hex(value: string): Promise<string> {
const digest = await crypto.subtle.digest("SHA-256", new TextEncoder().encode(value));
return Array.from(new Uint8Array(digest), (b) => b.toString(16).padStart(2, "0")).join("");
}
export async function signInWithApple(): Promise<void> {
// In the browser, keep the normal redirect flow.
if (Capacitor.getPlatform() !== "ios") {
const { error } = await supabase.auth.signInWithOAuth({
provider: "apple",
options: { redirectTo: window.location.origin },
});
if (error) throw error;
return;
}
// Apple gets the hashed nonce, Supabase gets the raw one and compares the hash.
const rawNonce = crypto.randomUUID();
const { response } = await SignInWithApple.authorize({
clientId: "com.example.app", // your bundle ID
redirectURI: "https://example.com", // required by the plugin's types; the native iOS flow does not use it
scopes: "email name",
nonce: await sha256Hex(rawNonce),
});
const { error } = await supabase.auth.signInWithIdToken({
provider: "apple",
token: response.identityToken,
nonce: rawNonce,
});
if (error) throw error;
// Apple sends the name only the first time a person signs in to your app.
if (response.givenName || response.familyName) {
await supabase.auth.updateUser({
data: {
full_name: [response.givenName, response.familyName].filter(Boolean).join(" "),
given_name: response.givenName,
family_name: response.familyName,
},
});
}
}Why the nonce: supabase-js documents that if the ID token contains a nonce claim, the hash of the value you pass is compared to the value in the token, which stops a token from being replayed. Supabase's Flutter example uses the same pattern - the SHA-256 hash goes to Apple, the raw value goes to Supabase (Supabase: Sign in with Apple). The plugin is a community package, not an official Capacitor or Supabase one; check its version against your Capacitor version before installing.
Step 4: native sign-in in an Expo app
Supabase's guide has a full Expo example with expo-apple-authentication (Supabase: Sign in with Apple). Install it with npx expo install expo-apple-authentication, add "usesAppleSignIn": true under ios in app.json, and only show the button when AppleAuthentication.isAvailableAsync() resolves to true (Expo docs). The core of it:
import * as AppleAuthentication from "expo-apple-authentication";
import { supabase } from "./supabaseClient";
export async function signInWithApple(): Promise<void> {
const credential = await AppleAuthentication.signInAsync({
requestedScopes: [
AppleAuthentication.AppleAuthenticationScope.FULL_NAME,
AppleAuthentication.AppleAuthenticationScope.EMAIL,
],
});
if (!credential.identityToken) throw new Error("No identity token from Apple.");
const { error } = await supabase.auth.signInWithIdToken({
provider: "apple",
token: credential.identityToken,
});
if (error) throw error;
// Save credential.fullName with updateUser here - Apple sends it only on the first sign-in.
}AppleAuthentication.AppleAuthenticationButton for the button itself. When testing in Expo Go, add host.exp.Exponent to Client IDs in Supabase; for development builds, add each bundle ID variant you use.Step 5: Lovable Cloud projects
On Lovable's built-in backend, ask in the project chat to add an Apple sign-in button, or enable Apple under More > Users > Settings > Apple (Lovable: Apple authentication). Two things Lovable's docs say that matter for an iOS app:
- In the default Managed by Lovable mode, Lovable signs people in with its own Apple identifiers, so a token that Apple issues to your iOS app is not accepted. The iOS app has to open Sign in with Apple in the browser and come back through a custom scheme (such as
myapp://callback) added to Redirect URLs. With your own credentials, the Client ID takes one identifier: the Services ID for the browser flow, or the app's bundle ID for native sign-in. - Apple identifies users per developer team. Switching between Managed by Lovable and your own credentials later can mean existing Apple users are not recognized, and their relay addresses change. Decide before you launch.
If your Lovable app is connected to your own Supabase project instead, follow steps 1 to 3. For the browser-and-deep-link route in any wrapped app, Supabase's native mobile deep linking guide covers the redirect setup.
Step 6: put the button where Apple expects it
- Show Sign in with Apple on every screen where Google is offered, at least as large, without scrolling.
- Use the system button (the plugin or Expo component, or Apple's web button) rather than a home-made one. Apple's guidelines describe the allowed styles and titles (Human Interface Guidelines).
- After an Apple sign-in, do not ask for a password, and do not ask for a personal email address when the person chose a relay address. The Human Interface Guidelines say both directly.
Step 7: existing users and accounts
Supabase links identities with the same email address to one user automatically (Identity linking). A person who signed up with Google and later uses Sign in with Apple with the same, shared email ends up in the same account. A person who picks Hide My Email arrives with a relay address, so Supabase creates a new, separate account. If that matters for your app, offer a way to connect accounts from the account settings: Supabase has manual linking with linkIdentity(), which you enable in the project's auth configuration. Apple's guidelines also suggest offering account linking (Human Interface Guidelines).
Step 8: test like a reviewer, then resubmit
- On a TestFlight build on a real iPhone, sign up with Apple using Hide My Email. Check that the user appears in Authentication > Users (or More > Users in Lovable) and that the app works normally.
- Sign out and sign in again with Apple. The second time Apple sends no name, so check the app does not break or ask for one again.
- Rerun the provider query from check 2: an
applerow should now appear. - If the app supports account deletion, delete the Apple test account from inside the app - Apple's account deletion rules apply to Apple sign-in users too (see our 5.1.1(v) guide).
- Upload the new build, say in the Review Notes where Sign in with Apple is and that it was added, and reply on the App Review page before resubmitting (Contact App Review).
When to get help
- The app is a wrapped web app and Apple sign-in opens but never returns to the app, and you cannot tell whether the problem is the WebView, the redirect URL or the Supabase settings.
- Many users already sign in with Google, and you need Apple sign-in, relay addresses and account linking to work without creating duplicate accounts.
- You are not sure whether one of the 4.8 exceptions applies to your app, for example a business app that requires a company account.
- The app also needs account deletion, in-app purchase changes or a demo account, and you want one resubmission instead of several review cycles.
Sources
Primary documentation this guide was checked against. Platforms change - if something here no longer matches, the source wins.
- App Store Review Guidelines (last updated 2026-10-16)Apple Developer
- Sign in with AppleApple Human Interface Guidelines
- Sign in with AppleApple Developer Documentation
- ASAuthorization.ScopeApple Developer Documentation
- Configuring your environment for Sign in with AppleApple Developer Documentation
- Communicating using the private email relay serviceApple Developer Documentation
- Adding capabilities to your appApple Developer Documentation
- Contact App Review for help with a submissionApp Review Help
- Sign in with AppleSupabase docs
- signInWithIdToken()Supabase docs
- IdentitiesSupabase docs
- Identity linkingSupabase docs
- User ManagementSupabase docs
- Native mobile deep linkingSupabase docs
- Add Apple authentication to your appLovable docs
- Users and authenticationLovable docs
- AppleAuthenticationExpo docs
- @capacitor-community/apple-sign-innpm (Capacitor Community)
Frequently asked questions
- Does Guideline 4.8 require Sign in with Apple specifically?
- The current text does not name it. It requires an equivalent login option that limits data collection to name and email, lets people keep their email private, and does not collect app interactions for advertising without consent. Sign in with Apple has those features, which is why it is the usual fix.
- My app has email and password plus Google. Do I still need Sign in with Apple?
- The exemption covers apps that exclusively use their own account system. With Google as one way to create the main account, the app is not exclusive, so it needs an option with the three privacy features. A plain email-and-password form does not let people hide their email address. Removing the Google button is the other way out of 4.8, if your users can live without it.
- What if I only use Google for something other than login, like Google Drive access?
- 4.8 applies to third-party login used to set up or authenticate the user's primary account. Connecting a Google account inside the app to import files, after the person signed in another way, is not that. Expect the reviewer to look at the login and sign-up screens.
- Can I use the web OAuth flow inside my wrapped iOS app?
- Supabase says it is best practice to use native Sign in with Apple on iOS instead of the OAuth flow in web-based native apps. The native flow also avoids the 6-month secret rotation, which applies only to the OAuth flow. On Lovable Cloud in Managed mode, the browser flow with a custom-scheme redirect is the documented route for an iOS app.
- Why is the user's name empty after Sign in with Apple?
- Apple's identity token does not include the name, and Apple sends the name only on the first sign-in. Save it with
supabase.auth.updateUserright after that first sign-in. With the web OAuth flow the name is not available at all, according to Supabase. - Emails to some users bounce after adding Sign in with Apple. Why?
- People who chose Hide My Email have an address at Apple's private relay. Apple only forwards mail from sending domains or addresses you registered for the relay service, authenticated with SPF (and DKIM where possible). Register them in your Apple Developer account.
Related guides
Fixed-price audit
Want someone to check the whole app, not just this?
A review of data security, production readiness and App Store readiness for apps built with AI tools. 900 USD, a ranked list of fixes within 5 business days.