我能够从xcode 6.1之前的备份中恢复我的项目，

一旦我从不同的目录打开我的工作空间，我就能够运行我的目标而不会出现这个错误。 模拟器现在也可以正常工作了。

What we didn't do right was to not apply with the accurate code when signing in the Build Settings. We fixed the issue up this way: Enter into Build Settings >> Code Signing >> Code Sign Identity. Then, apply with your iOS Developer ID for 'Debug', but be sure to apply with your iOS Distribution Profile for 'Release' We didn't apply correctly, so we couldn't have permission to ask for the App from the server, actually. Anyway this post forced us to revise all the parameters and requirements, so we pretty appreciate all your answers. Regards, T.

我能够从xcode 6.1之前的备份中恢复我的项目，

一旦我从不同的目录打开我的工作空间，我就能够运行我的目标而不会出现这个错误。 模拟器现在也可以正常工作了。

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

我发现在Build Options中将我的编译器更改为LLVM 6.0对我来说就足够了(xcode 6.1)

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