Same here. 😞
If there are no solutions for resolving this issue other than waiting for Apple to fix it*, is restarting the Simulator sufficient for recovery from the crash? It would be really annoying to have to reboot every time this happens. 😬
* This reminds me to mention that we should all report it via Feedback Assistant so they know it's happening. 😉
InteractiveLogic
Users receive reputation points by contributing quality content to the forums.
Posts include post and replies published on the forums.
Post authors can mark replies as Accepted to indicate successful solutions.
Apple Developer Forums admins can mark replies as Apple Recommended to indicate an approved solution
Last seen
User for
Post
Replies
Boosts
Views
Activity
Yeah according to the App Transfer Criteria in the App Store Help here, "Apps using Sign in with Apple cannot be transferred."What is really unfortunate about that requirement is that there are a ton of apps that will need Sign in with Apple starting June 30, and once converted, they can't be transferred as-is.The right solution is not clear to me how someone would transfer an app after implementing SIWA.Perhaps you would need to create your own authentication system, and then the SIWA rule wouldn't apply to you. Not super practical, but it's one way around it.
No it's not necessary in your situation. According to the App Store Guidelines, "Sign in with Apple is not required if your app exclusively uses your company’s own account setup and sign-in systems."https://developer.apple.com/app-store/review/guidelines/#sign-in-with-appleHowever, if your app uses something like Facebook or Google authentication in addition to your own authentication system, then yes, you'll need to add Sign in with Apple.