-
-
Notifications
You must be signed in to change notification settings - Fork 4.8k
JSON text did not start with array or object and option to allow fragments not set. #2517
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
Ignore |
I played around with this more and I am able to run a simple hello world cloud function. I get the
when I run any function that returns something. Here is the cloud code I am calling:
|
Turns out I just wrote the Cloud Code wrong. Closing. |
Parse.Cloud.define("test", function(request, response) {
}); here is my cloud code , when i am calling this cloud code from application following error shows error:Error Domain=NSCocoaErrorDomain Code=3840 "JSON text did not start with array or object and option to allow fragments not set." UserInfo={NSDebugDescription=JSON text did not start with array or object and option to allow fragments not set.} |
Problem
I am getting the following response when I try to call [PFCloud callFunctionInBackground:] in my iOS app.
Error Domain=NSCocoaErrorDomain Code=3840 "JSON text did not start with array or object and option to allow fragments not set." UserInfo={NSDebugDescription=JSON text did not start with array or object and option to allow fragments not set.
My configuration in the AppDelegate looks like:
[Parse initializeWithConfiguration:[ParseClientConfiguration configurationWithBlock:^(id<ParseMutableClientConfiguration> configuration) { configuration.applicationId = @"MY0PjsEc4aLZaWWoiYPnb4cju4VoKN7zyR41FPnR"; configuration.server = @"https://myappname.herokuapp.com/parse"; }]];
The interesting thing is Parse.Cloud.beforeSave function works as expected. Only when I am requested data back this issue appears.
Environment Setup
Any help is appreciated
The text was updated successfully, but these errors were encountered: