Same here. No way at the moment to test all the different flows that we would expect from the Apple Sign In feature. Hope that Apple does not expect us to create an Apple account for every test we need to perform in order to make sure that the app works as intended. This makes testing really difficult, on top of which, Apple has strong-armed us into adding this feature. They rejected our app for this reason, that we provided other social authentication options, like Google and Facebook, and did not include Apple Sing In. At that point we had 2 options, to disable social auth all together, leaving thousands of users with no means to authenticate, or offer Apple Sign In within the app. Obviously, we did not go for the first one, so Apple Sing in it was. I was supposed to start my holiday 3 days ago, instead I started building this new feature in place. Yet this is where I am at. A nobody, in the middle of the Apple desert. Very poor experience Apple. Really disappointed. This would not be a huge issue, if we did not have critical issues being addressed in our latest release off the app, which got rejected by the App Store team on the basis of Apple Sign In. I have asked them to approve this release, hence the critical issues being addressed within it, with the promise to include the Apple Sign in feature in the next. And they wouldn't have it. These things take at least 1 week to plan around, if you want to make sure you check all the security checkboxes. Just a huge disappointment. And now this, no way to reset/revoke access, to be able to use the same account through all the possible journeys that a user could take while using the Apple Sing in feature.