I recently have had to migrate my Parse server from HerokuApp to MongoDB Atlas, and to do so, it is required to update my parse server from 2.2.12 to at least 2.8.4. During the installation I see a lot of warnings and errors, but it does in the end say ‘Build succeeded!’. Click here for a text file containing the full log during the update.
I don’t know if these warnings/errors are the issue or if there was a breaking change after parse server 2.2.12, but now in my front end code (I am using Parse-SDK-iOS-OSX) I am receiving an error whenever I request objects:
JSON text did not start with array or object and option to allow fragments not set.
I have changed the parse server back to 2.2.12, and it works again, then back to 2.8.4 and it doesn’t work, so obviously it is something to do with changes or problems with the parse server, which is why I’m posting now in the parse server topic. (I previously posted this as an iOS issue here: iOS SDK: findObjectsInBackground query returns strange JSON error)
Is anyone aware of breaking changes in parse server that I need to adjust my code for? Or would the issue be related to the errors/warnings in updating parse server, in which case, any advice there?
- I am using the latest Parse-SDK-iOS-OSX (version 1.19.1).
- I have seen that it might be possible to get a more meaningful error message if I add logging to the parse server and set up the Parse dashboard. Unfortunately this potential solution was a dead-end for me also, after installing Parse dashboard, I see:
[Error] Origin http:// localhost:4040 is not allowed by Access-Control-Allow-Origin.
If resolving this Parse dashboard issue would be the easiest way to diagnose my iOS code issue, I have posted about this issue in StackOverflow here: stackoverflow .com/questions/64706303/parse-dashboard-access-control-allow-origin-error. (sorry I had to put the space into the URL so that I could post this topic as new users can only include two links)