Maps

We've updated the Maps API to include new classes and new functionality for geographic shapes (GeoShape and GeoPolygon) and lines (GeoPolyline and Polyline). You can use MapView to display a map that the user can interact with. You can also display location-specific information including points of interest and locations using GeoLocation. You can drop pins for points of interest and show bubbles to present more details about a point of interest using Marker.

• geolocation_event_get_accuracy_rotation_angle()
• geolocation_event_get_accuracy_semi_major_axis()
• geolocation_event_get_accuracy_semi_minor_axis()
• geolocation_event_get_geoid_height()
• geolocation_event_get_hdop()
• geolocation_event_get_pdop()
• geolocation_event_get_propagated()
• geolocation_event_get_satellite_is_almanac_decoded()
• geolocation_event_get_status_accuracy()
• geolocation_event_get_status_active_request()
• geolocation_event_get_status_background()
• geolocation_event_get_status_passive()
• geolocation_event_get_status_period()
• geolocation_event_get_status_response_time()
• geolocation_event_get_vdop()
• geolocation_event_get_vertical_speed()
• geolocation_event_is_accuracy_rotation_angle_valid()
• geolocation_event_is_accuracy_semi_major_axis_valid()

• geolocation_event_is_accuracy_semi_minor_axis_valid()
• geolocation_event_is_geoid_height_valid()
• geolocation_event_is_hdop_valid()
• geolocation_event_is_latitude_valid()
• geolocation_event_is_longitude_valid()
• geolocation_event_is_pdop_valid()
• geolocation_event_is_propagated_valid()
• geolocation_event_is_status_accuracy_valid()
• geolocation_event_is_status_active_request_valid()
• geolocation_event_is_status_background_valid()
• geolocation_event_is_status_passive_valid()
• geolocation_event_is_status_period_valid()
• geolocation_event_is_status_response_time_valid()
• geolocation_event_is_vdop_valid()
• geolocation_event_is_vertical_speed_valid()
• geolocation_request_status()
• geolocation_set_passive()
• geolocation_set_stationary()

• NETSTATUS_INTERFACE_TYPE_P2P (netstatus_interface_type_t)
• netstatus_info_t
• netstatus_event_get_info()
• netstatus_free_info()
• netstatus_get_info()
• netstatus_info_get_availability()
• netstatus_info_get_default_gateway()
• netstatus_info_get_default_interface()
• netstatus_info_get_default_ip4_interface()
• netstatus_info_get_default_ip6_interface()
• netstatus_info_get_ftp_proxy_host()
• netstatus_info_get_ftp_proxy_port()
• netstatus_info_get_http_proxy_host()
• netstatus_info_get_http_proxy_login_required()
• netstatus_info_get_http_proxy_port()
• netstatus_info_get_https_proxy_host()
• netstatus_info_get_https_proxy_port()
• netstatus_info_get_ip4_status()

• netstatus_info_get_ip6_status()
• netstatus_info_get_ip_status()
• netstatus_info_get_name_server()
• netstatus_info_get_num_default_gateways()
• netstatus_info_get_num_name_servers()
• netstatus_info_get_num_search_domains()
• netstatus_info_get_search_domain()
• netstatus_info_get_search_domains()
• netstatus_interface_get_http_proxy_host()
• netstatus_interface_get_http_proxy_login_required()
• netstatus_interface_get_http_proxy_port()
• netstatus_interface_get_ip4_status()
• netstatus_interface_get_ip_destination_address()
• netstatus_interface_get_mtu()
• netstatus_interface_get_num_search_domains()
• netstatus_interface_get_parent_interface()
• netstatus_interface_get_search_domain()

Cascades upgrade guide

We also have an upgrade guide available that can help you transition your apps to the 10.2 Gold release version for BlackBerry 10. Check out the upgrade guide here.

Behavior changes

Payment Service

The Payment Service has been updated to use sheets (instead of dialog boxes) for the purchase flow of digital goods and applications. To minimize the number of requests to the Payment Service, requestExistingPurchases(false) now requests existing purchases from the BlackBerry World client cache. If the client cache is invalid, existing purchases are retrieved from the BlackBerry World server.

For more information about using the Payment Service, see Payment Service.

Sheet behaviour

Cards and sheets now slide in from the right side of the screen. For more information, see the UI guidelines for Cards and Sheets.

For more information about creating cards, see Cards.

Bluetooth

If your app makes calls to QBluetoothLocalDevice::address(), you must enable the read_device_identifying_information permission in your app’s bar-descriptor.xml file. The requirement for this permission will be enforced in a future release. When it is enforced, any calls to QBluetoothLocalDevice::address() without the required permission enabled will fail with an error message.

For more information about setting permissions, see App permissions.

Changes to signing your apps

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.

BlackBerry Platform Services Library

navigator.h

Deprecated navigator_open_file(). Use the invocation framework APIs from navigator_invoke.h instead.

Bluetooth Library

btgatt.h

Deprecated the following definitions:

• GATT_TIME_INFINITY
• GATT_UUID_STRING_LENGTH
• GATT_CLIENT_CHAR_CFG_UUID
• GATT_CHARACTERISTIC_PROP_BROADCAST
• GATT_CHARACTERISTIC_PROP_READ
• GATT_CHARACTERISTIC_PROP_WRITE_NORESP
• GATT_CHARACTERISTIC_PROP_WRITE
• GATT_CHARACTERISTIC_PROP_NOTIFY
• GATT_CHARACTERISTIC_PROP_INDICATE
• GATT_CHARACTERISTIC_PROP_WRITE_SIGNED
• GATT_CHARACTERISTIC_PROP_EXT_PROP

btdevice.h

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.

For more information on the Bluetooth Library, see the API reference.

Camera Library

camera_api.h

The following functions and data type were incorrectly included in the header file and should not be used.

• camera_get_supported_video_vf_modes()
• camera_get_video_vf_mode()
• camera_set_video_vf_mode()
• camera_video_vf_modes_t

For more information on the Camera Library, see the API reference.

Geofencing Library

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:

• geomonitor_monitoring_mode_t
• geomonitor_region_get_monitoring_mode()
• geomonitor_region_get_notification_invoke_target()
• geomonitor_region_get_notification_message()
• geomonitor_region_get_stop_monitoring_event()
• geomonitor_region_set_monitoring_mode()
• geomonitor_region_set_notification_invoke_target()
• geomonitor_region_set_notification_message()
• geomonitor_region_set_stop_monitoring_event()

For more information on the Geofencing Library, see the API reference.

Headless apps

We've made some changes and additions to the documentation for headless apps. There's now more information about notifications and interprocess communication (IPC), as well as a few more sample apps. We've also restructured the step-by-step approach for creating a headless app to be more complete and easier to follow.

For more information on headless apps, see documentation.

Scoreloop SDK

scui_client.h

Deprecated the following functions:

• SCUI_Client_New()
• SCUI_Client_ShowFavoriteGamesView()

For more information on the Scoreloop SDK, see the documentation.

BBM Social platform

Images that use transparency might not appear correctly in the user's list of BBM applications.

Camera

The acl_to_text() and acl_from_text() functions were not safe to use in multithreaded programs.

Cascades platform APIs

When using the SMS transport API, you could not register other app's headless target ID.

When using the SMS service you could not register apps with the service.

The WiFiDirect networkInterfaceName() and networkSsid() functions were returning empty strings instead of the network interface name or the network SSID as expected.

When a headless app's UI was registered with a port, an SMS trigger for the headless app was bringing a UI into the foreground.

When you had an app with paid digital items listed on the BlackBerry World storefront, each time you called the requestPrice() function, a response was required before sending the next request. Calling requestPrice() multiple times without waiting for a response would result in a PriceReply error.

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.

If your app was in the enterprise space, the sms trigger did not invoke the app because the default is to invoke the app in the personal perimeter. Since the app is not there, nothing was invoked.

Applications installed in the enterprise perimeter could not be invoked by the Geomonitor service. Invocation was defaulting to the personal perimeter and not enterprise.

If you had a GeoLocation with a radius greater than 0, only the marker was rendered, not the radius circle.

If you didn't register your signing key and your PlayBook debug token with the same clientID, an error would be thrown when trying to link your BlackBerry ID account with a Signing Authority account.

Headless apps didn't receive SMS triggers from the invocation framework.

If you were running a headless app, the bb.action.system.STARTED invoke trigger was not sent after a device restart.

When you had an app with paid digital items listed on the BlackBerry World storefront and called the requestPrice() function, both a valid SKU value and a valid ID number were required in order to retrieve the price. However, the documentation states that only one of the ID or SKU was required in order to retrieve the price.

Components that derive from CustomControl did not display accessibility warnings correctly.

Invoked headless apps were displaying an incorrect StartUpMode. The value is set to ApplicationStartupMode.

C++ Invocation Framework and Menu Service did not have an enum type for Headless Application.

Headless apps can display UI messages.

Headless apps couldn't invoke services using the invocation framework.

Headless apps sometimes terminated due to an app connection timeout.

If you peeked into another window, which brings up the previous and next cards, the application could at times crash.

When a mode change occured, the service only sent and updated by stating the new mode, and did not send an update regarding the new policies for other settings that had changed due to the cascading effect of the mode change.

Visually disabled items were getting highlighted when ListSelectionIndicator was set to highlight on SystemListDialog.

Compiling a project with an mkbuild in command prompt occasionally resulted in a BundleException and SWTException.

If you changed the card orientation several times, your app might crash.

The checkWord() and suggestion() functions of SpellChecker sometimes returned false with correctly spelled words due to timing out.

Sometimes the processStateChanged() signal from Application was not being emitted.

When you were using the BlackBerry 10 Simulator in Z10 mode, the isPhysicalKeyboardDevice() function returned true, even though it should have returned false.

The PaymentErrorCode class sometimes wouldn't work properly in QML, and cited an error at run-time.

When using the PurchaseReply class, the finished() signal didn't return true, even after the purchase was made and the onPurchaseFinished() slot function was run.

The ProcessState API documentation didn't contain enough information on the difference between background and stopping Type enumerations.

In the SpellChecker API, the checkWord() function sometimes returned true, even if the word was misspelled. Invoking word suggestions didn't return any results.

Using the Screenshot API, the capture() function didn't display a permission requirement message, and failed with the error citing permission denied.

When a DisplayInfo object was set to the primary display, then the display name was obtained, sometimes the display name returned as an empty string.

Headless apps have heap usage limit based on permissions set.

When you tried to pair using Bluetooth, there was a potential risk for out-of-band (OOB) pairing to fail.

When you tried to create a Bluetooth connection, there was a potential risk for a low energy (LE) connection to fail.

In the SdCardInfo class, the state() and activity() functions didn't return proper values when a valid SD card was inserted, instead an unknown state was returned.

The BarcodeDetectorVisuals class was missing an API reference. Also, the return value of detected() in the BarcodeDetector class was just void.

The API reference for resetEmoticonsEnabled() of the SystemCredentialsPrompt class said the function resets the main text of the dialog box to QString::null. However, the function actually reset the emoticonsEnabled property back to the default value of false.

An unbound invocation query may have caused some invocation targets to appear twice in the menu. This issue also relates to 7215861 and 7301535.

When an SMS URI was typed, "Call" was an option in the context menu.

When a parent app invoked a Camera card, then the parent app disabled the camera use, the camera was still usable.

If an application has an invoke filter containing an asterisk (*), the application failed to install, showing a failure 884.

If invocation requests were pending, sometimes peeking and closing a card didn't work.

Sometimes when signing a BAR file, the content of the manifest .mf file and your Invoke-Target-Filter URI was altered, and your application failed to deploy properly.

You could not build a project from the command line on a Mac.

Sometimes when you purchased non-consumable items more than once, no error message was displayed, even if the payment didn't go through.

If there are no list items in the SystemListDialog class, the confirmButton function couldn't be enabled.

The API documentation for the Application.pooling() signal needed improvement. The app needed to be closed to trigger the pooling feature and pooling() signal. In the pooling() slot function, the handler, or somewhere after the pooling() signal was emitted, the app must call poolingCompleted(). If not, the app would be terminated in the normal way. In order to properly have pooling working, the app must have been deployed using the 'BlackBerry-deploy' command line program. Pooling would not work if you ran your app from the Momentics IDE for BlackBerry using the 'Run as' option.

When a DisplayInfo object was set to the primary display, then the display name was obtained, sometimes the display name didn't appear as expected.

When you used the HardwareInfo class to query for device information, the modelName() function returned the incorrect model name.

The API documentation for MenuItemInvokeParams.fileTransferMode() states that the file transfer mode will be applied if the scheme of the URI is "file:///". It also notes that the third forward slash represents the file path.

Sometimes when texting two numbers separated by a comma, the message was only sent to the first number.

Cascades Exporter plug-in for Adobe Photoshop

Using Cascades Exporter with Windows 8 and CS6 may have failed when exporting text layers.

Active Frames

The size of Active Frames was 310 x 396 for devices with a 720 x 1280 screen resolution. Now, for devices with this screen resolution, the size of Active Frames is 319 x 437. It was recommended that you create assets and text for Active Frames that support the 319 x 437 size. This may have caused your Active Frame to look distorted when developing for the 10.2.0.1443 release and earlier but it will now appear as expected.

BlackBerry Platform Services

Using the Screen capture API, the function screencapture_grab() failed with the error message:
error code 9 - CAMERA_EBADF
error message: Failed to open screencapture control PPS object

Headless apps

When you implemented a headless app, you could invoke notification dialogs using the Notification dialog functions of the Dialog API. Global dialogs were not encouraged as they were disruptive to the user experience.

If your app was in the enterprise perimeter, the sms trigger did not invoke the app because the default was to invoke the app in the personal perimeter. Since the app was not there, nothing got invoked.

Applications installed in the enterprise perimeter couldn't be invoked by the Geomonitor service. Invocation defaulted to the personal perimeter and not enterprise.

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.

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.

Headless apps were erroneously able to post windows, window groups, and dialog requests, which made them non-headless and display a UI.

When a headless app was invoked, the ApplicationStartUpMode was erroneously listed as LaunchApplication.

You could not invoke a service from a headless app.

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.

Invocation framework

An unbound invocation query may have caused some invocation targets to appear twice in the menu. (See also 345183)

Simulator

On Mac OS, the simulator controller could not be launched from the simulator installation location.

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.

QRC-based resources

If you are using QRC to improve performance in your apps, the new asset selection tool may affect your apps. If asset selection is used, an index file is generated automatically. However, this index file does not include contents that are only included in the QRC binary file. Instead, it lists only the files that reside in the assets directory in your project.

Workaround: Place a copy of QRC-compiled assets in your assets directory. The tool will then include these assets in the index file. When the device loads the app, the appropriate files in the binary are still used and the app continues to benefit from the performance gain of QRC.

Viewers in the invocation framework

Using the invocation framework, viewer-related classes (for example, InvokeViewerMessage and InvokeViewerRequest) and functions have been deprecated. The viewer-related classes and functions have been replaced by Card classes and functions. For more information on the Cards API, see the Cards documentation.

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.

FreeType

Applications using FreeType must add the following include path: $QNX_TARGET/usr/include/freetype2

Multimedia

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.

OpenAL

• 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.

OpenSSL

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().

Payment Service

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.

Scoreloop SDK

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

BBM Social Platform

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. This issue relates to 6118318.
Workaround: Restart the app if permissions have been modified.

Cascades Exporter plug-in for Adobe Photoshop

When using Cascades Exporter with an installation of Adobe Photoshop that uses French as the default language, a "Problem null" dialog might be displayed when you export a project, indicating that the export process fails.

Cascades platform APIs

When you're using a MapView, no useful information is displayed in a location caption dialog for the radius of a Geolocation, radius of a GeoDeviceLocation, a GeoPolygon, or GeoPolyline on that MapView. Subsequently, you cannot interact with a polygon, line, or radius circle.

Opening a large number of cards can cause the device to become unresponsive.

The networkOwnerIpAddress() and networkOwnerHardwareAddress() of WiFiDirect return empty strings.

Cascades maintains the visible and opacity properties of an ActivityIndicator. An ActivityIndicator becomes visible (opacity == 1) when it is running, and it is not visible (opacity == 0) when it is stopped. As a result, you should not read or set the visible and opacity properties of an ActivityIndicator. If you read or set the visible or opacity properties, it can cause unexpected results in your app.

GeoPolylines and GeoPolygons don't render if they cross 0, 180, or -180 degrees longitude or latitude.

Dotted and dashed edge styles don't render when you're using GeoDeviceLocation.

Dotted and dashed edge styles don't render when you're using GeoPolygon.

If you're using a GeoPolygon, inner boundaries don't render.

Generating static image maps with MapImageGenerator takes longer than intended.

Sometimes when editing JavaScript, code completion displays no proposals when there are proposals to display, including on console functions (such as the console.debug() function) or math functions (such as the Math.sin() function). The functions still work at runtime though.

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.

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. This issue relates to 6118318.
Workaround: Restart the app if permissions have been modified.

Classes that inherit DataModel, such as GroupDataModel, QListDataModel, and XmlDataModel, are missing some description information for implemented superclass functions, such as childCount(), hasChildren(), type(), and data().

An InvokeTargetFilter allows you to set the MIME type as '*' and register the filter, even if the filter is restricted.

If you call the InvokeUpdateTargetFiltersRequest.updateTargetFilters() function, a finished() signal is not emitted.

An established TCP connection over the cellular network interface fails when Wi-Fi is enabled on a device that is initially connected to a mobile network with Wi-Fi disabled.

On the BlackBerry 10 Device Simulator, if you start the controller from the installation folder and connect it to the simulator, then launch an app, you may not be able to switch the charging state to "charging."

There is missing documentation on QtNfcSubset classes including some enumerations and constructors in QNdefRecord, QNdefMessage, QNdefNfcSmartPosterRecord, QNdefNfcTextRecord, and QNdefNfcUriRecord.

When you set a URL property for a QML object, file paths are case-sensitive when they should be case-insensitive. For example, “FILE:app/native/assets/contacts.json” and “file:app/native/assets/contacts.json” should be treated the same, but are not. Also, a URL that’s defined in QML may result in a URL that has part of the path duplicated.

Progress toasts sometimes time out incorrectly when show() or exec() is called repeatedly.

When you add a custom URI to an InvokeTargetFilter and then retrieve the list of custom attributes, the size of the custom attribute list is reported as 0. The documentation does not specify that the returned size will be 0.

On the BlackBerry 10 Device Simulator, if you connect the windowGroupInvisible() and processStateChanged() signals and then minimize the app, neither signal is emitted.

InvokeRequest.setMetaData() doesn't work correctly if a QByteArray as part of the QVariantMap is passed in.

When using cards in an app that is run on the BlackBerry 10 Device Simulator, rotating the simulator may cause the UI to become distorted.

BBM Social Platform

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.

Camera

The acl_to_text() and acl_from_text() functions aren’t safe to use in multithreaded programs.

Documentation

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.

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.

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.

In the Security Builder Crypto Library documentation, the functions described for huecpvs.h and huecspeke.h are not available.

In the Camera API Library offline documentation, the following functions and data type should not have been included:

• camera_get_supported_video_vf_modes()
• camera_get_video_vf_mode()
• camera_set_video_vf_mode()
• camera_video_vf_modes_t

Headless applications

When using the Headless template, if the headless app project name is greater than 18 characters, the name of the generated entry point will exceed its maximum 25 character limit and create an error. If you want a project name that is longer than 18 characters, you need to rename the entry point of your service.

Currently, the category type for headless apps is incorrectly returned as "service". In the future, the correct type will be returned.

Installation

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.

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.

You might get a warning after uninstalling the Native SDK that some directories couldn't be removed. This can be ignored.

When you perform a software update, you must accept the security warning about installing unsigned software, and continue the installation.

Invocation framework

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.

OpenAL

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.

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.

Scoreloop SDK

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.

You can't set a profile picture on the edit profile page of the Games app.