Support Topics Documentation Slack YouTube Blog

JSONSerialization

hello, i found an issue in the ProcessResponse class (getResponseResult). The json decoder doesn’t parse some data correctly if its fragmented. Maybe allowing the parse to .allowFragments. This fixes the issue of parsing for example a api response of just bool
This is when using custom cloud functions, it doesn’t parse backendless exceptions as it should

Hello @Adrian_Ispas,

I’ve created an internal ticket BKNDLSS-22507 for this issue and will investigate it as soon as possible.

Regards,
Olha

Hi Team,

This is a pretty big issue for us, so please keep up updated.

Could you please provide your Application Id with Custom Service we can use for tests?

Regards,
Olha

App ID: 08B538C0-0E98-1827-FF98-7DF8AFF96600
Try the “acceptFriendRequest” custom method

Hi Olha,
Just to summarise the issue, the iOS SDK doesn’t handle backendlessexceptions when returned via any custom API service.

You could make a test api service and return an exception, you would see the issue. It works fine on the rest console, just on iOS.

To add to this, when returning an exception, this is what is returned on IOS:

“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.}

Try the “acceptFriendRequest” custom method

Could you also provide the valid request parameter value?

Hi Olha,

You won’t need any parameters as just invoking causes a exception (this exception is expected):
image

As mentioned above, the exception works fine on the rest console, but it returns this error:

“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.}

When returning the exception to an iOS device. SO the problem is the iOS SDK needs to be updated to handle .allowFragments

Could you please check with v 6.0.3?

Seems to work now. Thank you fir the quick fix