-
-
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
Parse.FacebookUtils.isLinked(user) returns false since parse-server 2.2.6 #2342
Comments
Found the problem submitting a PR. |
Wow, that was fast! Thank you :) I suppose I just wait for the next version of parse-server to come out now and try that? |
That's effectively the easiest route |
Too easy. Any idea when that might come out? I don't really know what determines when a new version is released, seems to be every 2 weeks or so based on changelogs though. |
Just wanted to confirm that I was able to upgrade from 2.2.6 to 2.2.17 and Facebook authentication is working again, thanks! :) |
great, thanks for the feedback! |
…masterKey (parse-community#2348) * Makes sure we don't strip auth data or session token from users queried with masterKey (parse-community#2342)) * nit: test title
…masterKey (parse-community#2348) * Makes sure we don't strip auth data or session token from users queried with masterKey (parse-community#2342)) * nit: test title
Description
We are still using parse server 2.2.6 since all upgrade attempts since this point have broken the facebook integration, as seen in #1579 and #1846.
This has reportedly been fixed, but for me
Parse.FacebookUtils.isLinked(user)
still returns false in all versions above 2.2.6 (tried upgrading to 2.2.16 today).I also tried querying to get the user from the server rather than the request as suggested in #1846, but still no luck :(
Steps to reproduce
Expected Results
Parse.FacebookUtils.isLinked(request.user)
returns true like it does in 2.2.6Actual Outcome
Parse.FacebookUtils.isLinked(request.user)
returns false when server is on higher version (for example 2.2.16)Environment Setup
Logs/Trace
The text was updated successfully, but these errors were encountered: