OK. I will try to figure out how to use the C API. Display problem with the documentation -> FB9956926. If you use Google Chrome, it's a bit better.

I would just use the - (pid_t)pid private API if I had to get this value insecurely.

Thanks for the info. I don't remember where I saw this but indeed, there seems to be some checks with paths such as /System/, /Library/Apple/, /usr/bin, and bundle identifiers such as com.apple.* , Motion,… The issue with the com.apple.* pattern is that when Xcode crashes (yes, it happens), you end up with something incorrect where the Xcode binary and its linked embedded frameworks are not considered user code but its embedded Swift Libraries are…

This may be related to the sandboxing of Installer Plugins. It might be preferable to only disable the Continue button if the conditions are not met and invite the user to quit the application. Side note: The issue when you check requirements through an Installer Plugin is that these requirements will not be checked when the installation is run from the command line or through a deployment solution (b/c the Plugin will not be loaded). So this would end up in the erroneous installations you mentioned.