Known Issues for Hybrid Web Container

Workaround: SAP recommends that you decide prior to migration (or, in the case of newly written Hybrid Apps, prior to generation) which API setting you want to use. Failing that, after changing the API setting, delete the API.js, Utils.js, WorkflowMessage.js, and Custom.js files manually and regenerate the Hybrid App with the desired API setting.

Workaround: None. Wait up to a minute for the operation to complete.

Workaround: Use iOS version 5.0 or later.

Workaround: Register the Windows Mobile device to the Sybase Unwired Platform server before saving credential information to the device.

Workaround: Use a BlackBerry 7 device for deploying Hybrid Apps.

• showAlertDialog() – the title parameter is no longer used on iOS. It is already ignored on other platforms. This is true only for Sybase Unwired Platform versions 2.1.3 and 2.2sp02 (2.2.0 and 2.2sp01 work as before). 
• showConfirmDialog() – this function does nothing.

These functions are deprecated.

Alternatively, you can use PhoneGap APIs to display an alert or confirmation dialog. Be aware that although the PhoneGap APIs allow you to set the title of the alert and confirmation dialogs, and buttons, the PhoneGap APIs are asynchronous rather than synchronous, so using them as a direct substitute for the showAlertDialog() does not work. That would require refactoring the code in each instance where it is used.

Workaround: Include the sound files with the application. See the discussion about this problem at:  https://groups.google.com/forum/?fromgroups=#!topic/phonegap/xCOwgKh0IQ0

The badge count represents the number of queued items on the server that are waiting to be delivered. This matches the queue count for the application connection as seen in Sybase Control Center. As the items in the queue count includes items that are not necessarily new messages, this does not match the new message count of the Hybrid Web Container inbox.

Workaround: None.

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

(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. Then after several times of opening and closing the Hybrid App, 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. This is a known problem with RIM APIs on these devices. See https://www.blackberry.com/jira/browse/JAVAAPI-701   and http://supportforums.blackberry.com/t5/Java-Development/Storm-Torch-camera-getSnapshot-orientation-issue/td-p/1316867.

Workaround: None.

Workaround: If you want to save the password in the application, do so in the application code with the secured storage SUPStorage API.

Workaround: Run the BlackBerry Hybrid Web Container on newer OS 6.x or OS 7.x devices with more memory. A fix for this is not available from RIM for Java-based platforms. See  https://www.blackberry.com/jira/browse/JAVAAPI-2275

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.

Workaround: None.

On both window.open() and window.location.href the HTML5 sessionStorage values are not carried to the next page.

Workaround: None.

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

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

Workaround: Upload the log files again.

Workaround: None.

In Hybrid Apps running on iOS, numeric edit boxes do not validate user entries.

Workaround: None.

Workaround: If you receive an "MMS Authentication Failed" error message, check your certificate to make sure it is not expired.

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

Workaround: The hwc.startClient API must be called after the hwc.saveSettings invocation to connect to the server by manual registration.

The hwc.showProgressDialog and hwc.hideProgressDialog APIs do not work for the Windows Mobile Hybrid Web Container.

Workaround: Open the hwc-comms.js file, and remove for Windows Mobile in the hwc.showProgressDialog and hwc.hideProgressDialog functions. Change:

if (hwc.isWindowsMobile()) { navigator.cursor.setWaiting(); }
else { hwc.getDataFromContainer("showprogressdialog", "&message=" + message); }

hwc.getDataFromContainer("showprogressdialog", "&message=" + message); 

if (hwc.isWindowsMobile()) { navigator.cursor.setDefault(); }
else { hwc.getDataFromContainer("hideprogressdialog"); }

hwc.getDataFromContainer("hideprogressdialog"); 

If the Sybase Unwired 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. Sybase Unwired Platform currently assumes that application service nodes are installed to the same path on all the nodes in the cluster, that is, that all application server nodes are installed to 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 Sybase Unwired Platform using the same installation path for each node of the cluster.

Workaround: If you do not provision the Afaria server with the iOS Hybrid Web Container seeding file, the user must manually enter the connection settings for the Hybrid Web Container before launching it.

This issue does not occur if the Afaria client is not installed on the iOS device.

Workaround: None.

Workaround: Either turn off the proxy or connect through Sybase Relay Server.

If all of these conditions are true, these workarounds are available depending upon whether the Hybrid App is using JavaScript generated by the Mobile Workflow Forms Designer or using the Packaging Tool in conjunction with the JavaScript container code that ships with Sybase Unwired Platform 2.2.

Workaround #2: Modify hwc_api.js (usually installed in SUP_HOME\UnwiredPlatform\MobileSDK22\HybridApp\Container) in the Hybrid App to look like the following example, and redeploy the application to the Hybrid Web Container. 

/**   
    * Encapsulate the HTTP post method. This function is called internally   
    */   
   hwc.postDataToContainer = function( queryType, data)   
   {   
                try   
 {   
            var response = "";   
            if (hwc.isWindowsMobile()) {   
            xmlhttp = hwc.getXMLHTTPRequest();   
            xmlhttp.open("POST", "/sup.amp?querytype=" + queryType + "&" + hwc.versionURLParam, false);   
           
            xmlhttp.send(data);   
            response = xmlhttp.responseText;   
                   }   
                  else if (hwc.isAndroid()) {   
                     response = _HWC.postData("http://localhost/sup.amp?querytype=" + queryType + "&" + hwc.versionURLParam, data);   
                  }    
                  else if (hwc.isBlackBerry()) {   
                      var xmlhttp = hwc.getXMLHTTPRequest();   
                      xmlhttp.open("POST",
        "http://localhost/sup.amp?querytype=" + queryType + "&" + hwc.versionURLParam, false);   
                      xmlhttp.send(data);   
                         response = xmlhttp.responseText;   
                   }   
                 else if (hwc.isIOS())
        {   
                   var xmlhttp = hwc.getXMLHTTPRequest();   
                  xmlhttp.open("POST", "http://localhost/sup.amp?querytype=" + queryType + "&" + hwc.versionURLParam, true);   
                  try   
                  {   
                      xmlhttp.send(data);   
                  }   
                  catch (ex)   
                  {   
                     if (ex.message.search(/XMLHttpRequest Exception 101/) == -1)   
                     {   
                        throw ex;   
                     }   
               }   
         }   
         return response;   
      }   
      catch (ex)   
      {   
         hwc.log( "hwc.postDataToContainer error: " + ex.message, "ERROR", false);   
      }   
   }; 

Workaround: Do not close the application when the credentials dialog is presented.

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");
		}
    }
}

Workaround: None for BlackBerry 7.0. Upgrading to BlackBerry 7.1 eliminates the problem.

Workaround: None.

This can happen when all of these conditions are present:

• There is only one read-only edit box control on a single screen, and
• The application is using jQueryMobile GA version, and
• You are using an Android 2.2 simulator or Samsung Galaxy device with Android 2.2.

Workaround:

• Upgrade the OS on the device to Android 2.3, or,
• If using an Android 3.x simulator, see CR 673572, or,
• Add one or more controls to the screen.

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.

Workaround: Use a BlackBerry 9800 simulator with version 6.0.0.499 or later.

If 2.0 or 2.0 ESD #1 clients have not connected through an activated registration, and you upgrade to 2.1 ESD #3, those clients may not be able to connect to a 2.1 ESD #3 or a 2.2 server.

Workaround: Implement a server registration that uses an empty application ID, and use manual registration to connect the MBS and Hybrid Web Container 2.0 and 2.0 ESD #1 clients to the server.

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.