Learn about known issues and apply workarounds for Hybrid Web Container (HWC) development.
Issue Number | Description |
---|---|
CR 722779 | Hybrid Workflow Application does not use the full screen on iPhone5 The Hybrid Workflow Application does not use the full screen on iPhone5. In portrait mode, narrow black bars appear on the top and bottom of the screen. In landscape mode, narrow black bars appear along the left and right side of the screen. Workaround: None. |
CR 721056 | Date/time picker does not open for iOS 6.0 The date and time picker does not pop up in iOS 6.0. This is not an issue on iOS 5.1.1. |
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:
|
CR 701485 | 'PictureOption.PictureSourceType' [undefined] is not an
object. In custom.js, the customGetPictureDataFromCamera() and customGetPictureDataFromLibrary() methods contain a typographical error in the camera source type. Workaround: Change the PictureOption.PictureSourceType.CAMERA to PictureOption.SourceType.CAMERA. |
CR 693907 | Hybrid Web
Container occasionally fails on Android. This can
happen when all of these conditions are present:
Workaround: Either:
|
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:
|
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 690013 | In iOS, the
Listview in a Scroll screen does not zoom in or out well. A pinch-to-zoom gesture must use some of the screen background and/or the header or footer. On a Listview screen (particularly one with many rows), there may not be any background revealed, making it appear that pinch-to-zoom is disabled, when it is not. Workaround: The gesture can use some small amount of background space surrounding the Listview, combined with the header or footers. Also, zooming can be toggled (Zoom In/Zoom Out) by clicking the title in the header. |
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: None. |
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. |