This document contains the NI Package Builder known issues that were discovered before and since the release of NI Package Builder 20.1. Known issues are performance issues or technical bugs that NI has acknowledged exist within this version of the product.
Not every issue known to NI appears on this list; it is intended to show the most severe and common issues that you may encounter and provide workarounds when possible. Other technical issues that you may encounter could occur through normal product use or system compatibility issues. You may find more information on these issues in NI’s Product Documentation, Knowledgebase, or Community.
Bug Number |
Legacy ID |
Description |
Details |
---|---|---|---|
1105686 |
Version is Empty for a Solution Package Without a Display Version in the Add Dependencies DialogThe Add Dependencies dialog does not show the Version of a package in the Solution Packages tab if the solution package does not specify a display version. Workaround: There is currently no known workaround for this issue. |
Reported Version: NI Package Builder 20.0 Resolved Version: NI Package Builder 20.5 Added: N/A |
|
1108853 |
Building a Local Repository Doesn't Copy EULA PackagesPackage Builder does not include dependent NXG defined End User License Agreement (EULA) packages in a local repository. Workaround: Manually add the EULA to the local repository and use the "nipkg feed-add-pkg" command to update the feed to include the EULA. You can also building a package installer which will properly include the EULA package. |
Reported Version: NI Package Builder 19.6 Resolved Version: NI Package Builder 20.5 Added: N/A |
|
1047801 |
Renaming a Directory that Contains Hundreds of Files Causes SlowdownPackage Builder appears to hang when entering each character for a rename of a directory in the Editor Pane if the directory contains hundreds of files. Workaround: Temporarily move the files to a different directory location in the package, rename the directory, and move the files back to the renamed directory. |
Reported Version: NI Package Builder 20.0 Resolved Version: N/A Added: N/A |
|
1045471 |
Sequence File Included in Built Package Will not Execute if Override Packed Project Library step is Configured to Build PPL to a Higher DirectoryDeploying a TestStand sequence file that contains a LabVIEW Packed Project Library (PPL) Override step with a LabVIEW project that builds the PPL to a directory above the sequence file results in a step that cannot execute. Workaround: Configure the step to build the PPL in the directory of the sequence file, or rebuild the Override PPL after deploying the sequence file. |
Reported Version: NI Package Builder 20.0 Resolved Version: N/A Added: N/A |
|
1036386 |
Package Builder Appears Unresponsive when About Dialog is Hidden Behind ApplicationNI Package Builder appears unresponsive when the About dialog is hidden behind the Package Builder application when you click on the Package Builder in the taskbar before dismissing the About dialog. Workaround: Launch Windows Explorer and then immediately close it. |
Reported Version: NI Package Builder 20.0 Resolved Version: N/A Added: N/A |
|
1035363 |
Rerunning Discovery After Building a Previously Missing Packed Project Library Still Results in Warning 16086Adding a TestStand sequence file with a step that specifies a Packed Project Library (PPL) Override with a calling context project and the PPL is missing on disk will result in Warning 16086 "Discovery could not find the following dependency on disk". Rebuilding the PPL and rerunning discovery will still result in this warning another time even though the PPL is now on disk. Workaround: Perform discovery a third time for Package Builder to properly locate the PPL. |
Reported Version: NI Package Builder 20.0 Resolved Version: N/A Added: N/A |
|
1035159 |
Build Fails when Including an Override Packed Project Library Incompatible with the Active LabVIEW VersionBuilding a package fails during staging if an included Override Packed Project Library (PPL) for a sequence step is incompatible with the active version of LabVIEW, such as a 64-bit PPL and 32-bit LabVIEW. Workaround: There is currently no known workaround for this issue. |
Reported Version: NI Package Builder 20.0 Resolved Version: N/A Added: N/A |
|
987052 |
Warnings Cannot be Avoided when Opening a Solution that Contains TestStand Files on a Machine without TestStandPackage Builder reports a warning when opening a solution that contains TestStand files and TestStand is not installed. TestStand files do not appear in the Editor pane and therefore cannot be removed, causing the warnings to reappear on each subsequent opening of the solution. Workaround: There is currently no known workaround for this issue. |
Reported Version: NI Package Builder 20.0 Resolved Version: N/A Added: N/A |
Issues found in this section will not be listed in future known issues documents for this product.
There are currently no issues to list.
Explore Support Content and Product Documentation
Ask the NI Community
Request Support from an Engineer
A valid service agreement may be required, and support options vary by country