Repository navigation
|
How can a team catch Sign in with Apple relay addresses on private.icloud.com rejected by email validation automatically before a build goes to review? |
Replies: 1 comment
|
The quick check. Run this from the project root and read what it prints. grep -rn 'privaterelay\.appleid\.com' . && ! grep -rqn 'private\.icloud\.com' .Read the result honestly. This is a heuristic. A match is something to inspect, not proof of a violation, and an empty result means nothing was found, not that the app is compliant. For CI, run the full guard, which reports this as What the hit means. The account system, email validation, or allowlist accepts only privaterelay.appleid.com. Apple now issues Hide My Email relay addresses on private.icloud.com as well. Sign-ups with the new domain fail silently and the app is rejected under 4.0 or 4.8 for a broken Sign in with Apple flow. The fix. Accept both privaterelay.appleid.com and private.icloud.com everywhere email addresses are validated, allowlisted, or matched, server and client. Recipe source. data/detection-recipes.json This is a maintainer FAQ for app-store-compliance, an open playbook and pre-submission guard for App Store and Google Play review. Run |
The quick check. Run this from the project root and read what it prints.
Read the result honestly. This is a heuristic. A match is something to inspect, not proof of a violation, and an empty result means nothing was found, not that the app is compliant. For CI, run the full guard, which reports this as
APPLE-4.0-SIWA-RELAY-DOMAINwith a coverage line and a proper exit code.What the hit means. The account system, email validation, or allowlist accepts only privaterelay.appleid.com. Apple now issues Hide My Email relay addresses on private.icloud.com as well. Sign-ups with the new domain fail silently and the …