Cascades - Fixed in this release
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 & 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.
BBM Social platform
Images that use transparency might not appear correctly in the user's list of BBM applications.
Core - Fixed in this release
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_EBADFerror message: Failed to open screencapture control PPS object
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.
JI: 380460 JI: 377399
An unbound invocation query may have caused some invocation targets to appear twice in the menu. (See also 345183)
On Mac OS, the simulator controller could not be launched from the simulator installation location.
Back to Top