Developer Resources
Technical Articles

QNX Technical Articles

QNX Software Center 2.0: Release Notes

Date of this edition: January 22nd, 2024

Note: Changes to these notes since October 18, 2022 are highlighted below with this icon: New:

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:

  1. Go to the QNX website, www.qnx.com, and log in to your myQNX account.
  2. Select the Developers tab at the top of the page and click the QNX Software Center link.
  3. Scroll down the page and click any link for See Installation/Release notes.


What's new in this product?

The QNX Software Center 2.0 includes following updates:

  • Address some security vulnerabilities in OpenJDK and in other 3rd party code.
  • Continue improvement of the QNX Software Center Admin and Client portals.
  • Continue support for SDP 7.0 and SDP 7.1.
  • Ensure performance maintenance and security updates.
  • Enhance user experience.

New product features

  • We've introduced a concept of a release to make administration and testing convenient. In the QNX Software Center, a release is a logical group of packages that are published to a specific folder. Three new fields are introduced with it:
    • Release
    • Release Folder
    • Published
    It is available in the user interface. For details, see the User's Guide.
  • We've improvised the Group By action. It is now a dropdown action option under the top level for Updates, Available, Installed and All tabs. For details, see the "Group By" chapter in the User's Guide.

Deprecation of macOS Host support:

  • The QNX Software Centre 2.0 isn't supported on macOS host environments.
    BlackBerry QNX recommends that you continue using QSC 1.7 if you use a macOS host environment.

Known issues

  • In both Ubuntu 22 and RHEL8, the Desktop QSC GUI shows settings/Java icon instead of QSC icon on the Favorites panel. (Ref# J2915495)

  • When you go to the End User License Agreement section, the reference (link for a native browser) for the license agreement is not present. There is only text: 'The content of this package is licensed under the QNX® DEVELOPMENT LICENSE AGREEMENT'. (Ref# J2697781)
    Workaround: To view the agreement:

    1. Go to the Installation tab.
    2. Select the QNX® Software Development Platform.
    3. Select the End User License Agreement.
  • An error message, 'No valid QNX license keys found' is displayed when a development seat license is not activated on the host. (Ref# J2923341)
    Workaround: Activate any of the assigned licenses or proceed with the baseline installation which activates the license automatically.
  • When you're prompted to update the QNX Software Center, a popup window appears with the text 'Do you want to restart the application after the installation is complete'. If you click Yes, you may get an error message: 'The Software Center has stopped working' or the application may enter an infinite loop. (Ref# J2553359, 2811660, 2895354)
    Workaround: Do not select the Restart Now option after an update. Instead, select No and restart manually after the update is complete. If you did click Restart Now, there are a few possible outcomes:

    • If the application crashes or exits without relaunching, you can work around it by ignoring it and restarting the QNX Software Center manually.
    • If the application enters an infinite restart loop, try to kill it with the task manager.
    • If nothing works, restart your computer and the QNX Software Center should update upon relaunching.
  • The QNX Software Center cant 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 Users Guide.

  • A patchset exported from an incomplete installation cannot be installed on its own. An incomplete installation is a result of selectively adding a few packages to an empty installation. (Ref# J2891406)
    Workaround: Such a patchset can only be installed on an existing installation. Instead, create a patchset from a full installation.

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

  • New: With QSC 2.0, when no baseline is installed, it's not possible to install a new baseline using a .qpkg patchset.
    Workarounds (select one):

    • Use a text-based patchset instead of a .qpkg patchset.
    • Use the command line to install the patchset.
    • After experiencing the error, retry using the QSC installation wizard.
    • Use the following procedure:
      1. Before installing the patchset, click Add Installation.
      2. Select a baseline.
      3. Follow the steps of the wizard.
      4. Click Cancel on the last page instead of Finish.
      5. Try the installation of the baseline again using the .qpkg patchset.

Technical support

For information about technical support for any QNX product, go to the Support area on our website: https://blackberry.qnx.com/en/support. You'll find a wide range of support options.