Hello
Our app does not allow users to register from within the app. They must register elsewhere (on our website) and can then use the app after the fact. We use Facebook login, which would require us to implement Sign In With Apple, but this leaves us in an odd situation that we don't know how to solve as we're not sure of the rules.
Currently, if you log in with a Facebook account that has no ties to an account, you will not be allowed to proceed and you must use your Facebook account when you sign up on our website. Or if you already have an account, you must go to our website, log in and then connect your Facebook account. Our plan is to implement a similar logic for Sign In With Apple, but *something* tells me this would not be acceptable to App reviewers.
There is no good solution for this. For a strict "Apple login must work" workaround we can let users sign in with Apple and access a user account that has no content and serves no purpose. Our app is not meaningful in this way and it will lead to confusion: Our system is a SaaS which makes it impossible to onboard users inside the app, as the app cannot be used unless you've already been granted access to the SaaS platform by an administrator.
Would it be acceptable to reject a Sign in With Apple request if no user account exists? Remember that this is equivalent(*) to how Facebook is implemented, which is what the app review guidelines indicate as the requirement . Could we ask testers to provide an Apple user ID that we can connect to a user in our database for the login-flow to work correctly?
(*)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.
