-
-
Notifications
You must be signed in to change notification settings - Fork 4.8k
Difference in Json object returned by Parse Server #803
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
It seems to be a pretty serious issue, Can you post the query you're running? |
Here is the curl request: curl -X GET -H "X-Parse-Application-Id: " http://52.86.109.86:xxx/parse/classes/TestClass API key parameter is not included in the curl request as it is optional for the migrated server. This command returns all the objects under TestClass but with an additional root node (as mentioned in the original question above). The same request made to Parse.com returns the JSON data as expected. Thanks. |
I'm also curious why the query response is different on Parse Server. Previously if I console logged a query response I would get a plain json object. Now if I run the same function the console logs an array of ParseObjectSubclass objects that don't appear to contain anything useful. I can see the correct "results" array in the network response tab, but not sure how to access it? |
I was using the DB Migration tool to transfer records from Parse.com to the new server. Tried again by first taking the back-up of the database in JSON format and then imported it in to the new server. This fixed the issue. |
I have migrated a Parse app to AWS by following the migration guide. Server is running fine and data is accessible however my application is not able to process the json response returned by server.
Initially, on Parse.com, the json response returned by server starts as the following:
But now, the response received from the migrated Parse server starts as following:
_Notice the additional "results": [ and objectIdat the root. _
I could update my app to deal with it but it will be great if this can be fixed from the server end so that I don't need to make changes in my app.
Any help will be appreciated.
Thanks
The text was updated successfully, but these errors were encountered: