Application Builder bug when build spec name ends with ".lvlibp"

[bienieck]

I noticed that when the name of my build specification for a PPL ends with .lvlibp, the Application Builder fails to build it and does not clearly communicate the issue. For example, I have a simple library named LIB A.lvlib, the build specification is called LIB A.lvlibp, and the final artifact is also named LIB A.lvlibp. When building this specification, I receive an error, which I have pasted below. An additional indication of this issue is that in the preview, the artifact is displayed with the name LIB A.lvlibp.lvlibp. Could someone check if they experience a similar issue? I am using LabVIEW 2024 64-bit.

Click the link below to visit the Application Builder support page. Use the following information as a reference:

Error 1 occurred at Invoke Node in AB_PackedLibrary.lvclass:Open_Reference.vi->AB_Build.lvclass:Copy_Files_Core.vi->AB_Build.lvclass:Copy_Files.vi->AB_Build.lvclass:Build.vi->AB_PackedLibrary.lvclass:Build.vi->AB_Engine_Build.vi->AB_Build_Invoke.vi->AB_Build_Invoke.vi.ProxyCaller

Possible reason(s):

LabVIEW: (Hex 0x1) An input parameter is invalid. For example if the input is a path, the path might contain a character not allowed by the OS such as ? or @.

Method Name: Library:Open

[bienieck]

After conducting additional tests, I’m not convinced that the issue lies with the build specification name. The problem occurs in various situations, for example, when copying files or running more complex procedures in pre/post actions. Generally, I have the impression that the Application Builder is either caching something or not closing certain references. So far, the only solution to my various issues has been to delete the build specification and create it from scratch...

I would like to add that I previously submitted a service request for a similar issue, but at that time, the problem occurred when I tried to use an FGV to transfer information from pre to post actions. Now, there are other cases that are reproducible on my end but only up to a certain point. It seems that the reproducibility of the issue is temporary (until I change something in the project or test it on an entirely new project).

[raphschru]

It reminds me of this thread, where the editor tries to be smart by using a symbolic reference to the project name in the PPL name:

https://forums.ni.com/t5/LabVIEW/Project-name-affecting-PPL-qualified-name/m-p/4336906

Regards,

Raphaël.