I think at this stage (3 months after https://developer.apple.com/news/?id=09122019b was posted) we have to assume that the Apple did not make a mistake by including 'exclusively' in:"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."The most sensible interpretation I can see is that Apple have deliberately left a 'grey' area in the middle, where apps that make non-exclusive use of third-party/social login may have to implement Sign In with Apple at a future not yet announced date.

I guess this a new app? Can you share the rejection message? Did you appeal the rejection quoting the rule?

I guess this a new app?Can you share the rejection message?Did you appeal the rejection quoting the rule, i.e. that it says the requires is for "Apps that exclusively use a third-party or social login service"?

Thanks jm_ba - they have indeed; it's crystal clear now that if you offer social login you must offer sign in with Apple, and for existing apps this kicks in on 30th April:https://developer.apple.com/news/?id=03042020d