You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
request.user in the correct way, if it is null that could indicate that there is no user logged in to your app. Could you check that you have a logged in user, and if you still have issues, respond with some detailed reproduction steps?
Can you capture the request being made to the server? One way is to run the server with an environment variable set, VERBOSE=1 In this case it sounds like the session token may not be present.
@gfosco I found the problem. In _User collection a field _session_token is present and if you fetch the user data form server, this field override the sessionToken saved in your browser.
If you don't fetch the user, all request to server contain the right sessionToken and if you fetch the user data from the server, all next requests will contain the bad sessionToken come form the _session_token in user data fetched.
Activity
drew-gross commentedon Feb 5, 2016
request.userin the correct way, if it is null that could indicate that there is no user logged in to your app. Could you check that you have a logged in user, and if you still have issues, respond with some detailed reproduction steps?flessard commentedon Feb 5, 2016
Yes i have user logged.
I just call a cloud function from my web app using javascript SDK js1.6.14.
gfosco commentedon Feb 6, 2016
Can you capture the request being made to the server? One way is to run the server with an environment variable set,
VERBOSE=1In this case it sounds like the session token may not be present.flessard commentedon Feb 6, 2016
Voilà !
and this my Request payload in Goole Chrome
flessard commentedon Feb 7, 2016
@gfosco I found the problem. In _User collection a field _session_token is present and if you fetch the user data form server, this field override the sessionToken saved in your browser.
If you don't fetch the user, all request to server contain the right sessionToken and if you fetch the user data from the server, all next requests will contain the bad sessionToken come form the _session_token in user data fetched.
flessard commentedon Feb 9, 2016
Any follow up for this bug ?
thibauddavid commentedon Feb 10, 2016
+1, parse-server is not really usable in most cases without request.user returning client's user
flessard commentedon Feb 11, 2016
@gfosco. Bug still present in 2.0.8...
flessard commentedon Feb 16, 2016
fix whit #373