List of Known Issues for APIs

This topic lists known issues associated with APIs.

Table 1. API issues
CR#	Description
567100	After a synchronization using the client API, `SyncResult.LastPlayback` and `SyncResult.LastGoodPlayback` may not be set. In some cases after a synchronization using the client API, the result returned by client API may not set `SyncResult.LastPlayback` and `SyncResult.LastGoodPlayback`. This happens when both of the following conditions are met. User requests a sync for the first time and there are no rows matching the request in the EIS back-end system. The EIS interaction results in an error. There should not be any data in the cache matching this request, even from previous requests. Workaround: No user action is required; this resets automatically for the next successful sync that returns at least one row of data.
566720	Setting `noPlayback` to 'true' may generate recursive push notifications. If you set `noPlayback = 'true'` when calling the synchronization API, push synchronizations may generate recursive push notifications on Windows and Windows Mobile clients that are generated using Device Application Designer. Workaround: When calling the synchronization API, manually edit the generated client code to set the `noPlayback` setting to `'true'`. Note: This should only be done for synchronization calls done in response to push notifications. Normal synchronization calls can be left to use the default setting, which is `noPlayback = 'false'`.
565417	On Windows .NET clients, an exception is thrown and the device application aborts. When using the Sybase Unwired Platform synchronization APIs for Windows .NET applications, an exception is thrown if the device application name is greater than 100 characters, or if the aggregate synchronization parameters are greater than 384 characters. The exceptions are: Application name cannot exceed 100 characters. Push parameters exceed 384 character limit. Try shortening the application name. Workaround: Do not use more than 100 characters for device application names and do not have aggregate synchronization parameters in the mobile business object that are greater than 384 characters. For generated .NET clients, the default application name is the full path to the running executable. You can change the location of the device application to reduce this size, or you can modify the application name in the generated code.
539062	GetUploadFiles() lists all files in the directory instead of just the source file specified in the file MBO. If the file mobile business object specifies a single file, GetUploadFiles() still returns all files under that folder. Workaround: None.