我正在试着在我的iPhone 4s上运行Swift应用程序。它在模拟器上运行良好，我的朋友也可以在他的iPhone 4s上成功运行。我有iOS 8和官方发布的Xcode 6。
我试过了
重启Xcode, iPhone，电脑
清洁和重建
撤销并创建新的证书/供应配置文件
运行路径搜索路径是$(inherited) @executable_path/Frameworks
包含Swift代码的嵌入内容是“是”
代码签名身份是开发人员
下面是完整的错误
dyld: Library not loaded: @rpath/libswiftCore.dylib
Referenced from: /private/var/mobile/Containers/Bundle/Application/LONGSERIALNUMBER/AppName.app/AppName
Reason: no suitable image found. Did find:
/private/var/mobile/Containers/Bundle/Application/LONGSERIALNUMBER/AppName.app/Frameworks/libswiftCore.dylib: mmap() error 1 at
address=0x008A1000, size=0x001A4000 segment=__TEXT in Segment::map() mapping
/private/var/mobile/Containers/Bundle/Application/LONGSERIALNUMBER/APPLICATION_NAME/Frameworks/libswiftCore.dylib
我们有一个unity项目，它创建了一个xcode项目，其中包括使用swift的库。
我们尝试了这个话题上的每一个合理的建议。
毫无效果。代码在新设备上运行良好，在iOS上崩溃<=12
看起来swift是如此的聪明，即使你将它设置为"ALWAYS_EMBED_SWIFT_LIBRAIES"="YES"，它也不包括swift库。
真正为我们解决问题的是在项目中包含一个虚拟的swift文件。
该文件必须包含对分派、基础库的调用。
显然，这暗示了mighty-xcode强制包含库，但这次是真的。
下面是我们添加的虚拟文件，使其工作:
import Dispatch
import Foundation
class ForceSwiftInclusion {
init() {
// Force dispatch library.
DispatchQueue.main.async {
print("something")
}
// Force foundation library.
let uuid = UUID().uuidString
print("\(uuid)")
}
}
对于统一，也添加项目。AddBuildProperty(target， "SWIFT_VERSION"， "Swift 5");到创建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
}()
