What's new in Mobile Client 4.9.6
Upgraded Android SDK build-tools to 29.0.2 for integrating apps. Current Android SDK support level is SDK version 28 and later.
Resolved in Mobile Client 4.9.9
|MOB-647||Android||All||Corrected vulnerabilities identified via security scanning tools.|
|SPT-2243||iOS||All||Fixed an issue occurring when a web server closed a connection before sending all its data.|
|All||Fixed an issue where the Mobile Client was unable to fully establish an IKEv2 tunnel over IPv6 to the Blue Cedar Connect Gateway.|
|SPT-2261, SPT-2262||Android, iOS||All||Fixed a DNS issue occurring when reconnecting to the Connect Gateway.|
Resolved in Mobile Client 4.9.8
|MOB-835||Android||All||Corrected vulnerabilities identified via security scanning tools.|
Made improvements to relinking process. To take full advantage of the improvements, remove the app from devices, re-integrate the app, and re-deploy.
Note: This change may produce breaking errors in some apps.
Resolved in Mobile Client 4.9.7
|MOB-691||Android||All||Corrected vulnerabilities identified via security scanning tools.|
|SPT-2211||Android, iOS||Gateway||Changed handling of untrusted server certificates. Rather than allow the app user to proceed with an insecure session at launch and then later fail to reconnect, now the app cannot launch if the server certificates are untrusted.|
|SPT-2141||Android||All||Fixed an issue with apps integrated with the BlackBerry Accelerator using URLConnection. Such apps were not able to access content, but now the order of HTTP headers returned to the apps is consistent with other accelerators.|
Resolved in Mobile Client 4.9.6
|MOB-690||Android||All||Corrected vulnerabilities identified via security scanning tools.|
|SPT-2226||Android||All||Fixed an issue with apps hanging/crashing after authentication.|
|MOB-737||Cloud Platform||All||Fixed an issue where apps with names containing white space failed integration.|
Resolved in Mobile Client 4.9.5
Fixed an issue with certificate authentication when certificate-only authentication is enabled on the Blue Cedar Connect Gateway: the client would not present the certificate it received from enrollment.
Resolved in Mobile Client 4.9.4
|SPT-2113, SPT-2167||Android 10|
Network requests made through Secure Web Stack now correctly use CA certificates specified for augmented trust on Android 10. This includes requests made via WebView, URLConnection, OkHttp, and Apache HTTP Client.
Note that other trust verifications on Android 10 (such as direct calls to X509TrustManager) will not use the additional certificates at this time.
|SPT-2171||Android||Fixed app crashing on launch by increasing interception to properly align with app behavior and all supported accelerators.|
|SPT-2175||Android||Fixed the way the client handles illegal Android resource names starting with "$$".|
|SPT-2204||iOS, Android||Addressed an issue preventing React Native local storage files from being encrypted.|
Resolved in Mobile Client 4.9.3
|SPT-2196, SPT-2198||iOS||Fixed an issue that prevented app group permissions from validating correctly.|
|SPT-2109||Android||Fixed an issue where HTML5 apps could not store or retrieve data from local storage when the Data at Rest policy is enabled.|
|SPT-2180||Android||Fixed an issue where incorrect URLs could be delivered to WebViewClient following redirects, resulting in undesirable behavior.|
|SPT-2133||Android||Fixed an issue with unresponsive web views, related to a redirect issue with Secure Web Stack.|
|SPT-2147||iOS||Fixed a crash that can occur when calling functions from memory address.|
Fixed handling of relative redirect URLs for BlackBerry-integrated apps that use WebView.
|SPT-2141||Android||Fixed inconsistent order of HTTP headers returned to BlackBerry-integrated apps using URLConnection.|
|SPT-2122||Android||Fixed support library conflict between classes added for BlackBerry integration and dex-merged versions that were in the original app.|
Resolved in Mobile Client 4.9.2
|SPT-2162||Android||Fixed an integration failure where the client was adding OkHttp during integration when the app already had a copy. No longer adding OkHttp to support HttpUrlConnection traffic.|
Fixed apps integrated with the Blue Cedar Accelerator for BlackBerry that were crashing due to missing permissions.
BlackBerry requires these permissions for an app to run properly on all devices. If these permissions are not present in apps before integration, BlackBerry adds them during integration time. If you use maxSDKVersion for any of these permissions, Android removes the permission during installation on devices with an operating system above the maxSDKVersion: this removal makes the app crash. This fix removes maxSDKVersion for these permissions during integration:
|SPT-2163||Android||Fixed data migration failure after a PIN reset.|
|SPT-2056||iOS||Fixed an issue where body data was being incorrectly dropped for certain requests with relative URLs.|
Resolved in Mobile Client 4.9.1
|MOB-544||Android||When updating a BlackBerry app's package name to match its GDApplicationID, the package name in the resources.arsc bundle is also updated. This resolves an issue uploading integrated apps to BlackBerry UEM servers running 12.11.|
|SPT-2160||iOS||Updated SQLite handling to prevent crashes with Blue Cedar Accelerator for BlackBerry.|
|SPT-2141||Android||Added ability to handle Xamarin WebViews, including Xamarin Forms, with the Blue Cedar Accelerator for BlackBerry.|
|MOB-572||Android||Made several improvements for apps integrated with the Blue Cedar Accelerator for BlackBerry, particularly around HTTP redirect handling and cookies.|
|MOB-460||Android||Improved support for AndroidX-based Room databases.|
|MOB-431||Android||Allow external code signing to be used without uploading Android signing information to the Blue Cedar Platform.|
|MOB-434||iOS||Allow external code signing to be used without uploading iOS signing information to the Blue Cedar Platform.|
Browser support: The Blue Cedar Platform supports Chrome and Firefox browsers. Safari, Edge, and Internet Explorer are not currently supported.
Limitations with integrating the BlackBerry Dynamics SDK with the Blue Cedar Accelerator for BlackBerry include:
- ClipboardManager/drag and drop: The ClipboardManager BlackBerry Dynamics API is not integrated into apps since there is no 1:1 mapping to Android's ClipboardManager. Apps usually do not call the ClipboardManager directly to perform drag and drop operations. (BCP-1638, Android)
- BlackBerry Secure Network/Transport: Turning on/off Secure Network/Transport from the Blue Cedar Platform does not affect the integration. (BCP-704)
- iPhone ARMv7 devices: BlackBerry Dynamics does not integrate into apps built for ARM v7 Apple devices (32-bit CPUs) such as iPhone 5 or 5c. (BCP-1523, iOS)
- Secure file transfer: There is currently no support for functionality to enable or disable file sharing between apps integrated with BlackBerry Dynamics and apps not integrated with BlackBerry Dynamics. (BCP-2001)
- Xamarin certificates: Xamarin HTTP traffic is not sent to the BlackBerry HTTP client. (BCP-2719)
Documentation and technical support
This release includes online documentation. To access this documentation, see.