我认为苹果在试图引用Swift库libswiftCore.dylib时，已经在Swift应用程序崩溃下总结了它

引自技术问答QA1886:

Swift app crashes when trying to reference Swift library libswiftCore.dylib. Q: What can I do about the libswiftCore.dylib loading error in my device's console that happens when I try to run my Swift language app? A: To correct this problem, you will need to sign your app using code signing certificates with the Subject Organizational Unit (OU) set to your Team ID. All Enterprise and standard iOS developer certificates that are created after iOS 8 was released have the new Team ID field in the proper place to allow Swift language apps to run. Usually this error appears in the device's console log with a message similar to one of the following:

[....] [deny-mmap] mapped file has no team identifier and is not a platform binary:
/private/var/mobile/Containers/Bundle/Application/5D8FB2F7-1083-4564-94B2-0CB7DC75C9D1/YourAppNameHere.app/Frameworks/libswiftCore.dylib

Dyld Error Message:
  Library not loaded: @rpath/libswiftCore.dylib

Exception Type: EXC_BREAKPOINT (SIGTRAP)
Exception Codes: 0x0000000000000001, 0x0000000120021088
Triggered by Thread: 0

Referenced from: /private/var/mobile/Containers/Bundle/Application/C3DCD586-2A40-4C7C-AA2B-64EDAE8339E2/TestApp.app/TestApp
Reason: no suitable image found. Did find:
/private/var/mobile/Containers/Bundle/Application/C3DCD586-2A40-4C7C-AA2B-64EDAE8339E2/TestApp.app/Frameworks/libswiftCore.dylib: mmap() error 1 at address=0x1001D8000, size=0x00194000 segment=__TEXT in Segment::map() mapping /private/var/mobile/Containers/Bundle/Application/C3DCD586-2A40-4C7C-AA2B-64EDAE8339E2/TestApp.app/Frameworks/libswiftCore.dylib
Dyld Version: 353.5

The new certificates are needed when building an archive and packaging your app. Even if you have one of the new certificates, just resigning an existing swift app archive won’t work. If it was built with a pre-iOS 8 certificate, you will need to build another archive. Important: Please use caution if you need to revoke and setup up a new Enterprise Distribution certificate. If you are an in-house Enterprise developer you will need to be careful that you do not revoke a distribution certificate that was used to sign an app any one of your Enterprise employees is still using as any apps that were signed with that enterprise distribution certificate will stop working immediately. The above only applies to Enterprise Distribution certificates. Development certs are safe to revoke for enterprise/standard iOS developers.

正如AirSign人员所说，问题的根源在于内部证书的主题字段中缺少OU属性。

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

我有一个企业发展证书，创建一个新的解决了这个问题。

我测试了上面所有的解决方案，但没有一个解决问题。 我使用的是Xcode 10.2和macOS 10.14.3。 首先，我安装了swift 5对命令行工具的运行时支持，但没有任何变化 第二，我将操作系统更新到10.14.4，没有任何变化 第三，我把Xcode更新到11.2.1，问题解决了(不使用Xcode 11.2。它有存档问题，已弃用)

对我来说什么都没用，然后我做了下面这些步骤:

我从podfile中删除了flipper的使用情况。在我看来是这样的: use_flipper !({Flipper-Folly”= >“2.5.3”,“鳍”= >“0.87.0”,“Flipper-RSocket ' = > ' 1.3.1 '}) 我在我的项目中添加了一个swift文件来创建一个桥接头。

换了新mac后，我也遇到了同样的问题，几个小时后，我尝试了问题中所有建议的答案，但没有一个对我有效。

我的解决方案是安装这个丢失的证书。 http://developer.apple.com/certificationauthority/AppleWWDRCA.cer

在这里找到了答案。 https://stackoverflow.com/a/14495100/976628

我同时安装了多个版本的Xcode。这个框架是用更新版本的Xcode构建的。我尝试编译的应用程序使用的是较旧版本的Xcode。当我用相同版本的Xcode清理和编译框架和应用程序时，事情就正常了。

我也有同样的问题

有很多答案，但我的答案可能会帮助别人。

// MARK: -核心数据堆栈

 lazy var persistentContainer: NSPersistentContainer = {
            /*
             The persistent container for the application. This implementation
             creates and returns a container, having loaded the store for the
             application to it. This property is optional since there are legitimate
             error conditions that could cause the creation of the store to fail.
            */
            let mom = NSManagedObjectModel.mergedModel(from: [Bundle(for: Self.self)])!
            
            let container = NSPersistentContainer(name: "Test", managedObjectModel: mom)
            container.loadPersistentStores(completionHandler: { (storeDescription, error) in
                if let error = error as NSError? {
                    // Replace this implementation with code to handle the error appropriately.
                    // fatalError() causes the application to generate a crash log and terminate. You should not use this function in a shipping application, although it may be useful during development.
                     
                    /*
                     Typical reasons for an error here include:
                     * The parent directory does not exist, cannot be created, or disallows writing.
                     * The persistent store is not accessible, due to permissions or data protection when the device is locked.
                     * The device is out of space.
                     * The store could not be migrated to the current model version.
                     Check the error message to determine what the actual problem was.
                     */
                    fatalError("Unresolved error \(error), \(error.userInfo)")
                }
            })
            return container
        }()