Known Issues for Hybrid Web Container

The Use backwards-compatiable API for generation (deprecated) option is used to generate JavaScript code using the SUP 2.1.3/2.2 naming convention, i.e. without hwc prefix for all JavaScript functions. These API signatures have been deprecated beginning with SAP Mobile Platform version 2.2 SP02.

When using iOS simulators, you may get the error "Unable to start client engine" when attempting to connect to SAP Mobile Server, after all connection information has been entered correctly in the Settings screen. This only happens on the simulator and not on real devices.

Workaround: Enter the connection information again and restart the application on the simulator, or use a real iOS device during development.

Depending on HTTP server behavior, client connection failures may occur when using the https-proxy plugin's HttpsConnection the first time (compared to the browser's default XMLHttpRequest) to send a HTTP(s) request to a remote server. When the client attempts to authenticate itself using basic authentication, failure may occur even when the user name and password are properly set in the header, with the server returning a 401 error.

Workaround: Send the request with username and password a second time.

Workaround: None. Keep the device online while performing registration with Afaria.

Workaround: Use a Sencha Touch version other than 2.1, such as 2.0.1 or 2.1.1.

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, manually delete the API.js, Utils.js, WorkflowMessage.js, and Custom.js files and regenerate the Hybrid App with the desired API setting.

See http://forum.jquery.com/topic/jquery-mobile-demo-page-causes-blackberry-7-1-simulator-browser-to-crash for information. This does not happen on an actual 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.2 SP02 (2.2.0 and 2.2 SP01 work as before). 
• showConfirmDialog() – this function does nothing.

Alternatively, you can use PhoneGap APIs to display an alert or confirmation dialog. Although the PhoneGap APIs allow you to set the title of the alert and confirmation dialogs, and buttons, the APIs are asynchronous, so you cannot use them as a direct substitute for the showAlertDialog() unless you refactored 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

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

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 (requires a login) and http://supportforums.blackberry.com/t5/Java-Development/Storm-Torch-camera-getSnapshot-orientation-issue/td-p/1316867.

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: Run the BlackBerry Hybrid Web Container on newer OS 6.x or OS 7.x devices with more memory. There is no fix available from RIM for Java-based platforms. See the following Blackberry sites, which require a login. https://www.blackberry.com/jira/browse/JAVAAPI-2275.

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 later 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.

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

Workaround: None.

Workaround: Make sure your certificate is not expired.

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

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

Workaround #2: Modify hwc_api.js (usually installed in SMP_HOME\UnwiredPlatform\MobileSDK<version>\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);   
      }   
   }; 

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.

iOS Hybrid Web Container fails when an Afaria client is not setup for seeding.

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.

This is an Android bug. See http://code.google.com/p/android/issues/detail?id=37050 for details.

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

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.

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

• 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.