我的项目是一个Swift项目，有一些Objective-C类。 我用旧的inHouse(企业)证书签名时也遇到了同样的问题。

以下步骤为我解决了这个问题。

创建并使用一个新的证书和移动供应。 (参考AIRSIGN博客) 将Runpath Search Paths构建设置设置为:$(inherited) @executable_path/Frameworks。 (参考马特的回答)

在更新到Xcode 10.2 (Swift 5)后遇到了这个问题。找到下面的苹果链接，显示了两个选项: https://support.apple.com/kb/DL1998?locale=en_US

对我来说，我把MacOS更新到10.14.4 (OS中包含Swift库)。否则，“下载Swift 5运行时支持命令行工具”的旧操作系统。

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

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代码/库，你应该尝试解决方案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

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

参考https://forums.developer.apple.com/thread/21292

这个解决方案对我很有效:

It occurred on my side when building an app in the command line via xcodebuild and xcrun PackageApplication, signing the app with an enterprise profile. On our CI build servers, the certificate was set to "Always Trust" in the keychain (select certificate -> Get Info -> Trust -> "Use System Default" can be changed to "Always Trust"). I had to set it back to "Use System Default" in order to make this work. Initially we set this to "Always Trust" to work-around the keychain dialogs that appear after software updates and certificate updates.

重启Xcode就解决了这个问题。