In my app I use Google Sign In and Game Center Sign In. My app rejected due to Guideline 4.8 - Design - Sign in with Apple. I already have Game Center sign in so do i still have to implement Apple Sign In? I asked to apple team about it they didn't give a proper answer.
Yes, it is mandatory to implement Apple Sign-In because you have implemented a social sign-in (Google).
The only scenarios when you are allowed to skip Apple Sign-In, while providing a social sign-in are mentioned under guideline 4.8 (link for reference).
Game-Center sign-in is not equivalent to Apple Sign-In and cannot take its place.
Apple just rejected my app due to I don't offer Sign in with Apple in my app as my app allow login with Google and Linkedin, and these(sign in with Google and Linkedin) are configurable like if some user don't want this it'll be disable by Admin.
So Can I go with another try to remove this option for that user which we give to Apple for Review and also tell them its configurable and not mandatory. So will Apple accept my app ?
Thanks
Personally I do not recommend using different configurations only for the App Store review process, because you can get rejected from App Store completely for cheating on the process. Read more at:
https://developer.apple.com/app-store/review/guidelines/#introduction
If you attempt to cheat the system (for example, by trying to trick
the review process, steal user data, copy another developer’s work,
manipulate ratings or App Store discovery) your apps will be removed
from the store and you will be expelled from the Apple Developer
Program.
About Apple Sign, here is Apple guidelines regarding this feature:
4.8 Sign in with Apple
Apps 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. A user’s primary account
is the account they establish with your app for the purposes of
identifying themselves, signing in, and accessing your features and
associated services.
Sign in with Apple is not required if:
Your app exclusively uses your company’s own account setup and
sign-in systems.
Your app is an education, enterprise, or business
app that requires the user to sign in with an existing education or
enterprise account.
Your app uses a government or industry-backed
citizen identification system or electronic ID to authenticate users.
Your app is a client for a specific third-party service and users are
required to sign in to their mail, social media, or other third-party
account directly to access their content.
Read more:
https://developer.apple.com/app-store/review/guidelines/#sign-in-with-apple
Apple Review team rejected the Application with the reason
"We noticed that your app uses a third-party login service but does not offer Sign in with Apple.
"
Even Application have normal Signup process as well with Email and Password.
Is it Mandatory to have Apple Signin in iOS 13 apps ?
Update 3 (March 04, 2020)
The App Store Review Guidelines have been updated to cover cases that use both third party and their own sign in services. Those apps are now required to offer Sign in with Apple. 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.
Original Answer:
So my app just got rejected for the exact same reason. My app offers regular email and password authentication as well as Facebook and Google login. Here are a few interesting things that I found while reading the App Store Review Guidelines.
1. It says:
Apps 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.
But my app does NOT EXCLUSIVELY use a third-part or social login service. It also uses our own email/ password method. In fact the email and password method is on top and thus assumed to be the main method of authentication. So I feel like this rule does not apply to my app.
2. It also says:
Sign in with Apple is not required if:
Your app exclusively uses your company’s own account setup and sign-in systems...
3. The first 2 rules don't cover my app's case.
My app does NOT EXCLUSIVELY use third-party login services and does NOT EXCLUSIVELY use our own method. It uses both. So it's neither required to implement the Sign in with Apple nor exempt from implementing it.
4. I submitted 2 apps for review in the same day with the exact same authentication methods and only one of them got rejected.
Yesterday I submitted 2 apps for review that are part of the same project and have the exact same authentication methods with the exact same auth screen design. They both got in review at the same time. The first one got approved and the second one got rejected for not implementing Sign in with Apple. Funny, right?
So unless they update the Review Guidelines to cover a case where you use both methods of authentication I believe we are not violating any rule. I'm trying to argue with the review team that my rejected app does not violate the App Store Review Guidelines and they should not have rejected it.
I'll update my answer when this get's resolved but till then it might actually help if others who face the same issue point this out to the review team. We'll either win our case and get our apps approved or they'll update their Review Guidelines to cover our case. Either way it'll be helpful for others in the future.
Update 1
Apple kinda understood that this is not right and my app's status changed from Binary Rejected to In Review. Now I'm waiting to see what they decide.
Update 2
After about 40 hours of being "In Review" my app finally got approved and is now "Ready for Sale". I can't believe it, but it finally feels like someone listened and understood the arguments that I made.
If you use any third-party sign-in feature, e.g. Facebook, Twitter, Google etc, you must now provide Apple Sign In as an additional option.
It's important to remember if you use solely a custom login system (i.e. email and password) then you do not need to include Apple Sign In.
4.8 Sign in with Apple
Apps 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. A user’s primary account is the account they establish with your app for the purposes of identifying themselves, signing in, and accessing your features and associated services.
Sign in with Apple is not required if:
Your app exclusively uses your company’s own account setup and sign-in systems.
Your app is an education, enterprise, or business app that requires the user to sign in with an existing education or enterprise account.
Your app uses a government or industry-backed citizen identification system or electronic ID to authenticate users.
Your app is a client for a specific third-party service and users are required to sign in to their mail, social media, or other third-party account directly to access their content.
Further reading can be found here: https://developer.apple.com/app-store/review/guidelines/
Bad news: the word "exclusively" has been removed from the guidelines early March.
Apps that 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
Basically, yes. New apps that use sign-in must provide sign-in with Apple as an option. Existing apps that use sign-in must provide sign-in with Apple by April 2020.
We’ve updated the App Store Review Guidelines to provide criteria for
when apps are required to use Sign in with Apple. Starting today [Sept
12, 2019], new apps submitted to the App Store must follow these
guidelines.
(Source: https://developer.apple.com/news/?id=09122019b)
App Store Review Guidelines
4.8 Sign in with Apple
Apps 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. A user’s primary account
is the account they establish with your app for the purposes of
identifying themselves, signing in, and accessing your features and
associated services.
Sign in with Apple is not required if:
· Your app exclusively uses your company’s own account setup and
sign-in systems.
· Your app is an education, enterprise, or business app that requires
the user to sign in with an existing education or enterprise account.
· Your app uses a government or industry-backed citizen identification
system or electronic ID to authenticate users.
· Your app is a client for a specific third-party service and users
are required to sign in to their mail, social media, or other
third-party account directly to access their content.
(Source: https://developer.apple.com/app-store/review/guidelines)
Today morning my app also got rejected because of the same reason but I was not using any third party sign up.
After rejection, I realised that in side menu under login button, I have 5 social media buttons for their respective social media page links so I replied to Resolution Center that I am using regular email based register and login. Also, I shared the screenshot of both screens (Login & Register). After 7-8 hours the status changed to 'In Review' and after next 10 minutes Apple approved and it goes live.
Apple have changed their store guidelines to include Sign-In For Apple:
Apps 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.
If my app uses Azure ActiveDirectory B2C and allows social logins via this service (e.g. Facebook, Google) then am I required to support Sign-In For Apple? I know this is possible (see Use Azure Active Directory B2C to enable ‘Sign in with Apple’ in your apps but I don't know if my app will be blocked from releasing until I do.
The user can just create an account on AD B2C. Apple also say:
Sign in with Apple is not required if:
Your app exclusively uses your company’s own account setup and sign-in systems.
But does this include a sign-in system that supports third-party social logins?
From https://techcommunity.microsoft.com/t5/Azure-Active-Directory-Identity/Azure-AD-Mailbag-Use-Azure-Active-Directory-B2C-to-enable-Sign/ba-p/566489
Using Sign in with Apple will be soon be required for all apps in the
Apple App Store which support third-party sign-in. This is indicated
at the very bottom of Apple’s recent update to its App Store review
guidelines. This requirement will be enforced once the service is out
of beta and commercially available.
This new policy means that if you implement any third-party or social
login (like Facebook, LinkedIn, or Twitter) in your iOS or Mac apps,
those apps will also need to include Sign in with Apple as an option.
By using Azure AD B2C to enable social login in your applications, you
can be ready for this requirement when it becomes mandatory later this
year.
I have integrated the code required for Apple Pay in my app based on the documentation available with Apple.
However, as a beginner, I have a doubt.
We have not used any third party payment processors like PayPal, Stripe etc.
Is it mandatory to use a third party processors? Can we just use the code and passbook/wallet and do the transactions?
Note: Merchant IDs, Payment certificates are created in the developer account.
Based on Apple documentation a payment provider is recommended but not mandatory.
Using one of these SDKs or hosted solutions is highly recommended
About develop your own payment process...
The alternative is to provide your own server-side solution to receive
payments from your app or website, decrypt payment tokens and
interface with the payment provider to process the authorization.
Handling credit and debit card payments can be complicated and unless
you already have the expertise and systems in place, an Apple Pay SDK
or JS API from a payment provider is the quickest and most reliable
way to support Apple Pay in your app or website.
In my opinion, It's better use a payment provider than develop your own. You're working with money, credit cards numbers...