如果你谷歌这个错误消息的文本，你会在StackOverflow，苹果开发论坛，Reddit等地方发现大约20个关于Xcode无法运行编译后的可执行文件的错误消息。

In these threads you will find many people offering various suggestions about how to fix the problem: changing product name to match project name, changing build phase options, something with info.plist, changing compilers to or from Clang, etc. Presumably the suggestions are offered in good faith because they solved the problem for someone, but the answers are so varied that it is clear that the error message is generic and this is an important point if you are receiving it: this error seems to mean that something is wrong with the binary. Ignore its actual text: it may have nothing to do with permissions.

对于这个错误没有通用的解决方案。错误消息是完全通用的;假设它意味着“坏二进制文件”。如果你收到它，解决方案取决于你正在尝试做什么，改变了什么，为什么你突然看到这个错误。谷歌您的具体情况，而不是这个错误消息。

在我的例子中，我感觉这是一个常见的例子，我试图做的是在现代Xcode上构建一个旧的iOS项目，我想有9年了。解决方案是切换到遗留构建系统，这导致了编译错误，因为在旧项目中没有现代架构目标，可以通过手动添加它们来修复。

我已经通过清理构建文件夹来修复它。刚刚进入“产品”菜单和选项+点击“清洁”。在那之后，一个问题解决了。

我的用例有点独特。我使用app_spec的info_plist属性来额外指定信息。plist属性通过哈希。

但是，设置CFBundleExecutable键会导致权限错误。我把它拿掉了。

我也遇到过类似的问题。不知何故，我的值键可执行文件混淆了。只需将其更改回${EXECUTABLE_NAME}(在您的项目> Info下)。为我工作!

None of the provided answers worked for me. In my case, I finally fixed the error by updating the target architectures in Build Settings/Architectures/Valid Architectures to $(ARCHS_STANDARD), as arm64 was missing. This was not prohibiting the project to build, although a warning was issued recommending updating the valid architectures, but the "app could not be opened" error was shown at run time. I surmise this error is rather generic and not always linked with a permission issue, but may be displayed when the generated app package is invalid.

我会进入Xcode文档所在的文件夹，点击command + I来获取信息。在底部，点击锁以解锁文件夹以编辑权限。如果权限看起来不错，勾选“应用到附带文件夹”的复选框，让它来做它的事情。我个人没有见过这个，也不确定这是否是你在编辑构建权限时在你的帖子中所说的。