1)首先构建选项。

2)然后将“Compiler for C/ c++ /Objective-C”的值改为Default Compiler。

清洁和工作:-)

如果你谷歌这个错误消息的文本，你会在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年了。解决方案是切换到遗留构建系统，这导致了编译错误，因为在旧项目中没有现代架构目标，可以通过手动添加它们来修复。

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.

错误消息是通用的，实际上并没有告诉您它的真正含义。

对我来说，我必须恢复早期的github回归，这给:

armv7 armv7s arm64

对建筑。

我有这个问题时，我的appdelegate类没有链接到我的主要应用程序目标，而是一个单独的静态框架。直接链接到目标应用程序解决了这个问题。

我试了所有列出的答案，没有一个有用。问题是由于存在另一个plist文件通过cocoapods从子模块链接。幸运的是，这是我自己的模块，所以我只是从子模块项目中删除了这个plist，并重新安装了pods。

解决方案

后来我明白了问题的关键在于第二个plist的名称:简单地说，就是info.plist。您可以重命名文件并通过子模块的sources部分重新链接它

第二个plist文件有一个唯一的名字，所以Xcode不应该感到沮丧。甚至我的目标设置都指向一个主plist，而不是info.plist。看来Xcode对这个名字有特别的考虑

该错误在Xcode 6.4和Xcode 7.0中再现