Closed rallen10 closed 4 months ago
Maybe macOS security mechanism kicks in. macOS caches information about the code’s signature in the kernel. It seems that Apple M processors require all code to be validly signed (if only ad hoc) or the operating system will not execute it, instead killing it on launch.
See https://developer.apple.com/documentation/security/updating_mac_software and some related discussion in https://stackoverflow.com/questions/67378106/mac-m1-cping-binary-over-another-results-in-crash
@hbe72 This seems to be the issue! Thank you.
The fix/workaround is identified in Mac's documentation. In short, use ditto
to move instead of cp
cp -r build/ ~/Desktop/AppSandboxBuild
~/Desktop/AppSandboxBuild/bin/AppSandbox
# This will fail with the above error
ditto build/ ~/Desktop/AppSandboxBuild2
~/Desktop/AppSandboxBuild2/bin/AppSandbox
# This works
I am running into an error when trying to relocate a very simple compiled app to a different part of my machine (not even a different machine).
System and Library Info
curl -fsSL https://install.julialang.org | sh
Minimum working example
I'm just trying to create a very simple app I'm calling AppSandbox
Then to build, I run the following using a local fix for issue #738 (see comment with fix here)
The app builds and I can successfully run it in the location it was built
But if I try to relocate the app locally, I get the following error