-
-
Notifications
You must be signed in to change notification settings - Fork 4.8k
bad json response issue, cant figure out why. #5116
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
For the record this is the server url. |
Your server code don’t make sense and isn’t valid javascript |
So the SaveSearchByDevice code was from the JS docs. |
That’s the GetKeys function that is really not proper Js. And when you say ‘from the JS DOCS’, can you share a link? |
Sorry I didnt find the getKeys on the parses docs. It was the other function, but I found a solutation on that. I am still having issues with the getkeys, how would I send a success back to the app? I am return a string and split it, but I rather return a json object (map) |
Use stackoverflow please for such questions that refer to implementation details. |
I have two functions that this is happening to...
First
I get a bad json response for this.
Here is my call...
I also have this cloud functions as well...
Parse.Cloud.define("SaveSearchByDevice", function(request, response) {
}, { useMasterKey: true });
And my code for this...
Thanks.
The text was updated successfully, but these errors were encountered: