对我来说，一个简单的产品->清洁工作很棒

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.

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.

X-code 6.3.2

[构建设置]选项。 [所有]-[构建选项]-[C / c++ /Objective-C编译器]-[默认编译器(Apple LLVM 6.1)]

然后重新构建项目，它可以正常运行。

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

我的项目也遇到了同样的问题。后来发现项目中使用的第三方(fmdb for SQLite)文件包含Info.plist。

简单地删除信息。Plist文件为我工作!