Skip to main content
Participant
September 16, 2025
Answered

macOS Security Update Blocks Photoshop Scripts from Running System Commands (app.system fails)

  • September 16, 2025
  • 2 replies
  • 155 views

Hello, Adobe Team. I am reporting a critical issue that prevents any Photoshop script from executing command-line processes on macOS using the app.system() command. This issue started recently after a long period of working perfectly. Environment: * Photoshop Version: [FILL IN YOUR VERSION, e.g., 25.9.1] * macOS Version: [FILL IN YOUR VERSION, e.g., Sonoma 14.5] Steps to Reproduce: 1. On a Mac with a recent macOS update, open Photoshop. 2. Run any script that contains the app.system() command to call a system utility (e.g., app.system('curl --version')). Expected Behavior: The script should execute the command and return the expected result. Actual Behavior: The script fails. In my case, a plugin that depends on curl returns a "Curl Not Found" error, even though curl is installed and works. A minimal test script using app.system() also fails. Diagnostics and Tests Performed: After extensive troubleshooting, we have confirmed the following: * The issue occurs on two different Mac machines. * The issue occurs on two different major versions of Photoshop (2024 and 2025). * The issue occurs with multiple different scripts, indicating it's not a bug in a specific script file. * The `curl --version` command works perfectly when run directly in the macOS Terminal, proving curl is installed and accessible. * Resetting Photoshop preferences, reinstalling scripts, and granting "Full Disk Access" and "Developer Tools" permissions to Photoshop did not solve the issue. Conclusion: The only logical conclusion is that a recent macOS security update has changed the sandboxing policies, and Photoshop is now being prevented by the operating system from executing processes via app.system(). This likely requires an update from Photoshop to comply with Apple's new APIs or security policies. Thank you for your attention. I look forward to a fix.

Correct answer creative explorer

@RS_Studio6742 You can often fix this immediately by providing permission to Photoshop to run the system command. Go to Applications > Utilities > Terminal. Paste the following command: 
xattr -r -d com.apple.quarantine /Applications/Adobe\ Photoshop\ 2025/Adobe\ Photoshop\ 2025.app (Adjust the year or path if you are using a different version.) You will need to enter the full path to your Photoshop application file (this example assumes you are running the latest version from the default location). This command removes a quarantine flag that macOS uses to limit the access of applications. Press Enter when done. Close and re-open Photoshop, then try running the plugin again. If you don't want to attempt the Terminal command, you can send a message to the Plugin Creator/Developer, and let them know the app.system call is failing due to the macOS security sandbox.

2 replies

Genius
September 29, 2025

I have scripts with system commands (EXIFTool as an example) and am not deeing this issue on multiple Macs, under both Sequoia and Tahoe.

creative explorer
Community Expert
creative explorerCommunity ExpertCorrect answer
Community Expert
September 29, 2025

@RS_Studio6742 You can often fix this immediately by providing permission to Photoshop to run the system command. Go to Applications > Utilities > Terminal. Paste the following command: 
xattr -r -d com.apple.quarantine /Applications/Adobe\ Photoshop\ 2025/Adobe\ Photoshop\ 2025.app (Adjust the year or path if you are using a different version.) You will need to enter the full path to your Photoshop application file (this example assumes you are running the latest version from the default location). This command removes a quarantine flag that macOS uses to limit the access of applications. Press Enter when done. Close and re-open Photoshop, then try running the plugin again. If you don't want to attempt the Terminal command, you can send a message to the Plugin Creator/Developer, and let them know the app.system call is failing due to the macOS security sandbox.

m