10.2 Gold Release Notes
The BlackBerry 10 Device Simulator allows you to simulate the BlackBerry 10 OS environment to help you develop your apps. Take a look at the release notes.
Visual Studio Plug-in
Prefer to develop in Microsoft Visual Studio? We have the BlackBerry Native Plug-in for Microsoft Visual Studio. Take a look at the latest release notes.
If you're interested in upgrading your apps, skip down to the Changes in this release section to find out what APIs are changing in this release.
Upgrading to 10.2 Gold
Core - Highlights
QNX Momentics IDE
In case you missed it in the 10.2 beta release, the QNX Momentics IDE for BlackBerry has a new and simplified interface. We've introduced API levels which can help you determine what APIs are available on a device OS version. You can also get access to developer forums, documentation, and sample apps straight from the IDE. For more information on the new IDE, visit Getting Started.
App signing changes
In this release, the way that you sign your apps (to prepare them for distribution in the BlackBerry World storefront) has changed. Previously, you used code signing keys that you obtained from BlackBerry to sign your apps. Now, you use a BlackBerry ID token that's associated with your BlackBerry ID. To learn more about these changes, see Signing apps.
We've added a few new permissions that you can specify for your apps. Permissions let your app access sensitive or restricted functionality on the device, such as contact information and shared files. To see what permissions are new, check out the New in this release section. For more information on permissions, take a look at App permissions.
Core - New in this release
We've added new functionality:
- You can suppress the progress dialog when your app registers with BBM to create a more seamless experience for the user by calling bbmsp_register_silent(). When registration is complete, a system toast appears to the user, confirming that your app is connected to BBM.
- You can retrieve the version of BBM that is running on a user's or a contact's device by calling bbmsp_profile_get_bbm_version() or bbmsp_contact_get_bbm_version(). You can then determine which version of the BlackBerry OS is running on the device (for example, BlackBerry 7 and earlier, or BlackBerry 10).
- You can determine whether a user has completed the setup of BBM on their device by signing in with their BlackBerry ID (Setup > BlackBerry Messenger) by calling bbmsp_is_bbm_setup().
- A new registration state, BBMSP_ACCESS_BLOCKED_ENTERPRISE_PERIMETER, is available to indicate that registration with the BBM Social Platform is blocked because your app is installed in the Work perimeter. To connect to BBM, your app must be installed in the Personal perimeter.
This is a new API with functions to determine changes to the cellular network status on the device.
This is a new API with functions that enable screen input guard, which is a feature of the device that turns the screen off and disables the touch screen during a phone call or similar voice chat. This API lets your app avoid unwanted touches causing unintended events.
Added the following data type and functions:
Added the following functions:
Added the following functions:
Added the following data type and functions:
Added the following constant, data type, and functions:
- NETSTATUS_INTERFACE_TYPE_P2P (netstatus_interface_type_t)
Deprecated the following functions:
Added the following function:
Added the following constants:
Deprecated the following constant:
- Bluetooth GATT server
- You can now use your BlackBerry 10 device as a GATT server. The APIs are available in btgattsrv.h
- Blutooth Human Interface Device (HID)
- You can implement the Bluetooth HID profile to remote control HID hosts. The APIs are available in bthid.h
- Blutooth Object Push Profile (OPP)
- You can use the OPP APIs to send files to a paired Bluetooth device that supports OPP. The APIs are available in btopp.h
- Bluetooth low energy
Added the following constants and functions:
Added the following functions:
Added the following enumerators to camera_error_t:
Added the following function:
In addition to the listed share target items, users can now see large app icons (358 x 358 pixels) of share targets in the target selection menu. These suggested target app icons appear based on the user's recent selections.
For more information, see App integration.
Your app can use this API to receive notifications about the insertion or removal of peripheral devices. As well, your app can retrieve information about inserted peripherals.
For more information, see Peripheral Discovery Library.
The following new permissions have been added:
- Automatic Input Control (_sys_inject_events)
- Control Notification Settings (access_notify_settings_control)
- Gamepad (use_gamepad)
- Phone Control (control_phone)
- Run in Background (_sys_run_headless)
- Screen Capture (use_camera_desktop)
- User Contact Information (read_personally_identifiable_information)
- Wi-Fi Connection (access_wifi_public)
Note that the run_when_backgrounded permission was previously called "Run in Background". This permission is now called "Run as Active Frame", and the _sys_run_headless permission is called "Run in Background".
For more information, see App permissions.
Default UI is available for 'Challenges' along with 'Favorite a game', 'Edit profile', 'Leaderboards', and 'Awards & Achievements'.
Added the following functions:
Added the display property SCREEN_PROPERTY_INTENSITY to support application-controlled brightness.
Added the window property SCREEN_PROPERTY_PERMISSIONS to support window permissions.
Added the following window permission masks:
The VPN Extensions Library lets you create extensions to the VPN service, each of which can be associated with a VPN adapter. You can use the functions in this library to perform tasks such as creating a VPN Extension context, adding a Key Agreement callback, and running the VPN service.
For more information, see VPN Extensions Library.
- Wi-Fi hotspot aggregator capabilities
- You can create hotspot aggregator applications that manage authentication to a Wi-Fi hotspot. The APIs are available in wifi_service.h
Core - Changes in this release
In this release, the way that you sign your apps (to prepare them for distribution in the BlackBerry World storefront) has changed. Previously, you used code signing keys that you obtained from BlackBerry to sign your apps. Now, you use a BlackBerry ID token that's associated with your BlackBerry ID.
To learn how to sign your apps using this new process, see Signing apps.
Deprecated the following definitions:
If your app calls bt_ldev_get_address(), in the Application tab of the bar-descriptor.xml file of your app, you must enable the read_device_identifying_information permission. This requirement will be enforced in a future release. When it is enforced, any calls to bt_ldev_get_address() without the required permission will fail with an error message.
The following functions and data type were incorrectly included in the header file and should not be used.
The default monitoring mode for regions is now transient. Previously, the default monitoring mode was permanent.
The following functions were removed and replaced by new functions:
- geomonitor_region_get_stop_monitoring_event(), which replaces geomonitor_region_get_delete_on_event()
- geomonitor_region_get_foreground_mode(), which replaces geomonitor_region_get_stop_monitoring_event()
- geomonitor_region_get_offline_notification_target(), which replaces geomonitor_region_get_notification_invoke_target() and geomonitor_region_get_notification_message()
- geomonitor_region_set_delete_on_event(), which replaces geomonitor_region_set_stop_monitoring_event()
- geomonitor_region_set_foreground_mode(), which replaces geomonitor_region_set_monitoring_mode()
- geomonitor_region_set_offline_notification_target(), which replaces geomonitor_region_set_notification_invoke_target() and geomonitor_region_set_notification_message()
Added the following data type and functions:
Deprecated the following functions:
Core - Fixed in this release
BlackBerry Platform Services
PR: 337891 JI: 391372
Using the Screen capture API, the function screencapture_grab() failed with the error message:error code 9 - CAMERA_EBADFerror message: Failed to open screencapture control PPS object
PR: 342618 JI: 394100
The complete set of offline help documentation was not available in the 10.2 beta version of the QNX Momentics IDE. It included only Using the QNX Momentics IDE. You could access the latest version of the online documentation on the BlackBerry Native SDK Documentation site.
PR: - JI: 469847
If you sent port-directed SMS messages to an invocation target that was a headless app, the Chat service invoked the target only once and a port-directed SMS trigger was emitted only once, regardless of the number of port-directed messages that were sent.PR: - JI: 469844
If you loaded a headless app on a device, you (correctly) received a System Started trigger. Then, if you restarted the device, you (incorrectly) didn't receive the System Started trigger again.PR: - JI: 460515
You could not invoke a service from a headless app.PR: - JI: 458228
When a headless app was invoked, and that headless app was not currently running, the headless app launched but was sometimes terminated due to an app connection timeout.
PR: - JI: 420257
In the QNX Momentics IDE, installing more than one API Level at the same time would result in an error.PR: 348970 JI: 403373
When using the Darwin (Apple) command line, the DYLD_LIBRARY_PATH environment variable was not set from the environment script. This caused some compiles or commands to fail. If you installed additional targets, you needed to modify the target scripts in a similar manner.PR: 348781 JI: 403370
When using the DOS command line, Windows environment variables were not set with forward slashes "/". This caused some compiles to fail. If you installed additional targets, you needed to modify the target scripts in a similar manner.PR: 345080 JI: 394155
When using the DOS or Linux command line, environment variables were not set to use the packaged JRE from the environment batch file. This could sometimes cause a command that uses Java to fail.PR: 343485 JI: 402268
Installing the Native SDK into the same folder as a previous version was not supported (see also PR: 239960, JI: 402307, and JI: 402280).PR: 339022 JI: 402297
When you installed the QNX Momentics IDE, you are now correctly unable to select a folder name that contains spaces, which would prevent your sources from compiling properly.PR: 327200 JI: 393988
If you canceled the SDK installation and did not have an SDK, you could not create a BlackBerry project. It is now clearer that the required SDK is missing and how to resolve the issue from the IDE.PR: 144987 JI: 402249
When you uninstalled the Native SDK on Mac or Linux, you might have received a warning that some files were not removed. This could be ignored and you could manually delete the remaining files. Mac now uses a drag-and-drop installation.
PR: 338399 PR: 337813 JI: 380460 JI: 377399
An unbound invocation query may have caused some invocation targets to appear twice in the menu. (See also 345183)
QNX Momentics IDE
PR: 349604 JI: 394341
On Mac OSX, launching the BlackBerry 10 Simulator from within the IDE may have caused Momentics to crash.PR: 347053 JI: 394236
Linux command line users needed to use the system's Java runtime or add an executable bit on features/com.qnx.tools.jre.linux_*/jre/bin and add this to their PATH.PR: 344313 JI: 394138
To display the source code navigator, on the Window menu, you needed to click Show Advanced Toolbars.PR: 337857 JI: 394062
If you already had a simulator installed, and the device manager in the QNX Momentics IDE did not recognize it, you needed to manually pair it in the IDE.PR: 302984 JI: 393914
On Mac OS, running the bbndk-env.sh script after running the mkbuild script produced an error.PR: - JI: 418611
If you uninstalled or aborted the installation of the BlackBerry 10 simulator from within the IDE, it no longer appeared in the Device Manager list or was available to download from within the IDE.
PR: 344761 JI: 394147
On Mac OS, the simulator controller could not be launched from the simulator installation location.
Core - Known limitations
BBM Social Platform
- Apps installed in the Work perimeter cannot access the BBM Social Platform. To connect to BBM, your app must be installed in the Personal perimeter.
- When you retrieve the version number of the BBM Social Platform library that is running on a contact's device, the value returned might be unreliable if the device is running BlackBerry 10 OS version 10.2 or later.
BlackBerry ID and Signing Authority linking
- If you do not register your signing key and your BlackBerry PlayBook debug token with the same clientID, an error will be thrown when you try to link your BlackBerry ID account with a Signing Authority account. A fix will be available in the next release.
- Applications using FreeType must add the following include path: $QNX_TARGET/usr/include/freetype2
- The Native SDK does not support Shared Install.
- When you execute bbndk.sh to launch the Native SDK on Ubuntu 11.04 32-bit, you will receive an error:
"QNX Compiler Configuration Error". Run the ./qde app instead.
- By default, the Native SDK installer creates the installation folder on Windows systems at the root of the C drive in C:\bbndk. During installation, you need to provide the administrative username and password or, if you are the administrator, accept that the SDK is installing on the C drive.
- When installing and uninstalling the Native SDK on a 64-bit Linux host computer, you may see an error regarding a missing libc.so.6 file. You can disregard this error message.
- On Mac computers, you may encounter an issue with incorrect permissions on the Native SDK installer executable. To launch the installation program, you will first need to manually change the permissions for the installer.
- To run the installer and the IDE on Ubuntu 64-bit, you need to install the 32-bit libraries: sudo apt-get install ia32-libs. During the installation, answer yes to all the questions.
- If an app plays a media stream that's encrypted, the app won't allow video playback if an HDMI display is connected, due to security restrictions. This limitation will be resolved in a subsequent release.
- There is a slight delay between tracks played as part of a playlist (approximately 0.5 seconds), even when the playlist includes only one track that is repeating.
- The OpenAL 1.1 Specification and Reference incorrectly states that the function alcCloseDevice() will fail if the device's contexts and buffers have not been destroyed. alcCloseDevice() actually destroys any contexts and buffers still associated with the device.
- The function alcGetIntegerv() does not throw an error when retrieving ALC_MAJOR_VERSION and passing an invalid device pointer.
- The function alcGetString(device, ALC_CAPTURE_DEFAULT_DEVICE_SPECIFIER) throws an error when invoked after the device has been closed. It should return the default device and ignore the device parameter.
- The OpenAL 1.1 Specification and Reference incorrectly states in the description of the function alcGetString(), "Specifying NULL for deviceHandle when asking for ALC_EXTENSIONS will generate an ALC_INVALID_DEVICE error." In fact, no error is generated.
- The OpenAL 1.1 Specification and Reference incorrectly states in the description of the function alBufferData() that, "An invalid size will result in an AL_INVALID_VALUE error." In fact, calling alBufferData() with an invalid size does not cause the INVALID_VALUE error.
- When the function alcMakeContextCurrent() is called with an uninitialized ALCcontext pointer, it correctly returns ALC_FALSE, but does not generate an ALC_INVALID_CONTEXT error.
- The OpenAL Programmer's Guide - OpenAL Versions 1.0 and 1.1 incorrectly lists AL_INVALID_VALUE as a possible error returned by the functions alGenBuffers() and alGenSources() when the array is not large enough to hold the number of items requested. In fact, no error is generated.
- The function alSource3f() does not throw an AL_INVALID_VALUE error when invalid numbers are passed as parameters. Apps should perform their own validity checking.
- The function alSourcef() throws an AL_INVALID_VALUE error for valid values when using AL_CONE_INNER_ANGLE and AL_CONE_OUTER_ANGLE.
- No error is thrown when the function alutLoadWAVFile() is called without a current context.
- The function alutGetError() does not return ALUT_ERROR_ALC_ERROR_ON_ENTRY when there was already an ALC error on entry to alutLoadMemoryFromFileImage().
- In the OpenAL Programmers Guide, AL_DATA is incorrectly documented as a valid buffer property. An attempt to retrieve this property through alGetBufferi() and alGetBufferiv() will result in an AL_INVALID_ENUM error.
- The deprecated function alutLoadWAVMemory() does not return the expected values.
- The function alGetListenerfv() does not generate an error when called with an invalid value. Apps should perform their own validity checking.
- The following attributes are set by the device, and cannot be altered using the attribute list of the function alcCreateContext(): ALC_FREQUENCY, ALC_REFRESH, ALC_SYNC, ALC_MONO_SOURCES, ALC_STEREO_SOURCES, ALC_MAX_AUXILIARY_SEN.
- The OpenAL 1.1 Specification and Reference incorrectly states that the function alGetEnumValue() sets the error code AL_INVALID_VALUE if the specified enumeration cannot be found. In fact, this error is not set when an invalid enumeration value is specified.
- The OpenAL Programmer's Guide - OpenAL Versions 1.0 and 1.1 incorrectly states that the functions alcSuspendContext() and alcProcessContext() produce the error ALC_INVALID_CONTEXT when called with a null or destroyed context. However, no error is generated.
- The function alListener3f() does not generate an error when called with a NULL value for the AL_VELOCITY attribute. Apps should perform their own validity checking.
- The function ALCGetProcAddress() does not return addresses for the specified context extension functions, even for valid functions. It always returns NULL.
- The function alSourceQueueBuffers() queues invalid buffers. If you pass a NULL buffer to this function, it will queue the buffer and not raise an error, even though the buffer is not valid.
BlackBerry 10 uses OpenSSL 1.0.1, with the following deviations from the standard implementation:
- TLSv1.2 is not supported.
- TLSv1.1 support is disabled by default.
- The heartbeat TLS extension has been disabled. This extension is described by RFC 6520, which is located at http://www.rfc-editor.org/rfc/rfc6520.txt.
- The list of default SSL/TLS/DTLS ciphersuites has been altered.
- Applications using SSL/TLS/DTLS connections to get a default set of ciphersuites unless they explicitly specify which ciphersuites they want to support using SSL_CTX_set_cipher_list() or SSL_set_cipher_list().
- The default set of ciphersuites has been changed to "ALL:!aNULL:!eNULL:!SRP:!SSLv2" which eliminates the SRP ciphersuites from the standard default set of ciphersuites provided by OpenSSL 1.0.1.
- SSL_CTX_new(), which is used to create a new SSL_CTX object for TLS/SSL/DTLS negotiations, has been altered to disable TLSv1.1 support by automatically setting the option SSL_OP_NO_TLSv1_1.
- TLSv1.1 will be disabled by default when using SSLv23_method(), SSLv23_server_method(), or SSLv23_client_method(). Applications that need TLSv1.1 support can clear the option by calling SSL_CTX_clear_options(ctx, SSL_OP_NO_TLSv1_1) or can use one of the following TLSv1.1-only methods: TLSv1_1_method(), TLSv1_1_server_method(), or TLSv1_1_client_method().
When you use the BlackBerry 10 Device Simulator to test your apps, your apps cannot communicate with the BlackBerry World servers to test certain Payment Service features. To test Payment Service features on the simulator, you should use Local Mode testing.
If you need to test your apps by interacting with the BlackBerry World servers, you need to run the app on a physical device and use a BlackBerry ID in sandbox mode. For more information about testing apps that use the Payment Service, see Testing in-app purchases.
QNX Momentics IDE
- It is possible that the debugger may take 5-10 minutes to launch in certain circumstances.
- When you use the Memory Analysis tool, you may see an empty graph with the warning "No graphical input". This is by design for security reasons and this information is unsupported for BlackBerry 10 OS targets.
- Standard makefile projects cannot be named "makefile". Use a different name for your project.
- Memory leaks are only reported when an application exits normally. If it is killed or crashes, memory leaks will not be reported. To report memory leaks in this case, the API should be used.
Social networks are not supported in this Scoreloop release. APIs related to the following classes are unsupported:
- SC_Message (Partial)
- SC_Message_Controller (Partial)
- SC_SocialController (Partial)
- SC_SocialNetwork (Partial)
For more information on the Scoreloop SDK, see the following resources:
- API reference and Integration information
- Scoreloop SDK sample applications
- Support for integrating the SDK into your gaming project
Core - Known issues
PR: - JI: 477424
For this release of the BlackBerry 10 Native SDK and the BlackBerry 10 OS, the size of Active Frames is 310 x 396 for devices with a 720 x 1280 screen resolution. In the future, and for future devices with this screen resolution, the size of Active Frames will be 319 x 437. It is recommended that you create assets and text for Active Frames that support the 319 x 437 size. This may cause your Active Frame to look distorted when developing for the 10.2.0.1443 release and earlier but it will appear as expected for future releases and devices.
BBM Social Platform
PR: 261200 PR: 218238 JI: 389356 JI: 389093
When the Connect to BBM permission (Settings > Security and Privacy > Application Permissions) is toggled from enabled to disabled or from disabled to enabled, the registration and permission states are not updated.
Workaround: Restart the app if permissions have been modified.
PR: - JI: -
The documentation that is embedded in the library header files for the following APIs may not be the most recent:
- Bluetooth Library
- Camera Library
- Unified Data Source (Hub Integration)
- Near Field Communication Library
- VPN Extensions Library
For the most up-to-date documentation, refer to the online documentation for each library.PR: - JI: 492681
In the Camera API Library offline documentation, the following functions and data type should not have been included:
We are hard at work creating an awesome UI experience for you! While we are doing this, some references to the BlackBerry 10 UI, including screenshots, may not reflect what you see in the current software.PR: - JI: -
In previous releases, the most recent version of the BlackBerry Platform Services library (libbps) was bundled with the Native SDK. This version was newer than the version on the target OS. To ensure the correct BPS library version was used by applications at run-time, projects in the Native SDK 1.0 would:
- Use BPS headers from the $QNX_TARGET/../target-override location for compilation,
- Link the libbps.so from the $QNX_TARGET/../target-override location to generate the application executable, and
- Package the libbps.so from the $QNX_TARGET/../target-override location in the BAR.
As of the Native SDK 2.0.0 release, BPS no longer resides in the target-override location. The BlackBerry 10 OS and BlackBerry 10 Native SDK versions of this library are in sync. If you have applications targeting BlackBerry 10 that you no longer want to support on PlayBook 1.0.x, you should remove the libbps.so.1 asset from bar-descriptor.xml and target the BlackBerry 10 version of the Native SDK. To verify, select the QNX page in the project properties dialog. Otherwise, packaging of the BAR file will fail because it will not be able to find the libbps.so file to include in the BAR.
PR: - JI: 482561
Currently, when implementing a headless app, you can invoke notification dialogs using the Notification dialog functions of the Dialog API. Global dialogs are not encouraged as they are disruptive to the user experience. This will be fixed in an upcoming release.PR: - JI: 479013
If your app is in the enterprise perimeter, the sms trigger does not invoke the app because the default is to invoke the app in the personal perimeter. Since the app is not there, nothing gets invoked.PR: - JI: 478856
Applications installed in the enterprise perimeter can’t be invoked by the Geomonitor service. Invocation defaults to the personal perimeter and not enterprise.PR: - JI: 461671
When a headless app is invoked, the ApplicationStartUpMode is erroneously listed as LaunchApplication.PR: - JI: 461658
Currently, the category type for headless apps is incorrectly returned as "service". In the future, the correct type will be returned.PR: - JI: 461484
Headless apps are erroneously able to post windows, window groups, and dialog requests, which make them non-headless and display a UI.
PR: 346256 JI: 394200
When you perform a software update, you must accept the security warning about installing unsigned software, and continue the installation.PR: 339019 JI: 402296
When installing on Windows XP, you must specify a different installation location, instead of using the default location. The folder name must not contain spaces.PR: 261783 JI: 402276
When you run the BlackBerry Native SDK installer on Windows 8, you cannot create a shortcut in the Start menu.
Workaround: You can use options in the installer to create shortcuts on the Desktop and the Quick Launch bar.
On Linux systems, if the launch command contains "..", the Native SDK installer fails.PR: 110605 JI: 402236
You might get a warning after uninstalling the Native SDK that some directories couldn't be removed. This can be ignored.
PR: 345225 JI: 389904
When reading a URI tag that contains ‘pin’, the BBM application doesn't handle the content of the tag, but the Smart Tags application does and invokes the URI.
PR: - JI: 403249
When using OpenAL to play sound on the device and an HDMI cable is plugged in, the sound does not transfer on to the connected device.PR: 112769 JI: 403231
You cannot create two contexts with different attributes by calling alcCreateContext(). Errors are produced after attempting to create the second context, you can no longer call alcOpenDevice(), and sound is no longer playable in other OpenAL apps.
QNX Momentics IDE
PR: - JI: 495678
If you have an old workspace with projects that refer to an API Level that is no longer installed and there are no other API Levels installed, you will get a ‘string index out of range’ error when you try to build your project.
Workaround: Install an API Level and restart the QNX Momentics IDE.
In the QNX Momentics IDE, if you open a new workbench window using Window > New Window and then close the original window, the new main toolbar is missing even if you restart the QNX Momentics IDE.
Workaround: In your workspace, remove the file .metadata/.plugins/org.eclipse.e4.workbench/workbench.xml.
The application binary interfaces for the Dinkum C++ and GNU C++ libraries are incompatible. If you link an app against both libraries, you'll get a segmentation fault.PR: - JI: 480112
In the 10.1 version of the IDE, if you clear the check box Update IDE while installing the 10.2 SDK, you must update the IDE separately by clicking Help > Check for Updates. For compatibility, the 10.2 version of the SDK requires the 10.2 version of the IDE.PR: - JI: 470689
If you have an OS version on your device that is newer than 10.2.0.1157 and, while running the debugger against your installed OS build, the debugger is not performing as expected, then you may have a mismatch with your runtime. You need to make sure the matching runtime is used instead of the API level.
- Run the debugger.
- At the prompt to download a new runtime, click Yes.
- When the runtime is downloaded, exit the QNX Momentics IDE.
- Go to the folder where you installed the NDK.
- Copy the runtime_10_2_0_xxxx folder to runtime_10_2_0_xxxx+2. For example, runtime_10_2_0_1443 becomes runtime_10_2_0_1445.
- In the runtime_10_2_0_xxxx+2 folder, edit the runtime.properties file to change the version=10.2.0.xxxx to version=10.2.0.xxxx+2. For example, version=10.2.0.1443 becomes version=10.2.0.1445.
- Restart the QNX Momentics IDE. The correct runtime is detected and set for your installed OS build.
In the bar-descriptor file, the <action> element used in previous versions of the Native SDK has been changed to be used with the Invocation Framework. The <permission> element has been reinstated for use to control permissions for an application. If you need to add permissions to your <action> application, you must change it to use the <permission> element. For more information, see The application descriptor file DTD.PR: - JI: 469900
On Linux, you cannot open the controller for the BlackBerry 10 Device Simulator through the Simulators tab in the Device Manager screen, even when the matching simulator for the Native SDK is installed, paired, and launched properly.
Workaround: Launch the controller manually from <ide_install_folder>/simulator_x_x_x_x/controllers/controller.
If you create a project using the 10.1 version of the Native SDK and specify that the project should use the 10.1 API level, and then update the IDE to the 10.2 version and install the 10.2 API level, project-specific settings automatically switch to use the new 10.2 API level.
Workaround: Manually change the API level of the project back to 10.1.
On Linux, if you're using the INSTALL_DESCRIPTOR_LOCATION, install the 10.0 or 10.1 version of the IDE, and then check for updates using Help > Check for Updates, you receive an error stating that the update site can't be reached.
Workaround: Click Help > Install API Level, which parses the install_descriptor for information. Then, close the API Level Manager without performing any actions and check for updates again.
On Windows XP, if you install the Native SDK as an administrator using the default installation settings, and then log on as a non-administrator and start the IDE, you receive an error indicating that you cannot access the Native SDK.PR: - JI: 393847
When you debug C programs, global variables do not appear in the Variables view.
Workaround: Type an expression in the Expressions view for each global variable that you want to inspect.
If you create a project that requires permission confirmation from the user (such as a geolocation permission), and then build and launch the app on the BlackBerry 10 Device Simulator, you receive an "Unable to determine returned PID from launch" error if you don't accept and dismiss the permissions dialog box on the simulator in a reasonable amount of time.PR: - JI: 393602
Breakpoints that you set from .gdbinit are not visible in the UI of the IDE.PR: - JI: 393564
When you change a library project name in the IDE, the library references of application projects that use that library are not updated automatically to use the new name.
Workaround: Update the library references manually. You can do this by clicking Preferences > C/C++ General > Paths and Symbols and changing the references in Includes, Libraries, and Library Paths. Or you can the bar-descriptor.xml and change the references in the <qnx>, <configuration>, and <asset> elements.
The Memory Analysis tool does not always collect all available events with multiple clients.PR: 346267 JI: 402332
On Mac OSX 10.8, if applications are downloaded from 'Anywhere', you receive a dialog box that states "Momentics is an application downloaded from the Internet. Are you sure you want to open it?" when you launch the IDE.
Workaround: Change the system settings in Security and Privacy to prevent the dialog box from appearing when you launch the IDE.
When you switch between a device and a simulator, you must click Run instead of Build the first time after the switch.PR: 296376 JI: 393904
If your application requires permissions and you launch it from the QNX Momentics IDE, you must promptly accept the permissions on the device or the launch might time out.PR: 276767 JI: 402278
In a Windows environment, uninstalling the IDE does not remove any SDKs installed using the update manager.
Workaround: Manually remove the SDKs from the installation directory.
If you rename an existing project, the IDE does not prevent you from using special characters, spaces, or other invalid naming conventions.
Workaround: To prevent issues, you should avoid using special characters, spaces, and names that are shorter than 3 characters or longer than 25 characters.
If you update the IP address of a BlackBerry Target and click OK without clicking Apply first, the IDE gives an error that it can't connect to the target. However, the IDE does connect.
Workaround: After updating the IP address, click Apply before clicking OK.
The locked SDKs in the Update Native SDK wizard may not accurately reflect the SDKs you are using. Use care when uninstalling SDKs to ensure that you don't uninstall an SDK that you want to continue using.PR: 258694 JI: 393837
In a Linux environment, if you run the update manager and do not choose the options to switch to the newest SDK or to update the IDE, after the upgrade, the newest SDK is used by default.
Workaround: When you run the update manager, choose the option to update the IDE.
Cancelling the BAR file signing process deletes a previously signed BAR file.
Workaround: Increment the app version before signing the BAR file for the second time.
Postmortem debug is not available for shared libraries. The error message, "'Asynchronous viewer input update' has encountered a problem. An internal error has occurred." is displayed.PR: 231389 JI: 393795
On Windows, using blackberry-deploy from the command line results in the error "Cannot connect: Permission denied: connect. Please check IP address settings for the target. Try to ping the target."
Workaround: Before you run blackberry-deploy from the command line, execute bbndk-env.bat, which sets the environment variables properly.
Using GNU debugger, your debug session may break with an internal-error (for example, handle_inferior_event).PR: 206368 JI: 393773
If you debug an application with Windows XP, you may receive an error stating there was an "InvocationTargetException".
Workaround: Install the Microsoft Visual C++ 2008 Redistributable Package (x86).
When debugging an OpenGL 2.0 project, the debugger may skip some breakpoints.PR: 195895 JI: 393766
If you try to launch an application in debug mode that is already running on the device, the QNX Momentics IDE may consume 100% of your CPU.
Workaround: Close the application on the device before launching it again.
When setting a project-specific SDK, the settings will only take effect the second time you build your project.PR: 157697 JI: 382833
A class containing a pure virtual function using variable arguments cannot be inherited virtually. The following error is generated: "generic trunk code fails for method 'virtual void Log::Logger::Debug(const char*, ...)' which uses '...'".PR: 140310 JI: 393746
When you create a project with a name that begins with a numeric value, you will see the following error: "Package ID is invalid". Project names cannot start with a numeric value and must start with a letter from a-z or A-Z.PR: 121283 JI: -
During debug sessions, watchpoints are not supported.PR: 119766 JI: 393738
If you launch Run Config and enable the Code Coverage tool, when you check Code Coverage Sessions, there is no coverage of shared and static libraries.PR: 117556 JI: 382703
While debugging the "GoodCitizen" sample project using the "Step Into" function, the debugger doesn't step into the function handle_events(). The debugger jumps directly to the function update() and steps into that function.PR: 114742 JI: 393718
Do not launch your application with the Application Profiler enabled in debug mode. This might cause the IDE to stop responding.PR: 114071 JI: 382690
During initialization, the MSYS.dll provided with the Native SDK will try to map network shares. If they are not available, then it will take as long as the network access timeout for each such mapped share for MSYS to start. This can lead to build times being slower if MSYS based utilities are used.PR: 111911 JI: 393715
To use the breakpoint command GNU Debugger (GDB) Command Action, you need to switch your debug framework to CDI. Click Run > Debug Configurations. Select your application, and on the Main tab, click Select Other at the bottom of the page. Select CDI Debugging Framework (Traditional) Launcher, and click OK.PR: 111197 JI: 382684
The Native SDK ships static libraries for most of the libraries of the platform. However, we recommend using shared libraries where possible to reduce your application footprint and to take advantage of bug fixes in the platform.PR: 77220 JI: 393694
If you use the Application Profiler with the Sampling method on a target, all threads must be bound to CPU 0 because the Application Profiler only checks samples for CPU 0.
PR: - JI: -
On occasion, when you are running the Setup Wizard for the first time either directly from the Games app or using a 3rd party game, when you click the Let’s Play button on the last page of the wizard, the Games app might close unexpectedly. This does not affect the Setup, and the Games app or the 3rd party game works normally when started again.PR: - JI: 469817
You can't set a profile picture on the edit profile page of the Games app.