How to verify that Apple logged-in user data is not lost after transfering the app?

Hi @guojianbin,

You wrote:

When we transfer app A to app B, if we transfer the app but don't migrate the user to app B, will the user's previous tokens from app A be invalid?

After an app is transferred there is a 60-day transfer period where both teams may use their client secrets and related token APIs for Sign in with Apple. After this period ends, only the recipient team will have access to the user data and active user sessions—all requests from the other team will be invalid since there is no longer an association with the client.

Next, you wrote:

Is this failure real-time or will there be a buffer period to transfer users?

The transfer period begins immediately once an app transfer is completed.

Then, you wrote:

If it is a live failure, we want to transfer some users during the transferation process to prevent accidents, and then test them. Is there a way to test it?

There is no testing per se. Sign in with Apple and app transfers both occur only on a production environment. However, you may use test Apple ID accounts to validate your migration logic, perform the app transfer, and then transfer the app back to the original team (as needed).

Cheers,

Paris X Pinkney |  WWDR | DTS Engineer

Hi You wrote:

However, you may use test Apple ID accounts to validate your migration logic, perform the app transfer, and then transfer the app back to the original team (as needed).

How do we get this ”test Apple ID accounts“？How do I create this account？

Hi @guojianbin,

You can create new Apple IDs for the purpose of testing your user migration flows at https://appleid.apple.com. They aren't test accounts, but standard Apple ID accounts that you know are used for your own testing purposes.

Cheers,

Paris X Pinkney |  WWDR | DTS Engineer

Do you mean I need to create a new Apple developer account and create a new app for migration testing? But the app migration needs to be a live app. It can't be tested with an app with no content, right? This is too expensive for us

Are you saying that you need to create a developer account and create a new app to test? Or am I getting it wrong?

I still look forward to your reply, please reply to me as soon as possible

Hi @guojianbin,

You wrote:

Do you mean I need to create a new Apple developer account and create a new app for migration testing? But the app migration needs to be a live app. It can't be tested with an app with no content, right? This is too expensive for us

It's much more simple than that. You may choose to create a new Apple ID account for the purpose of testing the user migration flow. You would essentially follow these steps:

1. Create the test account using a new Apple ID.
2. Authenticate the test account with your production app managed by Team A.
3. Transfer the app to Team B (Team A still has 60 days to properly handle existing requests and user sessions).
4. Test your user migration implementation.
5. Transfer the app back to Team A.
6. Perform the final app transfer once content with your user migration strategy.

Cheers,

Paris X Pinkney |  WWDR | DTS Engineer

Hello, at present, I am worried that there may be unknown problems after the transfer, so I want to test this application. This application has many online users, if there is a problem, it will be very troublesome to test with this application. If we test another application, we need to create a new one and launch it, which is also very troublesome for us. Are there any other detailed plans? Please reply as soon as possible.