Posts

Post not yet marked as solved
2 Replies
So, the ultimate answer proved to be totally different. After agonizing amounts of diagnosing, trying new configurations, I finally realized that there are two error messages up there: Reason: no suitable image found.  Did find:  file system relative paths not allowed in hardened programs The first one turned out to be correct; there was, in fact, a dylib missing from my build. (One for x86_64 arch) The second message is completely wrong, and led me down a long irrelevant path.
Post not yet marked as solved
48 Replies
I got the same message in Mojave (10.14.5) even though I had 40GB available. I thought it was corrupted, so downloaded again with no change. I was able to work around in Terminal:cd ~/Applications #otherwise, will unpack into home dir xip -x ~/Downloads/Xcode_11_Beta.xip