发生这种情况的原因有很多。刚刚度过了一个有趣的周末，发现了另一个导致这个问题的问题(代码签名的顺序)，我想创建一个总结答案，将所有可能的解决方案放在一起:

Add Embedded Content Contains Swift Code to project. You need to set this flag if your app contains Swift code. Clean project. In addition to a Project > Clean you can also delete the DerivedData and Build directories. Look under the Preferences for the location of DerivedData. Build should be in your project folder. Ensure Runpath Search Paths contains @executable_path/Frameworks. Ensure that your certificate contains your Apple Team ID in the OU (Organization Unit) field Apple will add this for you, just revoke your existing distribution certificate and create a new one, download, install on KeyChain, regenerate all provisioning profiles, download those and rebuild. Xcode restart. If everything is basically good, but Xcode hasn't gotten there yet.

这很简单。如果你正在进行自己的命令行构建，你可能会创建自己的.ipa文件来上传。在这种情况下，您需要确保以下内容:

Make sure the version of the Swift files in SwiftSupport/iphoneos is the same as the version in Contents/YourApp.app/Frameworks Because Swift is not yet binary compatible between version, you must ensure these versions are the one that you built your app with. You can find these libraries under /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/lib/swift/iphoneos. Sign the libraries and frameworks first. You need to codesign the libraries and framework files (under Frameworks in the .app folder) first and then sign the entire .app tree. The .app tree must be signed with an entitlements.plist but not the frameworks.

希望当Swift 3.0问世时，我们不再需要将Swift捆绑到我们的应用程序中，这个问题就会消失。

如果在Objective-C项目转换为开始使用Swift的过程中出现了错误，就会发生此错误。问题是链接器构建设置从未正确配置，所以你必须手动完成。寻找Runpath Search Paths构建设置并将其设置为:

$(inherited) @executable_path/Frameworks

编辑:我还应该补充一点，最近有大量的错误完全是由其他原因引起的——苹果对Swift本身进行了更改，可能从Xcode 6.1或6.1.1开始。唯一的解决方案似乎是退出Xcode，在Keychain Access中销毁你的证书，到会员中心删除所有证书和配置文件(除了应用商店中的配置文件-你不能删除它们)，然后从头开始整个证书请求过程。

我在我的项目中添加了SCLAlertView pod，后来删除了它。我没有从我的视图控制器中删除导入SCLAlertView。理想情况下，它应该给出一个编译时错误，但它给出了一个运行时错误，提到dyld: Library not loaded: @rpath/SCLAlertView.framework。我从我的视图控制器中删除了导入SCLAlertView，构建它，它没有给出错误。所以在我的情况下，我试图导入一个没有找到框架的库。删除这些引用将解决您的问题。

我在这个问题上研究了很久。有几个原因导致这个问题。

如果你在objective - C项目中使用Swift代码/库，你应该尝试解决方案1-2-3

如果你正面临这个问题，一个新的Swift项目解决方案4将最适合你。

解决方案1:

重启Xcode，然后重启电脑和iPhone

解决方案2:

转到项目构建设置，并设置始终嵌入Swift标准库(以前的嵌入式内容包含Swift代码)标志为YES

解决方案3:

进入项目构建设置，将@executable_path/Frameworks添加到Runpath搜索路径选项

解决方案4:

如果以上都不起作用，那么应该这样做。正如AirSign的帖子中提到的，苹果似乎是忍者补丁证书

At InHouse证书

主题:UID=269J2W3P2L, CN=iPhone分布:公司名称，O=公司名称，C=FR

他们添加了一个名为OU的新字段

主题:UID=269J2W3P2L, CN=iPhone分布:公司名称，OU=269J2W3P2L, O=公司名称，C=FR

因此，您应该重新创建证书和供应

我真的不知道为什么这个问题被否决了，当我第一次尝试在一个现有的项目中使用Swift时，我也遇到了这个问题。Xcode重启也为我解决了这个问题。

发生这种情况的原因有很多。刚刚度过了一个有趣的周末，发现了另一个导致这个问题的问题(代码签名的顺序)，我想创建一个总结答案，将所有可能的解决方案放在一起:

Add Embedded Content Contains Swift Code to project. You need to set this flag if your app contains Swift code. Clean project. In addition to a Project > Clean you can also delete the DerivedData and Build directories. Look under the Preferences for the location of DerivedData. Build should be in your project folder. Ensure Runpath Search Paths contains @executable_path/Frameworks. Ensure that your certificate contains your Apple Team ID in the OU (Organization Unit) field Apple will add this for you, just revoke your existing distribution certificate and create a new one, download, install on KeyChain, regenerate all provisioning profiles, download those and rebuild. Xcode restart. If everything is basically good, but Xcode hasn't gotten there yet.

这很简单。如果你正在进行自己的命令行构建，你可能会创建自己的.ipa文件来上传。在这种情况下，您需要确保以下内容:

Make sure the version of the Swift files in SwiftSupport/iphoneos is the same as the version in Contents/YourApp.app/Frameworks Because Swift is not yet binary compatible between version, you must ensure these versions are the one that you built your app with. You can find these libraries under /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/lib/swift/iphoneos. Sign the libraries and frameworks first. You need to codesign the libraries and framework files (under Frameworks in the .app folder) first and then sign the entire .app tree. The .app tree must be signed with an entitlements.plist but not the frameworks.

希望当Swift 3.0问世时，我们不再需要将Swift捆绑到我们的应用程序中，这个问题就会消失。