Skip to content

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

Closed
pcg92 opened this issue Apr 5, 2019 · 5 comments
Closed

After log out the current user is not null #145

pcg92 opened this issue Apr 5, 2019 · 5 comments

Comments

@pcg92
Copy link
Contributor

pcg92 commented Apr 5, 2019

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:

Screenshot 2019-04-05 at 13 02 51

@Atteprojects
Copy link

I usually check for objectId if currentUser != null

@phillwiggins
Copy link
Member

Hey, is this still an issue?

I can look into this tonight before creating a new release.

@pcg92
Copy link
Contributor Author

pcg92 commented Apr 25, 2019

Yes we can check for the objectId, but in the other sdks we just need to check for currentUser!=null

@pcg92 pcg92 closed this as completed Apr 25, 2019
@phillwiggins
Copy link
Member

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.

@phillwiggins
Copy link
Member

Fixed in the latest release

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants