BlackBerry 10 WebWorks SDK 2.2 Release Notes

Release: BlackBerry 10 WebWorks SDK

BlackBerry WebWorks is built on Apache Cordova, an open source development framework that lets you create applications using web technologies. By aligning with Apache Cordova, BlackBerry WebWorks apps are now easier to output to multiple platforms.

This release of the BlackBerry 10 WebWorks SDK builds upon the features provided in the previous releases.

Installation notes

For Ubuntu users:

If you are installing to Ubuntu, after downloading the installer, you'll need to make it executable by running the following commands:
$ chmod u+x ./ BB10-WebWorks-SDK_<version>.bin
$ ./BB10-WebWorks-SDK_<version>.bin

The ~/.bash_profile isn't automatically used on Ubuntu, so WebWorks is not in the PATH by default. Add . ~/.bash_profile to ~/.bashrc or ~/.profile after installation.

Upgrading notes

After installing BlackBerry 10 WebWorks SDK 2.2, you may encounter the following error when you attempt to build a project created using an earlier version of the BlackBerry 10 WebWorks SDK:
[INFO] 'java' is not recognized as an internal or external command, operable program or batch file. 
[ERROR] Native Packager exception occurred

If you receive this error, you need to upgrade your project. If you do not see the Upgrade option on the Configuration page of the SDK web tool, you can still upgrade your poject using the webworks upgrade command from the command line. See Updating your WebWorks project for more information.

Fixed Issues

The following issues from the previous release of WebWorks have been fixed in BlackBerry 10 WebWorks SDK 2.2:

JI: 16989

Previously, when creating a headless WebWorks project, the SDK failed to include two Makefiles with the C/C++ source for the headless component of the app. You needed to download the missing Makefiles manually. These Makefiles are now included for use by Momentics.

JI: 15908

Previously, the tools erroneously allowed you to remove a plugin from your app even if that plugin was a dependency of another plugin with no warning. This issue has been fixed with this release.

Known Issues

JI: 17760

If you view the usage of the webworks emulate command by typing webworks help emulate, the --no-uninstall option is listed as being supported. This documentation is in error; support for the --no-uninstall option has been removed for this command. If you attempt to run the webworks emulate --no-uninstall command, an 'unknown option' error is returned.

JI: 16669

If you try to add a plugin directly from a Git repository using the URI (for example, webworks plugin add, the operation may fail on Windows.

To work around this issue, first clone the repository and then add the plugin using the local path instead.

JI: 16668

After upgrading the VMware Player, the BlackBerry 10 WebWorks SDK may not detect a simulator that was paused before the upgrade. You must restart the simulator in the player before the SDK is able to automatically detect it.

Last modified: 2014-10-09

Got questions about leaving a comment? Get answers from our Disqus FAQ.

comments powered by Disqus