Known Issues for Hybrid Web Container for Windows Mobile

Workaround: Register the Windows Mobile device to Unwired Server before saving credential information to the device.

Workaround: Use a valid URL suffix when attempting to connect a 2.1.3 or older client to a 2.2 or newer server.

Within a closure code, when adding a new window property that references an object, the object is not correctly identified as garbage collection (GC) after closing the Hybrid App.

(function (window, undefined) { 
if (!window.OData) { 
window.OData = {}; 
} 

var odata = window.OData; 

odata.defaultHttpClient = { 
request: function () { xhr = new ActiveXObject("Microsoft.XMLHTTP"); } 
}; 
})(this);

When exiting the Hybrid App, window.OData still occupies the memory. After the Hybrid App is opened and closed several times, an "Out of Memory" error occurs.

//datajs
if (window.datajs) { window.ActiveXObject = window.oldActiveXObject; window.datajs = null; window.OData = null; window.oldActiveXObject = null; }
//hwc
window.CallbackSet = null;
window._Picture = null;
//cordova
window.console = null;
window.PhoneGap = null;
window.Cordova = null;
window.plugins = null;
window.addEventListener = null;
window.removeEventListener = null;

On Windows Mobile, if you experience a memory leak under these conditions, restart the device.

Workaround: Use the hwc.saveLoginCredentials() JavaScript API to save the user name.

Workaround: None.

Upon successful automatic registration, subsequent connections to the server uses the userid+deviceid+authcode combination (the password is not required). This is by design.

Workaround: To save the password in the application, do so in the application code with the secured storage SUPStorage API.

Workaround: Do not end the Hybrid Web Container process on Windows Mobile 6.0. It works as expected on Windows Mobile 6.5.

Workaround: None.

The version number of the new Hybrid App must be later than the current version number.

Workaround: Edit the manifest.xml file to update the version number and repackage the Hybrid App files.

Workaround: None.

Workaround: Make sure your certificate is not expired.

Workaround: After changing the default Hybrid App in SAP Control Center, restart the device.

Workaround: To connect to the server by manual registration, call the hwc.startClient API after the hwc.saveSettings invocation.

If the SAP Mobile Platform is installed in a cluster, and different paths are used on each application service node, the Hybrid App log may contain a message similar to Updated failed for Hybrid App item. SAP Mobile Platform currently assumes that application service nodes are installed in the same path on all the nodes in the cluster, that is, that all application server nodes are installed in the same path on all cluster nodes. It stores full paths in the database during Hybrid App package installation. When the client connects, it looks for those paths in the file system. If the node it is connecting to does not have one of those paths, you see the error.

Workaround: Install SAP Mobile Platform using the same installation path for each node of the cluster.

Workaround: None.

This can occur if a 2.1.2 (or older) version of the Hybrid Web Container (HWC) is installed on the same device as a native application using the Sybase Unwired Platform 2.1.3 libraries. The HWC and native applications share a common CMessagingCLient.dll.

Workaround: In order for a 2.1.2 (or older) HWC and a 2.1.3 native app to coexist and both successfully run on the same Windows Mobile device, install only the 2.1.3 version of CMessagingCLient.dll, and load it into memory on the device. Before starting either version of the application, verify that older versions of that DLL are removed from the device.

Workaround: When you use JavaScript to update the check box (using JQueryMobile) value, you must also add the refresh code. For example:

Whole sample in "customAfterMenuItemClick" method of Custom.js

function customAfterMenuItemClick(screen, menuItem) {
    if (screen === "Start" && menuItem === "setCheckbox") {
		var checkbox1 = document.getElementById('checkbox1');  
		checkbox1.checked = true;
		
		var checkbox2 = document.getElementById('checkbox2');
		checkbox2.checked = false;
		
		if (isJQueryMobileLookAndFeel) {
		    $("input[type='checkbox']").checkboxradio("refresh");
		}
    }
}

When using the imageElement.src = imageUri in the getPicture function, you cannot preview the selected image on the Windows Mobile emulator. This is because the HTML browser adds an unexpected prefix to the URI, so the Hybrid Web Container cannot find the file to which the URI refers.

The root cause is that Internet Explorer cannot load a large image; try one of these solutions to address the image size:

<img src="default-thumbnail.jpg" width="120" height="120" 
id="Thumbnail" sup_static_options="true" name="Preview" alt="Preview"/>

<img src="default.jpg?width=120&height=120" width="120" height="120" 
id="Thumbnail" sup_static_options="true" name="Preview" alt="Preview"/>

The width and height parameters are supported only on Windows Mobile and may cause display issues on other platforms.

• iOS - not supported.
• Android 2.2 - not supported. See http://code.google.com/p/android/issues/detail?id=9376.
• BlackBerry - supported.
• Windows Mobile - supported; however, can photograph only a grey/black screen.

Workaround: Use a physical device.

Hybrid Web Container/Workflow applications can display pictures from binary enterprise information system (EIS) data. But when a MBO developer drags and drops a table that contains an image field to create the MBO, the image field maps to a Binary datatype that has a length of approximately 3KB, which may not be large enough for the entire image. At runtime, the binary data of the image may be truncated in the cache database (CDB), and appear incorrectly on the device.

Workaround: When creating the MBO, manually modify the length of the binary field to make sure it is large enough to hold the image binary data, or use the BigBinary datatype instead.