Update your application to use callbacks from SDK version 2.1 ESD #3.
All callback methods are included in the SUPCallbackHandler protocol, and you must implement them in any class that directly implements the protocol without subclassing the default implementation in SUPDefaultCallbackHandler.
If you have created your callback handler as a subclass of SUPDefaultCallbackHandler, as Sybase recommends, you can safely remove the following messaging-based synchronization callbacks, as the SUPDefaultCallbackHandler has empty implementations of all the required methods.
For a complete list of callbacks you can implement in your application, see Developer Guide: iOS Object API Applications > Client Object API Usage > Callback and Listener APIs.
Old method:
- (void)onConnectionStatusChanged:(SUPInt)connectionStatus :(SUPInt)errorCode :(SUPNullableString)errorMessage;
New method:
- (void)onConnectionStatusChanged:(SUPConnectionStatusType)connectionStatus :(int32_t)errorCode :(NSString*)errorMessage;
Old method:
- (void)onRegistrationStatusChanged:(SUPInt)registrationStatus :(SUPInt)errorCode :(SUPNullableString)errorMessage;
New method:
- (void)onRegistrationStatusChanged:(SUPRegistrationStatusType)registrationStatus :(int32_t)errorCode :(NSString*)errorMessage;
Old method:
- (void)onDeviceConditionChanged :(SUPInt)condition;
New method:
- (void)onDeviceConditionChanged :(SUPDeviceConditionType)condition;