dyld: Library not loaded: @rpath/libswiftCore.dylib / Image not found

Question

I am running my app from xcode to my iOS device and I get this and black screen on iOS device.

Console text:

dyld: Library not loaded: @rpath/libswiftCore.dylib
Referenced from: /private/var/mobile/Containers/Bundle/Application/10DB2FE8-EF09-4857-B4AC-0DB2E4419D6F/App-Name.app/App-Name           
Reason: image not found        
(lldb)

Answer 1

Here are some steps to Solve the issue. Based on error below methods may helps you to solve the issue.(XCode Version Version 15.4 (15F31d))

By deleting Xcode's Derived Data directory.

OR

In the Framework Target (not the app target), go to Build Settings > Build Options > Always Embed Standard Swift Libraries to YES.

OR

Min Deployment to 13.0

AND

Clean the build folder: Product -> Clean Build Folder

Answer 2

Add @executable_path/Frameworks to the project Runpath Search Paths, not target. your_project -> Build Settings -> Linking -> Runpath Search Paths

Answer 3

Set "Always Embed Swift Standard Libraries" to "Yes" under your Build Settings > Build Options

(Don't forget to Shift+Cmd+K your project after)

Answer 4

Add the framework in the following locations:

1. General > Embedded Binaries
2. General > Linked Frameworks and Libraries
3. Build Phases > Link Binaries with Libraries

The embedded binaries seemed to be the key for me.

Answer 5

Add the following line to Runpath Search Paths of your target.

@executable_path/Frameworks

your_target -> Build Settings -> Linking -> Runpath Search Paths

Answer 6

Set the option

ALWAYS_EMBED_SWIFT_STANDARD_LIBRARIES

to YES in Project -> Build Settings -> Build Options

(Namirial framework through Cocoapods)

Answer 7

Seems this issue was caused by the inclusion of Swift file into objective-c custom framework. Also unsure if related but my app target was built in objective-c as well. Also building to simulator in debug. Haven't verified for release or archive build yet.
Additionally Runpath Search Settings for the project target were set to "@executable_path/Frameworks", within the target settings for the framework they were set to: "@executable_path/Frameworks" and "@loader_path/Frameworks".

After having tried rebuilding custom framework and reattaching to app target, clearing derived data folder and a couple other suggestions, what ultimately worked for me was changing the build setting within Project target for the custom framework project (not app target): "Always Embed Swift Standard Libraries" to "YES". It appeared not to matter what the setting for the app target was set to. I verified this by resetting the simulator and rebuilding. This is similar to Daniele Ceglia's answer but I wanted to provide more clarity.

Answer 8

The issue came from the certificates generated automatically by Xcode. I had to revoke these certificates dans generate them back from developer.apple.com

The solution is then:

• Go to developer.apple.com / certificates --> Revoke certificates OR go in Xcode > preferences > accounts > View details > select Sigining identities > clic setting whell > revoke
• Got to developper.apple.com and follow instructions to generate new certificates
• In Xcode in my project : go to Code Signing Identity and sign both Debug lines with the generated certificate
• Both release lines are set to "iOS Developer"
• Then project > clean
• Build and run on device

Answer 9

Just create a dummy.swift in your project, and Xcode would pop a window remind you whether need to create a bridge header, choose yes.

Answer 10

This is happening because I changed bundle identifier, so I just put old bundle id and it started to work again.

Answer 11

I fixed by deleting all from Xcode Derived Data directory:

~/Library/Developer/Xcode/DerivedData

Answer 12

I changed the iPhone Developer Certificate trust settings in Keychain. It should be Always Trust. Change it to Use System Defaults. Double click the certificate in Keychain to open the option screen Discovered that from this blog

Answer 13

I have done it on stupid way created new project and pod install from scratch and after confirmed it is working correctly, I copied all class files and storyboard files, at last done!

Answer 14

Everything was fixed by deleting Xcode's Derived Data directory.

Answer 15

In the Framework Target (not the app target), go to Build Settings > Build Options > Always Embed Standard Swift Libraries to YES.

Answer 16

In my case, This issue is coming in Objective-c project in which I am using a Swift framework (AirWatch SDK).

Solutions: I have resolved this issue with Xcode 9.3 and 11.0.1 iOS as mentioned bellow steps :

1. Drag and drop your swift framework in your project and move in default Framework folder of your project.
2. Then add them as Embedded binaries as shown in screenshot.
3. Change your framework status from Required to Optional as shown in screenshot. (Build Phases > Link Binary with Library)

3. Set Always Embed Swift Standard Libraries to Yes in your build settings.

4. Set Subpath and select destination as Framework for your added framework in Build Phases> Embed frameworks as shown in screenshot.

Answer 17

In my case Mac M1, xcode 14.3.1: I added /usr/lib/swift to Runpath Search Paths then it worked:

• Build Settings > search Run
• Add /usr/lib/swift into Runpath Search Paths enter image description here

Answer 18

I have an objective-c project, and this problem showed up after updating the Firebase version in Cocoapods. I added a new swift file (File->New->File) and was asked if I wanted to add a bridging header. I selected Yes, which fixed the problem.

Answer 19

Please check the *.framework If there is a _CodeSignature signature framework directory. If there is no _CodeSignature folder, Navigate to the Build Phases ,click + to add New Copy File Phase to create Copy Files. after that, reference *.framework and choose Code Sign On Copy

Answer 20

I had this error in a command line project (Xcode 10.2 and macOS 10.14.3)

The solution was to update to macOS 10.14.4

Swift command line projects won’t run on macOS 10.14.3 and earlier unless you install the Swift 5 Runtime Support for Command Line Tools package. Without that package, Swift command line projects crash on launch with “dyld: Library not loaded” errors. (46824656)

From Swift 5 Release Notes for Xcode 10.2

Answer 21

I had a similar problem in an Objective-C project where I started to include Swift files.

In my case, I created two targets in the main project, and I added a Swift empty file, that creates a bridging header file and some configurations, but I only marked it as a member of one target. The first target works properly, but the second not, and I noticed that the differences in build settings were this setting:

Runpath Search Paths -> $(inherited) and @executable_path/Frameworks

And I also needed to reference Objective-C Bridging Header to the file that was created before:

Objective-C Bridging Header -> pathTo/Target-Bridging-Header.h

After adding this two settings, the second target started to work properly.

Answer 22

This error message can also occur when using a framework build in a different Swift version then the one currently being used, e.g. if you upgrade Xcode.

Answer 23

For me Cleaning the project solve the issue!

Answer 24

I had this problem before in iPod touch iOS 9.3. And I used all the methods mentioned in this post, but none of them worked. I checked my project setting. And in the other link flag, I found I added -Wl,-sectcreate,__RESTRICT,__restrict,/dev/null.

This flag prevents dyld insert in the jailbroken phone. When I delete this flag, the app can be launched again. I am not sure why it worked. Because in iPhone se iOS 10 I don't have to delete this line. But it did work in iPod touch iOS 9.3. So check it if you have the same situation like me.

Answer 25

I already had the Runpath Search Paths set correctly, but it still didn't work. @Justin Domnitz's answer put me on the right track: Setting "Always Embed Swift Standard Libraries" to Yes in my target's build settings did the trick for me.

Answer 26

I had to switch 'Embedded Content Contains Swift Code' to 'Yes' to get my Obj-C app to work after updating the Obj-C embedded framework with a Swift object.

Answer 27

I have faced the same issue, setting the right code sign identity solved the problem(Build settings->Code Signing Identity).

As per Apple technical questions "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"