Question from a developer:
In testing logins, I'm seeing the LastLoginTime being returned as the current time, rather than the time of the previous login. Is this a bug?
Question from a developer:
In testing logins, I'm seeing the LastLoginTime being returned as the current time, rather than the time of the previous login. Is this a bug?
I was hoping to use the LastLoginTime to determine whether a user had logged in from somewhere on a different device as follows:
PlayFabClientAPI.LoginWithFacebookInstantGamesId(new LoginWithFacebookInstantGamesIdRequest { CreateAccount = true, InfoRequestParameters = new GetPlayerCombinedInfoRequestParams { GetUserData = true, UserDataKeys = null }, FacebookInstantGamesSignature = signature }, result => { Debug.Log($"LastLoginTime={result.LastLoginTime}"); // Compare to the last login time stored locally.
// If this value is greater we know a user has logged
// in somewhere else so apply the user data to their local data. }, error => { Debug.LogError(error.GenerateErrorReport()); });
Is there another recommended way of doing this?
I believe it is feasible, via caching local data on the client.
You may also refer to Brendan's answer in this thread: How to prevent duplicate login? - Playfab Community. Please feel free to tell us if you have any other questions.
2 People are following this question.