User logs into the game with anonymous account on device A
Makes some progress on device A
User logs with platform specific provider (i.e Apple sign in) and links the account.
User logs into the game with anonymous account on device B
Makes some progress on device B
User logs with platform specific provider (i.e Apple Sign In) and tries to link the account.
Game displays both players progress and user can pick with what account they want to continue
Based on the API LinkWithAppleAsync method will return exception AuthenticationErrorCodes.AccountAlreadyLinked
Will LinkWithAppleAsync also returns the other credentials to fetch data from cloud save?
Currently I also can’t see Unlink method. Will it be possible to unlink the platform specific authentication, so you can connect it with new account?
What would be the best way to achieve such flow?
Not necessarily. In the end, I just want to have the possibility to sign in on both iPhone or IPad with selected PlayerID to fetch correct data from Cloud Save.
There are two ways to handle it.
The SignIn will return error CredentialsAlreadyInUse and also credentials already associated with that PlayerID. With that information you user can select right PlayerID. If user selects the account associated with other device (iPhone) We can just reload reload the game and sign in again with selected PlayerID. If user decides to use iPad account and still link with Apple ID then they would need to manually unlink Apple ID from iPhone device.
That’s the use case you mentioned - we transfer PlayerID to other Apple ID
Thank you - this is super clear! We don’t have a way to support this at the moment, but this is something we do plan to support before GA. We have it tentatively slated for Q1, but I will plan to follow up on this post in the next month or so to confirm the plan.
Hi Aixa- wanted to follow up here. Our latest version, Authentication 1.0.0-pre.37 now supports Account Unlinking along with the following features:
Session Token Management
Profiles support
User Info
Account Deletion
We will be publishing our updated documentation this week which will provide more info on these capabilities. Thank you again for providing feedback! As for the second use case, that is something we are still planning to address in Q1.