LabVIEW get volume has unexpected results [OSX]

[sth]

This is a weird interaction between LabVIEW and the new apfs file system with the tight security for newer versions of MacOS.  I used to use the LV application as the designation of the root volume and then put all my data and VIs in a shared folder for multiple users to work with.  This has worked for many iterations of LV and MacOS.

However, with the newer versions of MacOS, parts of the OS are put on different logical volumes which all share the same physical volume and free space.  To the user these look like they are all on the same location in the file structure such that /Applications is one volume where the National Instruments Folder goes but is actually the volume mounted at /System/Volumes/Data/Applications

There is also a separate volume for the Safari Web Browser and the /System/Applications which are not writeable for security purposes but appear to the user as /Applications.

It would be helpful if the getVolumeInfo primitive would return the apparent logical volume rather than one of various other options.

[sth]

On further investigation it seems to only happen in built applications.....

[Christina_R]

Could you please provide a VI that demonstrates the issue (when built into an application)?

[sth]

I am trying to, I have had the a couple of instances where data was being written to /Applications/Users/Shared/Data instead of /Users/Shared/Data and I will try to track down which apps and which OS this happened on.  They all try to start with Get Volume path (left over when the network name was part of the path pre OS X).