Our app (app1) was recently transferred from Team A to Team B.
While reviewing the Apple login implementation, we discovered that "Sign in with Apple" had been incorrectly set up to use the Service ID and App ID of another app (app2) — specifically, it was using app2.service as the Service ID and app2 as the App ID.
In other words, app1’s users were authenticated through app2’s credentials due to a misconfiguration on our part.
Now that app1 has been transferred to Team B, we’re trying to preserve those users. However, app2 is still in Team A, and we cannot maintain Team A anymore — meaning app2 must also be transferred to Team B if we want to retain access to the user data.
One idea we considered is submitting app2 for App Review (even though it's non-functional) just to fulfill the transfer requirements, and then transferring it to Team B solely to retain the Apple login setup.
Is this approach acceptable? Are there any recommended ways to handle this kind of misconfiguration while preserving existing Sign in with Apple users?
Hi @JarryK,
Although you are now beyond the 60-day transfer period for Sign in with Apple user migrations, you should submit a report via Feedback Assistant so the App Store and iCloud engineering teams can assist with correcting this issue.
To learn more about the information needed in your report, as well as further guidance on user migrations, please see the following post:
Gathering required information for troubleshooting Sign in with Apple user migration
https://developer.apple.com/forums/thread/762829
Once you've submitted your report (by following the steps outlined in the post above), please respond here with the Feedback ID so we can resolve this issue with both developer team accounts.
Cheers,
Paris X Pinkney | WWDR | DTS Engineer
