sign-in-with-apple

To check for missing Sign in with Apple, inspect your iOS project to identify third-party OAuth implementations that omit the corresponding Apple sign-in option. This validates compliance with App Store Guideline 4.8 and surfaces non-compliant cases for remediation.

You need to add Sign in with Apple when your app offers third-party social authentication options like Google, Facebook, or Twitter. Apple's App Store Guideline 4.8 requires a corresponding Sign in with Apple option to be present alongside these third-party providers.

Sign in with Apple detection works by scanning your iOS or macOS project to identify existing third-party OAuth providers. It then validates whether a corresponding Sign in with Apple option is present alongside those providers and notes any omissions for remediation.

Yes, your app will likely face App Store rejection for using Google and Facebook login without Sign in with Apple. Apple Guideline 4.8 mandates that any third-party social login must be accompanied by a Sign in with Apple option to pass the submission review.

Yes, you can use this to audit macOS projects for third-party authentication compliance. The check applies to both iOS and macOS projects that contain social login flows, validating the presence of Sign in with Apple alongside other OAuth providers.

The best way to prevent App Store rejections related to Sign in with Apple is to run a pre-submission compliance check on your iOS project. This identifies missing Sign in with Apple implementations across authentication flows and generates a remediation plan before submission.