iOS

Application Changes Introduced in 2.1 ESD #2

Update and rebuild your application:

1. The Application APIs (in the SUPApplication class) are required for managing applications registrations, connections, and context. Rewrite the initialization code in your application to use the Application APIs. Replace references in your application to the Messaging Client API (SUPMessage class) with the appropriate use of the Application APIs (SUPApplication).

   For information on the SUPApplication interface, search for Application APIs in the Developer Guide for your platform.

2. Callbacks related to application events are now contained in a separate ApplicationCallback interface. Rewrite your application code to use this interface.

   For information on the ApplicationCallback interface, search for Callback and Listener APIs in the Developer Guide for your platform.

3. Replication-based synchronization clients require two data channels, a data channel for data synchronization, and a messaging channel for sending registration and push notifications to the client. Update your port configuration for both channels. See Sybase Control Center for Sybase Unwired Platform > Administer > Unwired Server > Server Properties.
4. In addition to the required libraries provided in previous SDK versions (libMO.a, libclientrt.a, and libSUPObj.a), two new libraries (libsupcore.a, libAfariaSLL.a) are provided and are required for all iOS applications. These libraries also require additional Apple-provided frameworks to be included when building object API applications.

   For information on importing required libraries, see Developer Guide: iOS Object API Applications 2.1 ESD #2 > Development Task Flow for Object API Applications > Creating a Project > Importing Libraries and Code.