I submitted 2 apps for review in the same day with the exact same authentication methods and only one of them got rejected. So it's neither required to implement the Sign in with Apple nor exempt from implementing it.Ĥ.
My app does NOT EXCLUSIVELY use third-party login services and does NOT EXCLUSIVELY use our own method. The first 2 rules don't cover my app's case. Your app exclusively uses your company’s own account setup and sign-in systems.ģ. So I feel like this rule does not apply to my app.
In fact the email and password method is on top and thus assumed to be the main method of authentication. It also uses our own email/ password method. Here are a few interesting things that I found while reading the App Store Review Guidelines.Īpps that exclusively use a third-party or social login service (such as Facebook Login, Google Sign-In, Sign in with Twitter, Sign In with LinkedIn, Login with Amazon, or WeChat Login) to set up or authenticate the user’s primary account with the app must also offer Sign in with Apple as an equivalent option.īut my app does NOT EXCLUSIVELY use a third-part or social login service. My app offers regular email and password authentication as well as Facebook and Google login. So my app just got rejected for the exact same reason. Therefore I'll be updating my apps to support Sign in with Apple and I recommend you do the same if you fall into this category. Those apps are now required to offer Sign in with Apple. The App Store Review Guidelines have been updated to cover cases that use both third party and their own sign in services.
0 kommentar(er)
