The following items are notable issues fixed between the release of Package Manager 21.0 and Package Manager 21.3, including additional patches and service packs. If you have an issue ID, you can search this list to validate that the issue has been fixed. This is not an exhaustive list of issues fixed in the current version of Package Manager.
|
Bug Number |
Legacy ID |
Description |
Details |
|---|---|---|---|
| 1240996 |
Dialog reporting internal error can appear after successfully installing individual packageAfter selecting Open on a package file (.nipkg) in Windows Explorer and installing a package, Package Manager might display an error dialog with the text "An internal error occurred. The PackageTransaction is currently in a Transaction." Workaround: Ignore the error dialog. |
Reported Version: Package Manager 20.6 Resolved Version: Package Manager 21.3 Added: May 4, 2021 |
|
| 1374463 |
A failure to update a feed during launch of Package Manager prevents subsequent feeds from updatingLaunching Package Manager and the top level path or uniform resource identifier (URI) for a feed is invalid in the feed pool, Package Manager displays the message, "Failed to update all feeds", with additional error information "The feed URI '<feed path>\Packages.gz' is invalid." When this error occurs, Package Manager skips updating subsequent configured feeds. Workaround: Correct the top level path or URI for the invalid feed, or remove the invalid feed from the feed pool. |
Reported Version: Package Manager 20.0 Resolved Version: Package Manager 21.3 Added: May 4, 2021 |
|
| 1512240 |
Package Manager slow to launch when disconnected from internetPackage Manager is slow to launch and appears to hang if connection timeout failures occur when Package Manager attempts to connect to URLs for configured feeds or to ni.com to populate the Browse Products tab. Workaround: There is currently no known workaround for this issue. |
Reported Version: Package Manager 20.7 Resolved Version: Package Manager 21.3 Added: N/A |
|
| 1284551 |
'Feed already in use' error message appears after opening and installing a package with Package ManagerOpening a package with Package Manager, such as double-clicking on a package in Explorer, that upgrades an installed package might fail with the error "The feed URI '<feed-uri>' is already in use. Choose a different URI for the feed." Workaround: If the package upgrade installed successfully, you can ignore the error message. |
Reported Version: Package Manager 20.6 Resolved Version: Package Manager 21.3 Added: N/A |
Installing some patches may require certain additional steps or considerations. Please refer to the following table for more information about patches for this release.
These patches currently do not have any special instructions.