Is there a way to programmatically allow (trust) the compiler plugin to run from the command line?

[kishikawakatsumi]

When I try to run code that uses a community-created macro library on CI (Xcode Cloud), it fails because I cannot interact with the compiler plugin to allow its use.

The error message looks like this:

Target 'PowerAssertPlugin' must be enabled before it can be used.

I have tried setting the following UserDefaults based on the following post but no effect.

defaults write com.apple.dt.Xcode IDESkipPackagePluginFingerprintValidation -bool YES

Telling Xcode 14 beta 4 to trust build tool plugins programatically

In Xcode Cloud you can use custom build scripts (ci_post_clone.sh) to set the following user default: defaults write com.apple.dt.Xcode IDESkipPackagePluginFingerprintValidatation -bool YES This will have the same effect as passing -skipPackagePluginValidation.

[owenv (Owen Voorhees)]

You can use defaults write com.apple.dt.Xcode IDESkipMacroFingerprintValidation -bool YES in a script to skip validation of macros from remote dependencies (the equivalent xcodebuild command line flag is -skipMacroValidation).

[kishikawakatsumi]

It works! Thank you so much.

[vladyslavsosiuk]

Is there a way to explicitly set a specific list of macros that are validated instead of skipping validation for all of them? as the documentation of the option suggests this is a security risk:

-skipMacroValidation Skip validation of macros (this can be a security risk if they are not from trusted sources)