-
-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
Wrongly generate _Session when login by Facebook #852
Comments
This was referenced Mar 5, 2016
Fixed by 857, will be in next release. 👍 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Here is how to reproduce:
localStorage.clear()
)user
column point to PRGzlgxcoE, which is correctParse.User.logOut()
)user
column to an unknown object: L1wysagBDK (which should be PRGzlgxcoE).Bonus step:
Parse.User.logOut()
, I use:localStorage.clear()
, which will also clear the Installation of Parse and the current logged in user.user
column point to another unknown object: C40NzjGJenEvery time I try to sign out or clear local storage, Parse Server will create(modify) a session with invalid user column.
But if I change to api.parse.com endpoint, this does not happen at all, all session is generated with correct user column.
Note that, the
api.parse.com
and my Parse Server point to the same mongo database, with same AppID and MasterKey.I've tested this on Parse Server 2.1.6 and 2.1.2.
The text was updated successfully, but these errors were encountered: