Known issues

When you specify the feature element in the configuration document, you must define feature IDs in a specific order for applications to recognize them. You must specify APIs starting with the most general one. (1248297)

Workaround: Specify APIs starting with the most general in the category, for example:
<feature id="blackberry.app" required="true" version="1.0.0.0" />
<feature id="blackberry.app.event" required="true" version="1.0.0.0" />
or
<feature id="blackberry.system" required="true" version="1.0.0.0" />
<feature id="blackberry.system.event" required="true" version="1.0.0.0" /> 

In either case, if you define the second ID first, errors will occur.

If the BlackBerry WebWorks SDK application archive (.zip) file name is greater than 10 characters in length, you cannot remove the application from the Home screen. (1243411)

Workaround: Shorten the .zip file name to 10 characters or less (not including the .zip extension). If you have already published the application to BlackBerry App World™, remove it directly by using the Delete button in BlackBerry App World.

The loading screen does not display properly in portrait mode. (1243215)

Workaround: None.

Embedded video is obstructed by overlapping when you scroll the page it is displayed on. (1239665)

Workaround: None.

If you install the debug token on the BlackBerry® PlayBook™ tablet and then subsequently install and uninstall a BlackBerry® WebWorks™ application, subsequent applications that you install will not run on the tablet. (1239001)

Workaround: Restart the tablet and then re-run the application.

When you use blackberry.invoke.invoke(blackberry.invoke.APP_VIDEOS) to start the Video application, the following message appears: "Cannot open the file. Please check the file permissions and try again." After you close the dialog box, the Video application starts normally. (1237080)

Workaround: None.

If the BlackBerry WebWorks SDK application archive (.zip) file name is greater than 10 characters in length, orientation will not work properly for the application. (1233358)

Workaround: Shorten the .zip file name to 10 characters or less (not including the .zip extension). If you have published the application to BlackBerry App World, you will need to remove it directly by using the Delete button in BlackBerry App World, before you attempt to publish it again.

During installation, in Mac OS, the default path is displayed as Research In Motion. The specific path should be displayed as /Developer/SDKs/Research In Motion. (1230810)

Workaround: None.

During video playback in HTML5, you cannot view the video in fullscreen mode. When you attempt to switch to fullscreen mode, the video remains the same size, while the background is blacked out. (1225131)

Workaround: None.

Geolocation is not able to return location information. From a BlackBerry WebWorks application, if you access a site that requests access to your location and grant that access, it will be unable to find your location. (1217601)

Workaround: None.

An error occurs if you specify a value greater than 25 characters in length for the name element. The BlackBerry® WebWorks™ Packager does not currently check this length when you package your application. (1200106)

Workaround: Ensure that you specify a value of 25 characters or less for the name element.

An error occurs if you specify a value greater than 18 characters in length for your application archive (.zip file) file name. The BlackBerry WebWorks Packager does not currently check this length when you package your application. (1200055)

Workaround: Although the error occurs if the file name is 18 characters or more, the .zip file must be 10 characters or less. Use a file name that is no longer than 10 characters.

In the config.xml file, if you specify an image file that is either incorrect or missing in the application archive file, an Unknown Source exception appears when you package the application. (1198688)

Workaround: Ensure that you specify the correct name for images you reference in the config.xml file, and that the images exist in the application archive.

When you attempt to sign your application, signing might fail with the message Cannot sign application - failed to find signing keys, if you specified incorrect parameters when you set up signing. For example, when you set up signing, if you specified the following using .pl2 (with a lowercase L instead of a 1) for the output file:
blackberry-keytool -genkeypair -keystore sigtool.p12 -storepass <p12password>
 -dname "cn=<company name>" -alias author

packaging would subsequently fail. (1197063)

Workaround: Ensure that you correctly specify the output file (and other parameters) when you set up signing. Also, use the specific path (bbwp/bin) for the output file.

BlackBerry WebWorks APIs are not supported in framesets or frames. (1092004)

Workaround: None.

Previous topic: Features

Was this information helpful? Send us your comments.