FAULT = '0' on synchronous save

General
1

Trying to do a blocking save:


        id<IDataStore> dataStore = [backendless.data of:[Shorti class]];
        @try{
            Shorti *savedShorti = [dataStore save:_shorti];
        } @catch(Fault *fault){
            NSLog(@"fault submitting shorti: %@", fault);
            return;
        }

I get the following response:

fault submitting shorti: FAULT = ‘0’ [com.backendless.IDataStore.find(Lcom/backendless/persistence/BackendlessDataQuery;)Lcom/backendless/BackendlessCollection;] <com.backendless.IDataStore.find(Lcom/backendless/persistence/BackendlessDataQuery;)Lcom/backendless/BackendlessCollection;>

2

What does the Shorti class look like?

3

attached is relevant header files. Thanks!

shorti headers.zip (3.57kB)

4

Thanks. I assigned it to a developer to investigate. The internal ticket number is BKNDLSS-15097

5

Hello, Allen

Unfortunately I can’t reproduce this problem. Could you please share your Application Id and a simple project with shorti saving method so we could check this? What version of iOS SDK do you use?

Regards, Olga

6

I just downloaded the auto generated iOS project from the console and tried a simple save with the Shorti class and get: FAULT = ‘0’ [java.lang.NullPointerException] <java.lang.NullPointerException>

I’m on 4.0b13

App Id: B040C647-FCD4-EF36-FFB4-E78E82488300

I tried all the other custom classes I’m using and they all work doing a simple save test, but Shorti does not.

Attached is the test project.

Shorti_DEV.zip (16.6MB)

7

Hello Allen,

We’ll check this issue and answer you as soon as possible.

Regards, Olga

8

Hello Allen,

the problem cause from your business logic, if you turn off handler, everything will be ok. try to debug your business logic.

9

Hey Sergey,

There shouldn’t be any business logic at all in the 4.x version… I just checked via the console and there’s nothing there (I definitely didn’t upload anything). There should be business logic in the 3.x version, but the issue I have is specifically for 4.x.

  • Allen
10

Hold up, was looking in the wrong place. Sorry about that, the new UI threw me for a loop. I see the event handlers now. Looks like they were imported in from the migration without me realizing it. I can push on now!

Thanks!