Documentation Issues and Updates for SAP Mobile SDK

Read about updates, corrections, and clarifications to the documentation released with SAP Mobile Platform Mobile SDK.

Issue #Description
SMPONP-14477
Update Operation

A code check has been added to the iOS API. If a previous non-default Create/Update/Delete operation is pending for an object, and submitPending synchronize has not been called, invoking Update on the object now throws an exception.

Workaround: See the iOS version of Update Operation.

SMPONP-14737 (BCP 65287 2014)
Agentry Client Installation Overview

This Installation Guide: Agentry Device Clients topic no longer correctly describes how to install Android, iOS, and other clients.

Workaround: Instead, install iOS clients from the Apple App Store, and install Android and other device clients from the SAP Service Marketplace. See Installing the Agentry Client on Supported Devices.

SMPONP-11248
Object API Application Tutorials not updated for 2.3 SP03
Only the Tutorial: iOS Object API Application Development is updated in the 2.3 SP03 release. The following tutorials have not been updated for SAP Mobile Platform version 2.3 SP03, and contain references to previous versions of SAP Mobile Platform. However the tutorials are still valid for 2.3 SP03:
  • Tutorial: Hybrid App Package Development > Developing a Hybrid App Package
  • Tutorial: Windows Mobile Object API Application Development > Developing a Windows Mobile Device Application > Creating the User Interface for the Windows Mobile Device Application
  • Tutorial: BlackBerry Object API Application Development > Developing a BlackBerry Application > Creating the BlackBerry Project
  • Tutorial: Windows Mobile Object API Application Development > Developing a Windows Mobile Device Application
In addition, the topic: Tutorial: BlackBerry Object API Application Development > Developing a BlackBerry Application > Creating the BlackBerry Project contains a reference to "SUP 2.2" which should be "SUP 2.3".
CR-710608

onHttpCommunicationError returns an unexpected code.

In an environment configured for SiteMinder authentication, the expectation is that onHttpCommunicationError is called back for error condition 302. This condition is not currently fulfilled by the Windows and Windows Mobile platforms; instead, they return 404 errors.

Workaround: None.