Known Issues for Hybrid Web Container

Learn about known issues and apply workarounds for Hybrid Web Container (HWC) development.

Issue NumberDescription
CR 708778
If the Relay Server credentials dialog is presented and the iOS Hybrid Web Container application is closed and re-opened, any previously saved credentials are retried automatically.

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

CR 708173
When the Hybrid Web Container tries to retrieve data from the MBO package an "Invalid application id <***> for package" error is received.
Workaround: In Sybase Control Center, manually add an Application ID for the MBO package's application list.
  1. Log in to Sybase Control Center.
  2. Go to hostname@localhost > Applications and click the Applications tab.
  3. Click Properties.
  4. In Domains and Packages, select the Domain that contains the applicable MBO package.
  5. Assign the Application ID to the MBO's package's Applications list.
CR 708122
Native application on Windows Mobile device receives an error, "Can't find an Entry Point 'DLL_setMclCallbacks' in a PInvoke DLL 'CMessagingCLient.dll".

Workaround: 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 SUP 2.1.3 libraries. The HWC and native applications share a common CMessagingCLient.dll. 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, the 2.1.3 version of CMessagingCLient.dll should be the only one installed and loaded into memory on the device. Make sure older versions of that DLL are removed from the device prior to starting either application.

CR 707616

When writing a Hybrid Web Application for iOS using the PhoneGap API navigator.camera.getPicture() and specifying FILE_URI as the destination type, you cannot display the image. The same is true for the result of any call to FileEntry.toURI(), DirectoryEntry.toURI(), or anything else that references file URIs.

The problem occurs because of a security restriction that does not allow pages with non-local schemes from loading resources with local schemes. File URIs are considered local schemes.

Workaround: Patch 01 fixes this issue. See the Fixed Issues in Patch 01 in the Sybase Unwired Platform 2.1 ESD #3 Patch 01 section of this release bulletin.

If you cannot apply the patch, then use this workaround: Modify the URL so that it looks like a local file path without the extra file URI syntax. One way to do this is to intercept the callback at the javascript layer, and strip off the file://localhost or file:// at the beginning of the URL. This leaves a bare file path like /var/mobile/.... Using the PhoneGap getPicture() function as an example, your success callback function might have this code: 
function onPhotoURISuccess(imageURI) {   
var newURI = imageURI.replace("file://localhost","");   
newURI = newURI.replace("file://","");
document.getElementById('MyImg').src = newURI;
}
CR 705895
After adding JavaScript code in the customAfterMenuItemClick method to update the checkbox (using JQuery Mobile) state on the screen, the checkbox fails to update.

Workaround: When you use JavaScript to update the checkbox (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");
		}
    }
}
CR 705219
When the iOS Hybrid Web Container application tries to retrieve seeding information from an Afaria iOS App store hosted package you receive an error message: Afaria client application is installed but not configured. Please configure Afaria client application and try again or go to the Settings application and enter your configuration information.
Workaround:
  • Seeding works for Enterprise hosted packages on the Afaria server.
  • You can still manually configure the connection information.
CR 703883
Switching from one edit box to another on a BlackBerry 7.0 simulator or device using the touch screen or mouse requires two clicks or touches.

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

CR 702603
On BlackBerry 7.0 devices, a white screen is seen until the Workflow application's activation screen opens. See https://www.blackberry.com/jira/browse/JAVAAPI-119

Workaround: None.

CR 693907
Hybrid Web Container occasionally fails on Android 2.2.

This can happen when all of these conditions are present:

  • There is only one read-only edit box control on a single screen
  • Using jQueryMobile GA version
  • On an Android 2.2 simulator or Samsung Galaxy device with Android 2.2

Workaround: Either:

  • Upgrade the OS on the device to Android 2.3or
  • If using an Android 3.x simulator, see CR 673572. or
  • Add one or more controls to the screen
CR 693381
Cannot preview a selected picture On Windows Mobile emulator.

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: Either:
  • Preview the image using an actual device instead of the emulator, or
  • Assign image data instead of image URI to the image element so the image data can be retrieved through the JavaScript API
CR 691005
Image upload may fail on BlackBerry 6 simulators older than version 6.0.0.499.

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

CR 688399
On Windows Mobile devices, thumbnails do not show properly if an image has a large size..

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

Solution 1: Specify a small-sized image as the thumbnail instead of using the original large image, for example: 
<img src="default-thumbnail.jpg" width="120" height="120" id="Thumbnail" sup_static_options="true" name="Preview" alt="Preview"/>
Solution 2: Pass the width and height as the parameters in the source of the image control, so the container compresses the original image on the fly, for example: 
<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.

CR 686465
Camera feature is supported on some device simulators/emulators.

Workaround: Use a physical device.

CR 680253
Images do not appear correctly on mobile devices.

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 not appear correctly 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.

Parent topic: Known Issues for Sybase Mobile SDK 2.1 ESD #3