You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on May 6, 2024. It is now read-only.
[UPD 13.08.2020]
Apple was rejected the app with sign in via Apple regarding to wrong Guideline 5.1.1 - Legal - Privacy - Data Collection and Storage
Full message from the Apple:
Guideline 5.1.1 - Legal - Privacy - Data Collection and Storage
We noticed that your app requires users to register with personal information that is not directly relevant to your app's core functionality. Specifically, the following fields or actions are required but do not appear to be directly relevant to your app's core functionality:
Your app requires users to input their name and/or email address after using Sign in with Apple.
Next Steps
To resolve this issue, please either remove all required fields that are not relevant to the app or make those fields optional. Information requested during registration must be relevant to the features the app provides.
Additionally, make sure your app does not require two-factor authentication after users use Sign in with Apple. Sign in with Apple is a self-contained, all-in-one login system that should not require additional steps or information from the user.
The text was updated successfully, but these errors were encountered:
illia-derevianko-raccoon
changed the title
New app with 3rd party sign in services can't be uploaded to App Store
App with 3rd party sign in services can't be uploaded(published) to the App Store
Jul 22, 2020
From iOS SDK 13 all apps contained 3rd party login services must include Sign In via Apple
Link to the news
Do you have any plans to implement this feature?
[UPD 13.08.2020]
Apple was rejected the app with sign in via Apple regarding to wrong
Guideline 5.1.1 - Legal - Privacy - Data Collection and Storage
Full message from the Apple:
The text was updated successfully, but these errors were encountered: