-
Notifications
You must be signed in to change notification settings - Fork 963
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
PlayGamesPlatform.IsAuthenticated() Incorrect Immediately After Calling SignOut() #12
Comments
This is actually working as intended, because Sign Out is an asynchronous process -- the method should be called RequestSignOut() rather than SignOut() to make this clear. However, it would be much more intuitive if IsAuthenticated() started to return false immediately after calling SignOut(), so I'm considering this a bug :-) I'll fix soon! Thanks for reporting. |
[internal tracking# 12836546] |
Fixed on 0.8.01 |
MMMhhh... no, PlayGamesPlatform.Instance.SignOut() not work fine to test on local. http://artistic-minds.it/sharingFiles/Screenshot_21.png Control is also done after many seconds (under a Update function), it is not a matter of waiting for the log out. Username is always the default user "Lerpz".
|
I found that if you call IsAuthenticated() right after calling SignOut(), IsAuthenticated will still return true. It seems that calling IsAuthenticated maybe one or more frames after calling SignOut will return the correct result.
This is a convoluted example, but I have an event that fires in response to signing out and code listening for that event might check for authentication - it seems that the function returns an incorrect value.
I can understand if SignOut is an asynchronous function that might fail for some reason, but the interface for it suggests that you are immediately signed out.
The text was updated successfully, but these errors were encountered: