Hi, I ultimately ended up implementing some handling of the transfer_sub on the auth server, and performed the App transfer. All is good in that prospect, yet I am having issues with generating the new team-scoped identifiers.
Since I ran into this thread (https://developer.apple.com/forums/thread/762829) I have opened a report via FeedbackAssistant with ID FB15415304. Would you please have a look at it @DTS Engineer ?
Post
Replies
Boosts
Views
Activity
Later, about the testing you said
[quote='806268022, DTS Engineer, /thread/764888?answerId=806268022#806268022']
There is no test, debug or sandbox environment for Sign in with Apple, or app transfers. You can create a new Apple ID account and use that for testing purposes, however, you'd still have to perform the app transfer. As soon as the transfer is complete, the 60-day transfer period begins, where both teams' tokens, keys and secrets are valid. You can then transfer the app from Team B back to Team A once you've completed your tests and are content with your implementation of the user migration process.
[/quote]
I do not see any benefits here, as with the transfer I'm exposing my app to user login issues, so doing it twice could only make it worse, or am I missing something?
Would it be possible to "clone" my app and transfer a clone of it instead of the version installed by the users of the store so it does not affect them? Or maybe creating a brand new app, just for testing purposes?
I see the App Store requirements are quite strict, and a "test" app of course wouldn't pass those (even if just with restricted access to a few selected test users)
Hi, and thanks for the prompt reply.
[quote='806268022, DTS Engineer, /thread/764888?answerId=806268022#806268022']
I'd recommend looking at the following technote, which may help understand the expected flows:
TN3159: Migrating Sign in with Apple users for an app transfer https://developer.apple.com/documentation/technotes/tn3159-migrating-sign-in-with-apple-users-for-an-app-transfer
[/quote]
As you can see in my original post, I have already had a look at the technote you have linked here, and unfortunately things are not that clear. Since you confirmed some info, I'll try narrowing down the scope of my doubts, hopefully you can tell me if that is a correct way of handling this or not.
Let's say I have a table in my database where I store a relation between the sub (which I get from the Apple Token), and our userId. My plan is the following:
TEAM A: Generate transferId for each sub I have saved in my database
TEAM A: Start App Transfer
TEAM B: Accept App Transfer
TEAM B: Generate team B sub identifiers with the migrationinfo endpoint
Store the new team B sub as related to the same user that the team A sub was related to (we can find this because they have the same transferId)
If all that is done, after the transfer I will open new tokens finding team b sub inside, and with that I can get the same user that the same AppleId was putting inside the sub when the app was assigned to team A.
Is this correct?
In step 5 I might also change the email address if they use a private relay. Should I keep the old email for any reason? Maybe for a rollback?
Later, about the testing you said
[quote='806268022, DTS Engineer, /thread/764888?answerId=806268022#806268022']
There is no test, debug or sandbox environment for Sign in with Apple, or app transfers. You can create a new Apple ID account and use that for testing purposes, however, you'd still have to perform the app transfer. As soon as the transfer is complete, the 60-day transfer period begins, where both teams' tokens, keys and secrets are valid. You can then transfer the app from Team B back to Team A once you've completed your tests and are content with your implementation of the user migration process.
[/quote]
I do not see any benefits here, as with the transfer I'm exposing my app to user login issues, so doing it twice could only make it worse, or am I missing something?
Hi, I'm also interested in knowing more about this, as I am about to perform an app transfer with user migration, and I have seen multiple forum posts in the last few weeks talking about this kind of behaviour.
Should I expect a high volume of errors @DTS Engineer ?
Also, @chris_avellis did you manage to have a successful transition after that September 22nd deadline?