-
-
Notifications
You must be signed in to change notification settings - Fork 206
After log out the current user is not null #145
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
Comments
I usually check for objectId if |
Hey, is this still an issue? I can look into this tonight before creating a new release. |
Yes we can check for the objectId, but in the other sdks we just need to check for currentUser!=null |
Hey, I'll look into this tonight. I'd prefer not to have a current user if there is no objectId. I potentially might make a method as well called something like, isUserAvailable that returns a bool or something. |
Fixed in the latest release |
Im doing user.logOut(), and then Im checking if the
currentUser!=null
but it is retuning not null.Here is the current user after log out:
The text was updated successfully, but these errors were encountered: