We have integrated the Unity Security Patcher (v1.2.0) into our automated CI/CD build pipeline on macOS, but we’re experiencing a critical issue that prevents unattended operation.
Problem:
The UnityApplicationPatcherCLI hangs indefinitely when executed on a locked/logged-out macOS machine, but works correctly when the machine is unlocked with an active user session and UI available.
Environment:
-
OS: macOS (Arm64)
-
Unity Patcher Version: 1.2.0
-
Patcher File: UnityApplicationPatcherCLI (from UnityApplicationPatcher-1.2.0-macOS-Arm64.zip)
-
Build Environment: Automated CI/CD pipeline (headless/unattended)
-
Target Platform: Android (.aab files)
How to test it?
We successfully reproduced the issue by connecting via SSH to a machine without monitor/UI access (such as a build server) and attempting to run the command. The command works when connecting through screen sharing, but fails via SSH.
This limitation renders the patcher unusable on build server machines.