QNX Technical Articles
QNX® Software Center 2.0.3: Release Notes
Date of this edition: September 11th, 2024
The QNX Software Center enables you to download, install, and manage the QNX Software Development Platform (SDP) 7.x or greater and related products. You can install the QNX Software Center on the following development hosts:
- Microsoft Windows 10 and Windows 11 Pro 64-bit
- Linux Ubuntu 22.04 Workstation LTS 64-bit or RedHat Enterprise Linux Version 8.0. (The QNX Software Center doesn't run on ARM-based Linux hosts.)
In this document, you may see reference numbers associated with particular issues or changes. When corresponding with our support staff about a given issue, please quote the relevant reference number. The reference numbers can also help you track issues as they become fixed.
For the latest version of the QNX Software Center release notes:
- Go to the QNX website, www.qnx.com, and log in to your myQNX account.
- Select the Developers tab at the top of the page and click the QNX Software Center link.
- In the table of downloadable items, click the "QNX Software Center 2.0.3" entry for your development host OS.
- In the download page for the QSC package, click the Release Notes link from the Related Documents panel at the bottom.
Contents
What's new in this product?
The QNX Software Center 2.0.3 includes following updates:
Adjustments to package legal attributes
- Changed the legal and regulatory package reporting fields.
- Changed the name of the field Redistributable to Target. In addition, this field no longer appears in some of the default column views.
- Removed the field Support Provided.
- Removed the field Engagement Model.
- Legal attributes calculated on a file basis are now viewable at the level of the package.
- The Status column is no longer viewable at the level of the package, as it only applies on a per-file basis.
- Added the field Software bill of materials (SBOM) to the manifest reports fields as an optional field.
- Added the Runtime Component field, along with its reporting template.
Unmanaged installation in the CLI
- Added support for unmanaged installation in the CLI. When using unmanaged installation, QSC doesn't resolve dependencies or keep an installation record.
In addition, the dependency resolution and filter checking features aren't applicable. Only the following options are supported in the unmanaged mode:
-installPackage (-i)
-downloadPackage
-cleanInstall
-destination
- -listInstalled (only usable with -installPackage)
- The package is downloaded to the destination/downloads folder. You can remove this folder afterward, if you don't want to keep it.
Fixed issues
-
A patchset exported from an incomplete installation can now be installed on its own.
Exception: You still cannot install a patchset that was exported from an installation with no baseline. (Ref# J2891406)
-
The error message 'No valid QNX license keys found' is no longer displayed when a development seat license is not activated on the host. (Ref# J2923341)
-
Corrected the behavior with QSC 2.0 (without a baseline installation) where it wasn't possible to install a new baseline using a .qpkg patchset. (Ref# 2927499)
Known issues
-
When adding a package to an empty installation, the Download Only option is blocked (greyed out). (Ref# 2969930)
Workarounds (select one):
- Use the CLI.
- Install or Download the package using the QNX website, www.qnx.com by logging in to your myQNX account. Once logged-in, Select the Developers tab at the top of the page and click the product of choice.
-
The QNX Software Center can’t activate a license key if your workstation sits behind a SOCKS proxy or an authenticating HTTP proxy that uses anything other than basic authentication. (Ref# J2221051)
Workaround: Use a basic authentication proxy or perform manual product activation, as described in the QNX Software Center User’s Guide. -
If you have multiple licenses activated on more than one machine, you may be presented with a license compliance error. (Ref# J2876541)
Workaround: You can safely ignore this warning. -
If you install an experimental package and then deactivate Install experimental packages in the Installation Properties dialog box, the QNX Software Center does not let you install, uninstall, or repair any packages in the affected installation. (Ref# J2812561)
Workaround: If you've installed experimental packages, leave Install experimental packages enabled. -
The Proxy Connections window of the QNX Software Center displays settings for HTTP/HTTPS proxies and for SOCKS proxies, but only the HTTP/HTTPS settings are supported. (Ref# J2752710)
-
If you attempt to add an installation while another installation is in progress, the installation wizard may freeze. In addition, the installation in progress may not complete successfully. (Ref# J2644173, 2507085, 2222799, 2801650)
Workaround: Avoid adding an installation while another installation is in progress. -
If you uninstall the last package from an installation that isn’t a QNX SDP 7.* baseline installation, the installation isn't removed, even though it's now empty (i.e., the Installed tab shows no packages for the installation). (Ref# J2557464)
Workaround: To remove the installation itself, go to the Advanced tab and select Remove Installation. -
You can’t re-import an exported report if the report omits the NAME, BUILDID, and DIGESTSHA512 fields. (Ref# J2372364)
Workaround: Before exporting a report, make sure that, at a minimum, it contains these three fields. -
On Windows, if you uninstall the QNX Software Center while it is running or while any of its files are open in another program, the uninstaller does not remove the open files. However, it displays a report that it ran successfully. (Ref# J1684312)
Workaround: Remove the leftover files manually.
Technical support
To obtain technical support for any QNX product, visit the Support area on our website: https://blackberry.qnx.com/en/support. You'll find a wide range of support options.
For product experience and roadmap information, please contact QNX Product Management.