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/libswif         


        

Answer 1

I got such issue, too All other ways could not help me, so 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! I think it is the last way for it, maybe could help you

Answer 2

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 3

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 4

I had the same error message, that is how I solved it :

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 5

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 6

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