我的天哪! !我花了几个小时来解决这个问题。

在XCode 7.3上，我的项目没有任何问题。

我错了

我只是添加了物理文件夹，并将我的文件移动到其中，问题开始了。

我什么都试过了

默认的编译器 清洁和构建 重置模拟器和重启模拟器，Xcode, iPhone甚至mac 更新Info.plist 删除派生数据 编辑项目文件夹的权限 检查我的架构

什么都没用:(

我是如何决定的

我是关于创建新项目，然后我只是删除那些物理 我添加的文件夹，干净的构建和是的!!

它的工作原理!

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

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。

在尝试了所有其他的解决方案(对我来说并不管用)之后，我这样做了，这个问题自动得到了解决。

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中打开旧项目会得到这个消息。

转到问题导航器，并遵循警告提示“更新到重新确认的设置”。

繁荣,神奇!