Guideline 4.0 - Design

Our app got rejected with below reason

Your app offers Sign in with Apple as a login option but does not follow the design and user experience requirements for Sign in with Apple. Specifically:

  • Your app requires users to provide their name and/or email address after using Sign in with Apple. This information is already provided by the Authentication Services framework.

These requirements provide the consistent experience users expect when using Sign In with Apple to authenticate or login to an account.

We have an option to login to our app with Apple sign in The user must have a valid account with a valid email id, that created from the web and the user must complete all onboarding program

In the app once the user sign-in using Apple login, we will check for the email ID is hidden or not, if it is hidden we cant log in because we must have a valid email id. So we show a modal with " We can't log you in because your email is hidden. Please select "Share My Email" to continue or use the regular email login option"

If user shares an email, then will check for account exists for that email or not,if yes, it will allow to log-in to the app

How can I sort out this problem?

Your use of SignInWithAppleButton is not clear. AuthenticationServices lets you find out whether or not the user is able to sign in on their device. In other words, it tells you whether the app is being used by the valid owner of the device. AuthenticationServices does not necessarily disclose user's e-mail address. So why are you using it?

Guideline 4.0 - Design
 
 
Q