getSynchronizationParameters issues in SUP 2.1.3

Question

Hi community members, I am developing an iOS application using SUP 2.1.3 version which implements RBS message synchronization. I am able to register device on SUP server and also able to synchronize the database successfully. The Following code i am using to set synchronization parameters of MBO of respective classes to get information for list of different items.

ItemNameSynchronizationParameters *  syncParamFirst = [ItemName getSynchronizationParameters];
[syncParamFirst setSYNC_NO:@"101"];
[syncParamFirst save];

ItemDescriptionSynchronizationParameters *syncParamSecond = [ItemDescription getSynchronizationParameters] ;
[syncParamSecond setSYNC_NO:@"101"];
[syncParamSecond save];

After setting above synchronization parameters when i tried to synchronize the database, the application flow is working fine and it is giving appropriate results for all list of items. But according to the expectation of an application, I also want to set the following synchronization parameters of the respective MBO class.

ItemUsesSynchronizationParameters *syncParamThird = [ItemUses getSynchronizationParameters];
[syncParamThird setSYNC_NO:@"101"];
[syncParamThird save];

After setting 3 synchronization parameters of MBO classes, when i tried to synchronize the app, it works fine for the first item, but when i am calling the same code to get information for the another item, it encounters following error

*** -[CFString retain]: message sent to deallocated instance 0x657c490

The problem is getting into the getSynchronizationParameters method of MBO class. Does SUP 2.1.3 provides any limitations over setting synchronization parameters of more than one or two MBO classes. I have tried patch 01 and 02 with SUP 2.1.3, but the error * -[CFString retain]: message sent to deallocated instance 0x657c490 is still present.

Any kind of help and suggestions are always welcome.

Answer 1

did it fail always when you use the setter of ItemUsesSynchronizationParameters ? For me it looks like a bad setter in the generated code. But i don't have any experience in the SUP Code generation.

I use up to 15 Syncgroups in my SUP Peojects