-
-
Notifications
You must be signed in to change notification settings - Fork 4.8k
Empty authData in user search request #1703
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 think this is a duplicate of #1568 |
yes, exactly. |
@dbezborodov @steven-supersolid is there a timeline for the next release? (sorry, dont know where else to ask) |
I can't imagine it will be too much longer due to the last release date being some time ago - would be really useful to know the release strategy going forward. I highly recommend you fork the repo though. You can then make a pre-2.2.8 branch, build and commit the lib folder, then use your fork/branch as an git npm dependency. This will enable you to apply other fixes as required. |
parse-server is not returning authData field in user search requests. Using v.2.2.7 POST request to _User class:
{"where":{"objectId":"xxxxxxx"},"limit":200,"order":"-createdAt,-createdAt","_method":"GET"}
returns something like:
{"results":[{"objectId":"xxxxxxx","createdAt":"2015-12-03T08:41:50.980Z","updatedAt":"2016-05-03T13:09:06.697Z","username":"xxxxxxxxxxx"}]}
but original parse API also returns authData:
{"results":[{"authData":{"facebook":{"access_token":"<access_token>","expiration_date":"2016-07-02T07:16:46.815Z","id":""}},"createdAt":"2015-12-03T08:41:50.980Z","username":"xxxxxxxxxxx"}]}
Both parse-server and parse API use the same Mongo database.
This issue makes parse-dashboard always showing authData as "undefined".
The text was updated successfully, but these errors were encountered: