Known Issues for SAP Mobile WorkSpace – Hybrid App Package Development

Directory paths that contain "MobileSDK22" should be "MobileSDK23".

By default, SAP Mobile SDK installer configures the system to use the 32-bit packaging tool. If you try to run the 64-bit packaging tool (PackagingTool64.bat) after completing a new or upgrade installation of SAP Mobile SDK on a 64-bit Windows system, launching the tool fails with this message:

Cannot load 64-bit SWT libraries on 32-bit JVM

Null values are not supported for the Windows Mobile platform. For example, the Allows null property in Designer has no effect on a Hybrid Apps running on Windows Mobile devices.

Workaround: None.

On some HTC versions running Android 2.3, selecting editable text in some Hybrid Apps does not display the keyboard.

Workaround: None.

On iOS 5.0, with the Safari mobile browser, in fields with the int type, when you enter a number larger than 1000, a comma is inserted. This is expected behavior with the Safari mobile browser.

Workaround: Set the logical-type to text instead of numeric.

The anchor can be moved on a slider that is designed to be read-only. This is a known BlackBerry problem.

Workaround: None.

On BlackBerry 7 devices, in a form that uses labels on the left, if the first field is editable, the second label does not initially use the theme set in the form.

Workaround: Type in the field to change the label to the appropriate theme.

In a BlackBerry 7 or later device, if you invoke the DatePicker control in a Hybrid App by clicking in a date field, click Cancel in the DatePicker, and then click again in the same field, the DatePicker control does not reopen.

Workaround: After clicking Cancel in the DatePicker, click in another field that is not of type DATETIME or TIME. You can then click in the original date field to open the DatePicker.

If you migrated a Hybrid App project that previously contained a submit Hybrid App action, setting its error screen property does not generate the AsyncRequestErrorLogs list key.

Workaround: Create a new Submit Hybrid App action, or click the Generate Error Screen button.

This might happen if the workflow is not constructed correctly.

On a Listview details screen, you cannot invoke a submit workflow to invoke an MBO operation that uses child keys of the list key that is bound to that listview. To prevent developers from performing an illegal operation, the keys are removed from the list. However, you can see those keys before making the workflow type operation a Listview details screen because it is not illegal in that circumstance; it is only illegal once you make it a Listview details screen. If you use those keys when it is not a Listview details screen and then make it a Listview details screen, the workflow operation fails without any indication of the problem.

Workaround:

Client-initiated workflow: verify that no online request operations (such as findall) precede the submit workflow type operation. If there are such operations, remove them.

Server-initiated workflow: verify that no links (between the start point and the first screen saved) precede the submit workflow operation. If there are such links, remove them.

Workaround: For best performance, keep the number of rows in choice controls smaller than 200.

Workaround: None.

This happens if you attempt to open a version 2.0 workflow on the iOS device and connect to version 2.1 of SAP Mobile Server.

Workaround: In SAP Control Center, use the HWC template to create an application connection, and leave the application identifier empty.

During Hybrid App package generation, you see a warning that validation keys are missing from the <locale>.properties file if the number of screens, controls, or menu items, have changed, for example, if you deleted a menu item. Resource strings associated with screens, controls, and menu items do not correctly update the sequence.

Workaround: Either do not remove screens, controls, menu items and so on after localizing, or manually correct the localization .properties file after making the changes.

SELECT x.* FROM Customer x WHERE x.state = :state 

Workaround: None.

"iAnywhere.MobileOffice.AMP.ResponseRetryException" on device, and following error in WorkflowClient.log: 

20110616T110249.554|4|My:1 -- ExecuteRequest- > Out 
20110616T110249.694|1|iAnywhere.MobileOffice.AMP.ResponseRetryException: Exception of type 
'iAnywhere.MobileOffice.AMP.ResponseRetryException' was thrown. 
20110616T110249.694|1| at Sybase.UnwiredPlatform.WorkflowClient.Utils.CheckMessageSize
(String serializedMessage, ContextData oContextData, Boolean fromResponder) 
20110616T110249.694|1| at Sybase.UnwiredPlatform.WorkflowClient.Responder.ProcessMessageFromDevice
(ContextData oContextData, String sData, Boolean isSynchronous) 
20110616T110249.694|1| at Sybase.UnwiredPlatform.WorkflowClient.Responder.ProcessSyncRequest
(ContextData oContextData, String sData) 
20110616T110249.694|4|My:1 -- ProcessSyncRequest- > Out

Workaround: Increase the allowed maximum message size (SupMaximumMessageLength). From SAP Control Center, expand Hybrid Apps and select the Hybrid App. Select the Context Variables tab. Modify the property.

See http://code.google.com/p/android/issues/detail?id=12987 for a description of this issue.

Workaround: Use an earlier version of the Android simulator. Alternatively, use Android simulator version 4.0 or later.

While you can add items to a listview and save the list, when you submit the operation, it is empty. Array/list fields in structure parameters are not supported. You can have a top-level parameter that is an array/list, and you can have a top-level parameter that is a structure that has non-array/list fields and substructures.

Workaround: None.

Workaround: None.

This happens only intermittently.

Workaround: If you know where to click for the drop-down, you can access the drop-down control, and it accepts your choice.

Workaround: None.