Hi,
Is it safe to use client API methods to do a background process for a second user without affecting the main "foreground" user (current logged in one)?
Here is the use case:
I'm saving the different account link status (Facebook, Google, Android DeviceID) in PlayerPrefs. If we detect that DeviceID is linked we connect using it. Otherwise, user must login using another option, once done we try to link DeviceID.
However, if a cache/data is wiped or app is uninstalled and then re installed we may encounter this situation:
1. DeviceA is linked to User1
2. User2 login using a method other than DeviceID, client tries to link DeviceID to account of User2
3. DeviceAlreadyClaimedError ==> backrgound process
4. Background Process:
- connect using DeviceID (User1)
- UnlinkDeviceID (User1)
5. LinkDeviceID (User2)
My question is: can I use SDK methods for background process or should I call HTTP requests using my own code to not risk affecting actual user (here User2)?
I'm under the assumption that some data about logged in user are saved and used internally, like session ticket, CloudScript URL...