关于Sign-in with Apple禁用“Hide My Email”选项的技术问询

Hey there, this is a super common pain point for apps that rely on direct, critical email communication with users—let’s break this down clearly.

First off, the straight answer: you cannot disable the "Hide My Email" option when using Sign-in with Apple. This is a core privacy feature baked into Apple’s framework, designed to give users full control over their personal information. Forcing users to share their real email would violate Apple’s App Store Review Guidelines (specifically around user privacy and choice), which could lead to your app being rejected or pulled from the store.

That said, there are practical workarounds to ensure you can still communicate with users effectively while respecting Apple’s rules:

• Set clear expectations upfront
  Before users start the Apple Sign-in flow, explicitly explain why you need their real email (e.g., "We’ll send order confirmations, security alerts, and time-sensitive account updates to this address"). Add this context right next to your Apple Sign-in button or in a short pre-login prompt. Users are far more likely to choose to share their real email when they understand the direct benefit to them.

• Prompt for a real email post-login
  If a user still opts for the hidden relay email, don’t block their access to your app. Instead, after they’ve successfully logged in, show a friendly, non-intrusive request asking them to provide their real email. Frame it around the value they’ll get (e.g., "Never miss important account updates—add your email here to stay in the loop"). Include a quick verification step (like sending a confirmation code) to ensure the address is valid.

• Leverage Apple’s relay email as a backup
  When users select "Hide My Email," Apple provides a unique private relay address (formatted like random-string@privaterelay.appleid.com) that forwards messages to their real inbox. You can send emails to this address, and users will receive them just like any other message. Keep in mind, users can disable this forwarding at any time via their Apple ID settings, so this should be a fallback rather than your primary communication method.

• Double-check your Sign-in with Apple configuration
  Make sure you’re properly requesting the email scope in your authorization request. Without this scope, you won’t even have access to either the real email or the relay address. For example, in JavaScript (Firebase example), you’d include:

  const provider = new firebase.auth.OAuthProvider('apple.com');
  provider.addScope('email');
  provider.addScope('name');
  

  (Syntax varies by platform, but the key is explicitly including the email scope.)

Remember, Apple’s top priority is user privacy, so any solution you implement must respect the user’s choice. Never restrict app functionality or deny access because a user chooses to hide their email—this will almost certainly result in an App Review rejection.

内容的提问来源于stack exchange，提问作者Pradip