macOS Gatekeeper: "libgdioapplm1.dylib" Not Opened
When you first run a GameDriver test on macOS, you may see a dialog that reads:
“libgdioapplm1.dylib” Not Opened
Apple could not verify “libgdioapplm1.dylib” is free of malware that may harm your Mac or compromise your privacy.
This is expected behaviour. macOS Gatekeeper applies a quarantine attribute to any file downloaded from outside the App Store or an Apple-notarized installer. Because GameDriver ships as a .unitypackage, the libraries it contains carry this attribute until you explicitly clear it.
Option 1: System Settings (GUI)
Section titled “Option 1: System Settings (GUI)”This is the quickest path on a local developer machine.
- Open Apple menu > System Settings > Privacy & Security.
- Scroll down to the Security section.
- You will see a message stating that
libgdioapplm1.dylibwas blocked. Click Allow Anyway. - Re-run your test. macOS will prompt one more time to confirm. Click Open.
The library is now saved as a permanent exception and will not be blocked again on this machine.
Option 2: Terminal (xattr)
Section titled “Option 2: Terminal (xattr)”This approach is faster when clearing multiple libraries, and is the only option in headless or CI/CD environments.
Run the following command, replacing the path with the actual location of the library on your machine:
xattr -d com.apple.quarantine /path/to/libgdioapplm1.dylibTo clear the quarantine attribute from all GameDriver libraries at once, run the command against the entire GDIO folder in your Unity project:
xattr -dr com.apple.quarantine /path/to/your/UnityProject/Assets/GDIO/The -r flag applies the removal recursively to every file in the folder.
CI/CD and automated pipelines
Section titled “CI/CD and automated pipelines”If your test runner is executing on a macOS build agent, the quarantine block will interrupt unattended runs. Before the first test execution on any new agent machine, add the xattr command above to your pipeline setup script or agent provisioning step.