I am growing on macOS and utilizing Visible Studio Code (VS Code) for debugging functions. After I run or debug my code, VS Code usually creates non permanent executable binaries in my venture’s debug output listing.
macOS robotically applies the com.apple.quarantine prolonged attribute to those newly created binaries, possible as a result of they’re being generated by an software which may have been downloaded. This ends in the same old macOS safety immediate (“is an app downloaded from the web…”) the primary time I attempt to run or debug them after a recent construct.
I’m conscious that I can manually take away this attribute utilizing the terminal command:
xattr -d com.apple.quarantine /path/to/my/debug/binary
As seen on this current Stack Alternate reply: https://apple.stackexchange.com/a/436677/434175
Nonetheless, I am searching for a approach to automate this course of inside VS Code or whitelisting in some apple settings in order that I haven’t got to manually run this command each time a brand new debug binary is created inside these venture directories.
My questions are:
- Does VS Code have any built-in settings or options that may robotically deal with the elimination of the
com.apple.quarantineattribute for non permanent debug binaries it generates on macOS? - Are there any particular VS Code duties or construct configurations that I can set as much as run a command (just like the
xattrcommand) robotically after the construct course of for debug targets? - Are there any related VS Code extensions which may present this performance?
- Are there every other really helpful approaches throughout the VS Code ecosystem to streamline the debugging expertise on macOS and keep away from these quarantine prompts for domestically constructed binaries?
I am hoping to discover a resolution that integrates properly with the macOS VS Code workflow and avoids the necessity for guide intervention every time I construct and debug.
