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

Question

I am trying to run a Swift app on my iPhone 4s. It works fine on the simulator, and my friend can successfully run it on his iPhone 4s. I have iOS 8 and the official release of Xcode 6.

I have tried

Restarting Xcode, iPhone, computer
Cleaning & rebuilding
Revoking and creating new certificate/provision profile
Runpath Search Paths is $(inherited) @executable_path/Frameworks
Embedded Content Contains Swift Code is 'Yes'
Code Signing Identity is developer

Below is the error in entirety

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

possible duplicate of [dyld: Library not loaded: @rpath/libswift\_stdlib\_core.dylib](http://stackoverflow.com/questions/24002836/dyld-library-not-loaded-rpath-libswift-stdlib-core-dylib) — Sruit A.Suk, Jun 20 '15 at 20:26
Solution is [here](http://stackoverflow.com/questions/27116371/dyld-library-not-loaded-reason-no-suitable-image-found/43466989#43466989). The same topic — Tarik, Apr 19 '17 at 14:04
1 I have been facing the same problem... It got fixed by adding: In you podfile: use_modular_headers! instead of use_frameworks! Good luck! I hope this works for you! — XtremeDevX, May 19 '20 at 06:04

score 582 · Answer 1 · edited Apr 05 '18 at 22:43

582

For me none of the previous solutions worked. We discovered that there is an "Always Embed Swift Standard Libraries" flag in the Build Settings that needs to be set to YES. It was NO by default!

Build Settings > Always Embed Swift Standard Libraries

After setting this, clean the project before building again.

For keen readers some explanation The most important part is:

set the Embedded Content Contains Swift Code (EMBEDDED_CONTENT_CONTAINS_SWIFT) build setting to YES in your app as shown in Figure 2. This build setting, which specifies whether a target's product has embedded content with Swift code, tells Xcode to embed Swift standard libraries in your app when set to YES.

enter image description here

The flag was formerly called Embedded Content Contains Swift Code

edited Apr 05 '18 at 22:43

pkamb

33,281
23
160
191

answered Nov 15 '14 at 18:28

TALAA

6,184
1
13
21

21

Worked for me too, so thanks a bunch. What puzzles me is, if I add swift code to a project, why doesn't Xcode updates this automatically? It sounds like a reasonable default behavior. I suppose this way it gives you more control over included libraries, etc. – PoL0 Dec 03 '14 at 12:06
Using the new CocoaPods pre with Swift support required this flag, at least for me. Thanks! – Markus Rautopuro Jan 10 '15 at 16:10
It's some weird bug of Xcode of not including Swift libs at some stage. Your answer helped, thanks a lot. Afterwards I set the property back to default No and it still continued to work fine. Just to keep things clean. As the property itself isn't required to be set for most of cases. http://stackoverflow.com/a/25703809/620184 – zubko Mar 23 '15 at 04:10
What a shame, still occurring on XCode 6.4 – webo80 Jul 13 '15 at 08:24
1

@wisenomad If it keeps working after removing the setting, that's because Xcode doesn't remove files when it does an installation. So if you uninstall the app from your device, then reinstall, you will resurface the bug. So you should not turn the setting back to NO, as that will break installation for people other than yourself. – nevyn Aug 19 '15 at 10:30
14

For me was "Embed asset Packs in Product Bundle"! – Matte.Car Sep 20 '15 at 11:16
19

Do a clean after you do this. – Aggressor Oct 27 '15 at 16:35
3

Doing a clean after doing this is what solved my problem. Glad I checked the comments! =] – Relequestual Dec 09 '15 at 17:09
I got this problem in Xcode 7.1.1 I installed a pod that included some swift code, it caused the same error as OP. This solution did work for me, and I think is the best one. – robinsj Dec 16 '15 at 21:01
1

The parameter of it is "Yes" at the beginning. I set it to "No", build the app and then set to "Yes". And the app works again. – oOEric Feb 15 '16 at 03:15
This. But had to clean project as well. – Makalele Feb 20 '16 at 20:44
This worked for me. I had to set the flag in the swift project I added to my workspace as well though. – horsejockey May 03 '16 at 21:03
My problem was solved after applying the changes suggested by TALAA and then cleaned the build and deleted derived data. – Aadi007 Jun 13 '16 at 08:24
Added some more explanation about that setting (if anyone interested). @TALAA it is worth to include some references to the documentation explaining what such setting mean and what are the implications. Anyway, up vote for a good answer – Julian Jun 27 '16 at 09:08
This can happen if you added swift code AFTER creating the Unit tests. In this case you have to set this on the targets section. (my case) – Felipe Cesar Assis Aug 11 '16 at 16:27
79

It's called Always Embed Swift Standard Libraries now. – Warpzit Aug 16 '16 at 06:27
Thanks a lot, it worked. It was actually set to YES in the main app, but set to NO in the app extension target, for some reason... *smh*. – Artemix Oct 19 '16 at 13:22
2

Be aware! - this is needed ONLY when your project does not use Swift code and have embedded libraries written in Swift. – Roy K Aug 15 '17 at 07:44
It does not work for me in Xcode 10.2 Beta in macOS 10.14.2. I checked the setting, cleaned build folder and it didn't help. I had to manually copy libSwiftXXX.dylibs to some place (like Desktop/SwiftDylibs, but please don't do it for production:P) and then modify Runpath Search Path to make it search in Desktop as well. – manicaesar Jan 29 '19 at 14:01
I agree with @manicaesar. I am experiencing the same issue on Xcode 11.3.1. – Pedro Paulo Amorim Mar 05 '20 at 09:51
I did this and now get a different error "Thread 1: signal SIGABRT" Don't know if that's better or worse. Still works on emulator only. – Curtis May 17 '20 at 21:13
In my case my Deployment Target was 10.0, I changed it to 13.0 and my issue was resolved. So my suggestion is also to check your deployment target as well. – Zulqarnain Mustafa Jul 02 '23 at 06:40

score 144 · Answer 2 · answered Dec 31 '15 at 07:31

144

Surprisingly enough, all i did was "Clean" my project (shift+cmd+K) and it worked. Did seem to be related to the certificate though.

answered Dec 31 '15 at 07:31

royherma

4,095
1
31
42

Clean makes sense, since it forces refreshing of cached items used in a build. I had to do this because I just refreshed a signing certificate. I did a clean and a Clean Build Folder (Option-clean). – Victor Engel Mar 13 '16 at 17:03
13

ha yes,it worked. i had reset my certificates earlier and this clean worked like a charm. – Code Tree May 07 '16 at 14:26
GENIUS, hah this was prob caused by upgrading from swift 2 to 3 without cleaning in between i suspect, for me at least – Fonix Nov 10 '16 at 13:33
If error occurs when compiling on a different machine, this could be the easiest fix. – cypark Jan 31 '18 at 16:45
Oh my god Apple, It's seriously true still in 2018. – boraseoksoon May 02 '18 at 06:20
2

Same problem here. New fresh build is required after manipulating certificates. – Marc Jan 21 '19 at 15:46
1

Same problem here . Clean is must step. no need to manipulate certificates. my problem solved. – Manish Nahar Jan 24 '19 at 07:25
this happened when I merge a branch so clean the build and then archive and it will work. – Cyrus Zei Jun 18 '20 at 04:07

score 102 · Answer 3 · answered Dec 11 '14 at 22:08

102

I started getting this error when I removed:

@executable_path/Frameworks

from Runpath Search Paths in my build settings. Replacing it fixed everything up again (thank goodness for source control!)

I don't know how it got there, but it appears to be needed for a binary to find its embedded Swift runtime.

answered Dec 11 '14 at 22:08

jemmons

18,605
8
55
84

2

Updated an old iOS6 project to iOS7 and Swift and got that error. @executable_path/Frameworks fixed it. Thanks! – Lensflare Dec 15 '14 at 16:07
6

For me, as of Xcode 8b5, it was actually `@loader_path/../Frameworks` for macOS unit tests and `@loader_path/Frameworks` for iOS unit tests that needed to be added. – Pascal Aug 12 '16 at 08:20
Yes! This was the fix that did it for me in iOS 10/Xcode 8. The project began on iOS 2-3 as pure objective-c and we're just now adding some Swift. – TahoeWolverine Oct 12 '16 at 20:44
Adding this fixed the error for me, as well. Anyone know the full reason for this? Thanks for the help. – Rod Nov 20 '16 at 00:40
Worked for me too! (XCode 8.2.1) – The Good Giant Feb 13 '17 at 16:29
@Pascal I want to kiss you. That is all. Thank you so much - @loader_path/Frameworks did it for me on iOS/Xcode9 – CPR Nov 03 '17 at 18:10

score 70 · Answer 4 · edited Jun 17 '18 at 14:18

70

For the device, you also need to add the dynamic framework to the Embedded binaries section in the General tab of the project.

edited Jun 17 '18 at 14:18

Cœur

37,241
25
195
267

answered Sep 25 '14 at 16:51

Mustafa

5,307
1
20
19

Embedded Binaries or Linked Frameworks and Libraries? And what are you referring to when you say the dynamic framework? – user3751185 Sep 25 '14 at 19:45
I'm assuming you are trying to use a dynamic framework. – Mustafa Sep 26 '14 at 16:45
I'm trying to add the Google Maps Framework. Correspondingly AVFoundation, CoreData, CoreLocation, CoreText, GLKit, ImageIO, OpenGLES, QuartzCore, SystemConfiguration. In addition: libc++.dylib, libicucore.dylib, libz.dylib. I don't have an 'Embedded frameworks' tab. What do you recommend I try? – user3751185 Sep 27 '14 at 00:59
1

Any thoughts? @Mustafa – user3751185 Sep 29 '14 at 18:00
69

The answer is very vague. – Unheilig Nov 06 '14 at 02:24
1

Again, answer quite vague. Not entirely sure what that means in relation to the OP. – Richie Marquez Nov 12 '14 at 18:46
2

Worked for me. Adding only to the "Linked frameworks and libraries" section didn't do the trick. – Danchoys Mar 14 '15 at 15:57
5

To expound: If what you're seeing in the error message is the name of a framework (e.g., a custom Cocoa Touch Framework that you made), don't just add the .framework in the Target Dependencies in Build Phases. You also need to add it to Embedded Binaries in the General tab. This answer fixed it for me. – Matthew Quiros Apr 15 '15 at 09:29
This worked for me as I was using 3 custom frameworks that I'd made. All I needed to do was add them to the Embedded binaries section and things worked perfectly. Great answer. – TMc May 09 '15 at 00:08
Can anyone explain simply what needs to be done with above answer in simple steps. – UKDataGeek Dec 29 '16 at 18:39

score 69 · Answer 5 · edited Apr 06 '18 at 22:09

69

In Xcode 8 the option for Embedded Content Contains Swift Code option is no longer available.

It has been renamed to "Always Embed Swift Standard Libraries = YES"

edited Apr 06 '18 at 22:09

pkamb

33,281
23
160
191

answered Nov 22 '16 at 08:03

Bonnie

4,943
30
34

This helped me with a crash on WatchOS – trusk Jun 14 '17 at 15:25

score 67 · Answer 6 · answered Nov 05 '21 at 11:16

67

Xcode 13 here (13.1 with react-native).

Created a clean react-native project and saw /usr/lib/swift as an entry in Runpath Search Paths.

After adding that, my project finally ran without crashing!

Nothing helped from what was suggested before.

answered Nov 05 '21 at 11:16

Hlib Barylskyi

865
1
7
11

11

This saved my day! Non of above solution works for Xcode 13, thanks! – Sunding Wei Dec 03 '21 at 09:36
Wow. the only thing that worked. gg wp. Tho I wonder why it is even required. for me it happened with unity project export not implementing it for some reason... – Kashkashio Feb 28 '22 at 23:10
Work like a charm for react-native 0.68.1!! Thank you – lmasneri May 12 '22 at 12:45
gg wp! indeed Nothing else worked except this. – noob Mama Jun 23 '22 at 22:25
This is the only solution that worked for me (Flutter, Xcode 13.2.1). Thank you! – thammaknot Jul 10 '22 at 03:48
Solved build issue for the Flutter Google-Ml-Kit-plugin in Xcode 13.4.1. Thanks! – VladH Aug 13 '22 at 00:46
Beautiful, this worked. Thank you! Likely a botched RN upgrade. – JaviCasa Sep 29 '22 at 22:50
Great! Xcode 14.2 worked like a charm! – Vidurajith Darshana Jan 15 '23 at 06:34
Yup. This was the solution for me. No idea what is really going on. – Larry Jan 16 '23 at 00:07

score 29 · Answer 7 · answered Dec 05 '14 at 23:16

29

I think it's a bug when certificates are generated directly from Xcode. To resolve (at least in Xcode 6.1 / 6A1052d):

go to the Apple Developer website where certificates are managed: https://developer.apple.com/account/ios/certificate/certificateList.action
select your certificate(s) (which should show "Managed by Xcode" under "Status") and "Revoke" it
follow instructions here to manually generate a new certificate: https://developer.apple.com/library/ios/documentation/IDEs/Conceptual/AppDistributionGuide/MaintainingCertificates/MaintainingCertificates.html#//apple_ref/doc/uid/TP40012582-CH31-SW32
go to Xcode > Preferences > Accounts > [your Apple ID] > double-click your team name > hit refresh button to update certificates and provisioning profiles

answered Dec 05 '14 at 23:16

Vijay Sundaram

291
3
2

Worked for me only when deleting and creating only in XCode, developer.apple.com's "Certificates, Identifiers & Profiles" tool created new bad certs. – Graham P Heath Dec 15 '14 at 19:00
4

Forgive my ignorance... What does this Answer have to do with the Question that was asked? It looks like you answered a different question. Or more correctly, you responded to @user3056783 deleted answer which was just an "I'm having this problem too comment". – jww Apr 15 '15 at 09:36
I had just generated a certificate in Xcode, so it may have been the same issue, though I was able to resolve it by just running a Clean. – pr1001 Apr 04 '16 at 18:12
1

That "refresh" button is now renamed to "Download All" ... :) – Thyselius Jun 06 '16 at 22:28
1

Same problem in XCode 7. Manually generate cert files at Apple developer center solved the problem for me. – JonSlowCN Jun 26 '16 at 07:52
Wow, using Xcode 9 - surprised to see this is the actual problem, but updating my certs fixed it – powerj1984 Mar 12 '18 at 14:13

DonnaLea · Answer 8 · 2015-07-30T20:59:27.457

28

I was having this issue with running my Swift tests (but not my app). It turns out that the test needed to have more than @executable_path/Frameworks in it's Runpath Search Paths build setting for the test target. Setting the Runpath Search Paths to the following worked a charm for me:

$(inherited)
@executable_path/Frameworks
@loader_path/Frameworks

edited Jul 30 '15 at 20:59

answered Jul 29 '15 at 22:15

DonnaLea

8,643
4
32
32

1

Yep this is it! Faced this for AFDateHelper.framework, Result.framework for those that Google their way here. I realised this was the solution since doing this changed the name of the framework I was receiving this error for - that was a framework I'd missed out on including in `carthage copy-frameworks` since it was a secondary dependency (one that a framework I was using had added) – Angad Jun 23 '16 at 14:28
2

Hallelujah! God bless you DonnaLea. That's just ended a 3 hour struggle. – Adam Waite Jan 30 '18 at 16:06
Brilliant. Just what I was looking for. – gran_profaci Aug 23 '18 at 00:23

score 25 · Answer 9 · answered May 15 '15 at 05:39

25

OK, sharing here another cause of this error. It took me a few hours to sort this out.

In my case the trust policy of my certificate in Keychain Access was Always Trust, changing it back to defaults solved the problem.

In order to open the certificate settings window double click the certificate in the Keychain Access list of certificates.

enter image description here

answered May 15 '15 at 05:39

nalexn

10,615
6
44
48

It worked for me as well. I was using pods to include PubNub and AWS sdks. I have tried using different methods like changing 'Runpath Search Paths' It was already set to value mentioned in above answer. Marked yes to Embed swift code in build settings but did not work. Finally this solution worked for me. Cheers. – Ehsan Jun 30 '16 at 00:15
1

Worked for me. I would never have suspected something like this. Thanks a lot. – Pierre-Yves Aug 26 '16 at 08:55
I tried every solution above this and this was the nail in the coffin. I'm not sure if I needed a combination of all of them, but this was the winner for me. To be clear, the ones I did were: Cleaning the proj, include load_path in Runpath search paths, moved distribution cert from system to login keychain, set Always embed swift standard libraries to yes, "untrusted" the cert (set it back to system default trust). – Nick Molyneux Nov 15 '16 at 18:24
Holy molly... Thanks a lot! – Ethenyl Nov 13 '17 at 13:28

score 23 · Answer 10 · edited Apr 11 '19 at 04:59

23

This issue occurs again in Xcode 10.2. You must download and install the following package from Apple. It provides Swift 5 Runtime Support for Command Line Tools.

https://support.apple.com/kb/DL1998?locale=en_US

edited Apr 11 '19 at 04:59

codeherk

1,609
15
24

answered Apr 08 '19 at 11:26

Jim Bray

758
8
12

I was getting dyld: Symbol not found: _$s11SubSequenceSlTl. This works – Aditya Deshmane Apr 19 '19 at 05:56
Great! Solved with this – Roran Jun 05 '19 at 15:57
Works! This reminds me of old time windows programming when you needed to install the redistributable visual c++ `msvcrt.dll` – mcatach Jun 19 '19 at 16:57
Thanks! Tried everything else and this was it. – Silverstar Aug 19 '19 at 04:35

score 20 · Answer 11 · answered Jan 19 '16 at 17:31

20

You have to set the Runpath Search Paths to @executable_path/Frameworks as showed in the following screenshot of Build Settings:

If you have any embedded frameworks made in Swift, than you can set to YES the Build Options Embedded Content Contains Swift Code.

answered Jan 19 '16 at 17:31

loretoparisi

15,724
11
102
146

1

YES, for framework in swift, setting "Embedded Content Contains Swift Code" to YES is necessary – david Jun 24 '16 at 04:16
I made a command line tool that uses some dylibs that are to be delivered along with the tool in a local directory (and not in /usr/lib or something like that). `otool -L` for these dylibs told me that they were already using `@rpath/...` for their own path. Now, by setting the *Runpath Search Path* to the path of that folder, I can run my tool and it'll find the dylibs that are stored in a folder next to it. – Thomas Tempelmann Mar 24 '17 at 22:00
When trying to add a Swift module into a React Native project, it was instead failing to find `@rpath/libswiftAppKit.dylib`. An [issue](https://github.com/krzyzanowskim/CryptoSwift/issues/137) lead me to learn that I had to add the searchpath: `@executable_path/../Frameworks/` based on [these instructions](https://github.com/kylef/Commander/blob/master/README.md#installation). Whether this applies only to my project structure, I can't say. Of note, I did not have to clean DerivedData for this setting to take effect! – Jamie Birch May 19 '18 at 11:02

flatronka · Answer 12 · 2015-10-24T13:37:34.997

I think Apple has already summarized it under Swift app crashes when trying to reference Swift library libswiftCore.dylib

Cited from Technical Q&A 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.

As the AirSign guys state the problem roots from the missing OU attribute in the subject field of the In-House certificate.

Subject: UID=269J2W3P2L, CN=iPhone Distribution: Company Name, OU=269J2W3P2L, O=Company Name, C=FR

I have an enterprise development certificate, creating a new one solved the issue.

After spending many many hours trying to understand why my new CI setup was not able to properly publish a beta app (enterprise account, indeed), I figured out that in the export options, compileBitcode MUST be true. — gderaco, Nov 20 '17 at 18:33

score 10 · Answer 13 · answered Apr 19 '16 at 05:17

10

Let's project P is importing custom library L, then you must add L into

P -> Build Phases -> Embed Frameworks -> +. That works for me.

answered Apr 19 '16 at 05:17

Sazzad Hissain Khan

37,929
33
189
256

score 9 · Answer 14 · answered Jul 03 '18 at 03:11

9

The most easy and easy to ignored way : clean and rebuild.

This solved the issue after tried the answers above and did not worked.

answered Jul 03 '18 at 03:11

Michael Yang

1,403
2
18
27

Worked for me, thanks! (seeing how simple this way, I tried it first, before the other answers above; thanks for saving my time!) – auspicious99 May 01 '23 at 03:46

score 8 · Answer 15 · answered Sep 28 '17 at 07:12

8

This error message can also be caused when upgrading Xcode (and subsequently to a new version of Swift) and your project uses a framework built/compiled with an older/previous version of Swift.

In this case rebuilding the framework and re-adding it will fix the problem.

answered Sep 28 '17 at 07:12

Paul Popiel

930
11
21

This happened to me, going from Xcode 9.2 to 9.3. Though I didn’t discover it until long after the upgrade, because as long as the project has been built using Xcode 9.2 previously, it continues to work indefinitely with Xcode 9.3. Only after doing a clean checkout did I discover this. – Svein Fidjestøl May 14 '18 at 07:45
I don't think this answer is rated high enough. Using Carthage and an updated version of Xcode gets installed, you need to rebuild your Carthage libraries to make this issue go away. – Darren Apr 29 '19 at 20:19

score 7 · Answer 16 · edited May 23 '17 at 11:47

7

I was having the same problem after moving to a new mac, and after hours, trying all the suggested answers in the questions, none of this worked for me.

The solution for me was installing this missing certificate. http://developer.apple.com/certificationauthority/AppleWWDRCA.cer

Found the answer here. https://stackoverflow.com/a/14495100/976628

edited May 23 '17 at 11:47

Community

1
1

answered Oct 15 '15 at 16:25

Bruno Coelho

926
13
25

score 6 · Answer 17 · answered Nov 25 '15 at 07:58

6

Change Copy Pods Resources for the target from:

"${SRCROOT}/Pods/Target Support Files/Pods-Wishlist/Pods-Wishlist-resources.sh"

to:

"${SRCROOT}/Pods/Target Support Files/Pods-Wishlist/Pods-Wishlist-frameworks.sh"

answered Nov 25 '15 at 07:58

Bartłomiej Semańczyk

59,234
49
233
358

1

Unless this has broken something else, this has been the fix for me! – RealCasually Nov 25 '15 at 18:24
What else that thing has broken? Can you help me improve the answer? – Bartłomiej Semańczyk Nov 25 '15 at 22:29
It seems to work with the exception being running 'pod install' overwrites the change. – RealCasually Nov 25 '15 at 23:01
@RealCasually you are right Is there a way to prevent from overwriting this or any workaround? – Bartłomiej Semańczyk Feb 03 '16 at 13:38
OMG. this was the problem for me after trying 100 other things and 4 hours of monkeying. What exactly happens in the framework.sh vs resources.sh? – kennydust Apr 25 '16 at 15:20
Works for me, but would be great to include an explanation of why this works. – Simo Nov 29 '16 at 11:26
to avoid it getting overwritten, change its name - the next pod install will generate it new Copy Pods Resource step – Radu Simionescu Mar 30 '18 at 16:07

score 6 · Answer 18 · edited May 25 '16 at 21:08

6

I solved by deleting the derived data and this time it worked correctly. Tried with Xcode 7.3.1GM

edited May 25 '16 at 21:08

Stu P.

1,365
1
14
31

answered Apr 24 '16 at 13:58

WhiteTiger

1,691
1
18
23

Deleting my derived data also worked, I did a clean (CMD+K) beforehand anyways just in case and the error died a painful death! – Stu P. May 25 '16 at 21:06

score 5 · Answer 19 · answered Nov 11 '15 at 13:20

After having tried out everything, I finally found out, that the build seems not always include every detail again and again. Maybe for speeding up the process... In order to ensure WHOLE packaging before running on a device, make a Clean first: Shift-Cmd-K. Then build with: Cmd-B. After that run it on your device. Easy. Kind regards to all you nice guys in that place!

Guy · Answer 20 · 2020-05-21T13:47:58.147

We had a unity project that creates an xcode project that includes libraries that use swift.

We tried each and every reasonable suggestion on this thread.

Nothing worked. Code runs fine on new devices, and crashes on iOS<=12

It seems that swift is so smart, that even if you set it to "ALWAYS_EMBED_SWIFT_LIBRAIES"="YES" it does not include the swift libraries.

What actually solved the problem for us is to include a dummy swift file in the project. The file must contain calls to dispatch, foundation libraries.

Apparently this hints mighty-xcode to force include the libraries, but this time for real.

Here is the dummy file we added that made it work:

import Dispatch
import Foundation


class ForceSwiftInclusion {

   init() {

    // Force dispatch library.
    DispatchQueue.main.async {
      print("something")
    }

    // Force foundation library.
    let uuid = UUID().uuidString
    print("\(uuid)")

   }
}

For unity, also add project.AddBuildProperty(target, "SWIFT_VERSION", "Swift 5"); to your post processing for creating the xcode project.

you sure about the "Swift 5" isn't it "5.0" instead ? – Romain Bitard Mar 30 '23 at 22:21 — Romain Bitard, Mar 30 '23 at 22:21

score 5 · Answer 21 · answered Sep 19 '22 at 08:01

I had the same issue for Xcode 13+ when I create a release build. Had to waste my time on troubleshooting this issue. Finally I was able to fix the issue with following step.

I added a new entry for Release in Runpath Search Paths in Build Settings -> Linking.

/usr/lib/swift

After adding that, I could run my app without crashing!

score 4 · Answer 22 · answered Apr 21 '15 at 03:35

In my case, it was just the name of my target :

I renamed it like this : MyApp.something and the same issue appeared. But I saw in the build Settings window, my product module name has been changed like this MyApp-something. So, I removed the dot in my target name (MyAppSomething) and the issue was gone.

score 4 · Answer 23 · answered Aug 21 '15 at 12:00

4

For me, having tried everything with no success, what worked was to remove @executable_path/Frameworks from the Packaging section (don't know how it came to be in there in the first place)

answered Aug 21 '15 at 12:00

abinop

3,153
5
32
46

is this for the framework path or for the main project settings path ? – ZeeroCool77 Jan 11 '16 at 15:35
I had one project static lib a and wanted to add swift fw into it. This instruction together with Embedded Contain Contains Swift to Yes code resolved all problems. – mauron85 Jun 14 '16 at 00:23
This seems to have broken my project. – UKDataGeek Dec 29 '16 at 18:33

score 4 · Answer 24 · answered Jun 01 '20 at 19:39

4

What worked for me in Xcode 11 was going to General -> Frameworks, Libraries, and Embedded Content and changing the "Embed" option for the framework in question to "Embed & Sign"

answered Jun 01 '20 at 19:39

Michael

748
8
11

1

Thank you...you saved me today.. – Sourabh Sharma Nov 23 '21 at 12:08

score 3 · Answer 25 · answered Dec 02 '15 at 00:52

3

None of the solutions worked for me. Restarting the phone fixed it. Strange but it worked.

answered Dec 02 '15 at 00:52

newDeveloper

1,365
1
17
27

score 3 · Answer 26 · edited May 23 '17 at 12:10

3

none of these solutions seemed to work but when I changed the permission of the world Wide Developer cert to Use System defaults then it worked. I have included the steps and screenshots in the link below

I would encourage you to log the ticket in apple bug report as mentioned here as Apple really should solve this massive error: https://stackoverflow.com/a/41401354/559760

edited May 23 '17 at 12:10

Community

1
1

answered Dec 30 '16 at 19:04

UKDataGeek

6,338
9
46
63

score 2 · Answer 27 · answered Dec 30 '15 at 03:54

2

Xcode 7.2, iOS 9.2 on one device, 9.0 on other. Both had the error. No idea what changed that caused it, but the solutions above for the WWDR were correct for me. Install that cert and problem solved.

https://forums.developer.apple.com/message/43547 https://forums.developer.apple.com/message/84846

answered Dec 30 '15 at 03:54

HG123

31
7

While this link may answer the question, it is better to include the essential parts of the answer here and provide the link for reference. Link-only answers can become invalid if the linked page changes. - [From Review](/review/low-quality-posts/10722641) – Bartłomiej Semańczyk Dec 30 '15 at 08:33
2

Apologies. Download the WWDR certificate and then open it to install into your keychain. Certificate is here: http://developer.apple.com/certificationauthority/AppleWWDRCA.cer – HG123 Dec 30 '15 at 15:59

score 2 · Answer 28 · answered Jan 17 '17 at 11:46

There are lot's of answers there but might be my answer will help some one.

I am having same issue, My app works fine on Simulator but on Device got crashed as I Lunches app and gives error as above. I have tried all answers and solutions . In My Case , My Project I am having multiple targets .I have created duplicate target B from target A. Target B works fine while target A got crashed. I am using different Image assets for each target. After searching and doing google I have found something which might help to someone.

App stop crashing when I change name of Launch images assets for both apps . e.g Target A Launch Image asset name LaunchImage A . Target B Lunch Image asset name LaunchImage B and assigned properly in General Tab of each target . My Apps works fine.

score 2 · Answer 29 · answered Sep 01 '18 at 10:02

For me building a MacOS command line Swift app that depended on 3rd party Swift libs (e.g. SQLite) none of the above solutions seemed to work. What did work was directly adding the following path to my Runpath Search Paths in the Build Settings:

/Applications/Xcode.app/Contents//Developer/Toolchains/XcodeDefault.xctoolchain/usr/lib/swift/macosx/

Doing that did give a warning at runtime saying that Xcode had found 2 versions of libswiftCore - which makes sense. Except that not including that line resulted in Xcode not finding any versions of libswiftCore.

Anyway, that'll do for me even if it doesn't seem right - my app is just a utility that I'm not intending to distribute and at least it runs now!

Thank you! I'm in your situation and this worked for me as well. — Joris Weimar, Mar 12 '19 at 09:28

score 1 · Answer 30 · answered Apr 26 '16 at 08:10

I have multiple version of Xcode installed at the same time. The framework was built with a newer version of Xcode. The app that I tried to compile was with an older version of Xcode. When I cleaned and compiled both the framework and the app with the same version of Xcode then things worked.

score 1 · Answer 31 · edited Nov 17 '16 at 23:44

I started getting this similar error for testing adding S3 file using AWS services. Below was the error. dyld: Library not loaded: @rpath/AWSAutoScaling.framework/AWSAutoScaling

I searched a lot and above solutions are also not helpful for me. Below link helped me to solve this issue.

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

Which says to fix this issue by re-downloading the WWDR (Apple Worldwide Developer Relations Certification Authority).

score 1 · Answer 32 · answered May 05 '17 at 00:36

1

I am on Xcode 8.3.2. For me the issue was the AppleWWDRCA certificate was in both system and login keychain. Removed both and then added to just login keychain, now it runs fine again. 2 days lost

answered May 05 '17 at 00:36

Max

3,371
2
29
30

Can you spare just a little more detailed answer? Where do you find it (the certificate) - I guess what you wrote stands for Apple Worldwide Developer something... but what's the full name? how to re-add it after you completely removed it from all key-chains? Where do you find this certificate? – Motti Shneor Oct 24 '17 at 16:26

Matt Bearson · Answer 33 · 2018-01-24T18:12:25.887

1

I'm using Xcode 8.3.3 and Xcode 9.2. The solution for me was to switch my default Xcode from 8 to 9 using Xcode Select:

$ xcode-select --print-path

$ sudo xcode-select -switch /Applications/Xcode-9.2.app

Edit: Actually what seemed to help here was that Xcode 9.2 used the derived data from Xcode 8.3.3. Not a solution but at least it allows me to move forward with my work.

edited Jan 24 '18 at 18:12

answered Jan 24 '18 at 17:06

Matt Bearson

993
8
15

I tried this issues occur but when i quit and restart xcode it works. :). Nice try – Abhishek Thapliyal Apr 13 '18 at 06:40

score 1 · Answer 34 · answered Aug 09 '19 at 03:30

If you're getting an error like this:

The bundle "YourFrameworkTests" couldn't be loaded because it is damaged or missing necessary resources. Try reinstalling the bundle. (dlopen_preflight(/some/path/.../YourFrameworkTests.xctest/YourFrameworkTests): Library not loaded: @rpath/SomeOther.framework/SomeOther Referenced from: /some/path/...)

and use CocoaPods in your framework, then try to edit the Podfile and remove inherit! :search_paths from the Test target, and run pod install again.

For more details, see https://github.com/CocoaPods/CocoaPods/issues/8868.

score 1 · Answer 35 · answered Nov 26 '19 at 15:01

1

I ran into this issue while I was trying to run unit-tests on a private pod.

I did everything everyone suggested. Nothing worked.

All I had to do was to run my unit-tests on a different simulator.

_{I didn't try resetting the contents and settings of my simulator, maybe that would have worked as well ¯_(ツ)_/¯}

answered Nov 26 '19 at 15:01

mfaani

33,269
19
164
293

Magic!! This one worked for me. I really tried all answers post on STO but none worked. – Jayprakash Dubey Oct 13 '20 at 11:10
FWIW I’m not sure if the simulators had different iOS versions or if they were the same – mfaani Oct 13 '20 at 12:44

score 1 · Answer 36 · edited Mar 04 '21 at 07:26

1

For Xcode 12.x, what worked for me is go to General > Frameworks, Libraries, and Embedded Content. Then, choose Embed & Sign all Agora frameworks. (it was defaulted to Do Not Embed.

edited Mar 04 '21 at 07:26

Dharman

30,962
25
85
135

answered Mar 04 '21 at 07:20

Jemzzzz

129
9

score 1 · Answer 37 · answered Dec 09 '21 at 06:01

1

For me none of above solutions worked.

I managed to get rid of the issue by creating an empty swift file inside my project. After that do a clean build and everything just worked!

Hope this helps others.

Tested on iOS 15 & React Native 0.66

answered Dec 09 '21 at 06:01

eggsloveoats

453
4
14

score 1 · Answer 38 · answered Apr 04 '22 at 23:45

1

I tried to read through all the answers. (Maybe missed some) But here is my solution. Might be helpful to someone. I just created a swift file (void.swift) in my project. When I added this file, it asked me to create a bridge. I said yes. That's all! It started working. Background: My project is written in obj c. And I added FBSDK pods to my project. After that, I started getting this error.

answered Apr 04 '22 at 23:45

Harshal Karande

476
4
9

Genius! It helped (though i'm using react native) – Sergii Feb 10 '23 at 18:36

score 0 · Answer 39 · answered Oct 06 '15 at 18:37

To add on to the Enterprise distribution cert solution: you can open Keychain and inspect the cert. If there is any red text saying the trust chain can't be verified or it being revoked, it WILL NOT WORK! On my computer, our distribution cert was showing as revoked even though the web portal showed it as still valid. We got a new distribution cert, which was green (valid) in Keychain, and this solved the issue.

score 0 · Answer 40 · answered Nov 15 '15 at 19:22

The above solutions did not work for me. I fix the issue by the following steps:

I had to go to the phone (Settings > Profile) and delete the profiles that were in the phone(including all the apps associated with those profile/provisions).
After that, make sure that you download the apple provisions in xcode. Go to xcode settings > account and sign in into your apple developer account.

score 0 · Answer 41 · answered Jan 12 '16 at 23:15

0

I'm using Xcode 7.2. If you tried all of above and the error still occurs, try deleting the old certificate from Keychain Access! It's such a pain to finally fix this.

answered Jan 12 '16 at 23:15

Maggie

1
1

score 0 · Answer 42 · answered Jan 13 '16 at 12:05

0

In my case,

I have set @executable_path/Frameworks

But I have to also set "Framework search paths"

$(PROJECT_DIR)/Frameworks

change as recursive

Which works for me.

answered Jan 13 '16 at 12:05

Max

2,269
4
24
49

score 0 · Answer 43 · answered Feb 23 '16 at 07:27

When Xcode asks you to reset certs, you reset it. And the app can be run on actual device without crash with that error messages. Once this problem is fixed in one swift project. Other swift projects with this problem are fixed also.

I have struggled for these about half a day and I found that reset certs again and again in provisioning portal doesn't help.

score 0 · Answer 44 · answered May 13 '16 at 17:20

In my case, one of my testing targets was working but the other one was not. It was giving the above error with a missing library or whatever. I compared the settings for both of the testing targets and found that one was missing the configuration for "Test Host", so I copied that from the working test target and it fixed my broken test target!

score 0 · Answer 45 · answered Jun 16 '16 at 09:14

0

From the post of https://github.com/CocoaPods/cocoapods-integration-specs/pull/24/files, that mean swift.dylib need sign but failed. I failed even create a new swift project with cocoapod support.

answered Jun 16 '16 at 09:14

BollMose

3,002
4
32
41

score 0 · Answer 46 · answered Jul 15 '16 at 21:37

0

If your project has cocoapods and different schemes, try running pod update, that fixed it for me.

answered Jul 15 '16 at 21:37

gmogames

2,993
1
28
40

score 0 · Answer 47 · answered Aug 17 '16 at 14:10

Shortly speaking, have you tried to check "Enable Bitcode=NO". It works for me.

In my case, my project was written in Object-C and includes one 3rd party framework written in swift. I can run my APP on both simulator and real device in developer mode. However, once I achieved the APP with Ad-hoc provision profile and installed this ipa OTA on real device, it crashed. Not even mention upload to store. Hope this information can help.

score 0 · Answer 48 · answered Dec 12 '16 at 11:02

I have the same issue, and the issue is like this:

dyld: Library not loaded: @rpath/Result.framework/Result Referenced from: /private/var/mobile/Containers/Bundle/Application/74AD1FE2-7095-47D2-B059-520863050EE2/ReactiveCocoaTest.app/Frameworks/ReactiveCocoa.framework/ReactiveCocoa Reason: image not found

My solution is below:

In the TARGET -> Build Setting -> Other Linker Flag -> delete the ReactiveCocoa framework. If is xxx.framework, you know, you should delete the xxx.

delete the ReactiveCocoa

score 0 · Answer 49 · answered Nov 11 '19 at 06:30

I tested all of the above solutions but nothing solved the problem. I was using Xcode 10.2 and macOS 10.14.3. first i installed swift 5 runtime support for command line tools but nothing changed second i updated OS to 10.14.4 and nothing changed third i updated Xcode to 11.2.1 and the problem solved (do not user Xcode 11.2. it has archiving issue and deprecated)

score 0 · Answer 50 · answered Feb 24 '20 at 04:07

0

Got the same issues after two years. I think this post explains the reason I got (But may be not the reason in this question). Use subscribed developer account or static libraries could help. Like remove use_frameworks! in your Podfile .

answered Feb 24 '20 at 04:07

Diya Li

1,048
9
21

score 0 · Answer 51 · answered May 01 '20 at 09:44

0

In my case, This is a bug of the early version iOS13.

https://forums.developer.apple.com/thread/128435

kambala

Mar 25, 2020 12:41 AM

FYI this is fixed in 13.4 release

answered May 01 '20 at 09:44

shingo.nakanishi

2,045
2
21
55

score 0 · Answer 52 · answered Mar 09 '21 at 13:14

I am having same issue

There are lot's of answers there but might be my answer will help some one.

// MARK: - Core Data stack

 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
        }()

score 0 · Answer 53 · answered Nov 12 '21 at 07:45

Me also got the exact same error in Xcode 13, iOS 12 mobile.

Here my project deployment info is 12.0, but my framework deployment info in iOS 15.0.

I have changed my Framework deployment info into 12.0.

Conclusion:

Which means framework and project supported versions issue. We need to fix the framework minimum support version after creating the framework.

score 0 · Answer 54 · answered Jan 11 '22 at 13:37

Nothing worked for me, then i did these steps below:

I removed the flipper usage from podfile. It looked like this for me:

use_flipper!({ 'Flipper-Folly' => '2.5.3', 'Flipper' => '0.87.0', 'Flipper-RSocket' => '1.3.1' })
I added a swift file in my project to create a bridging header.

score 0 · Answer 55 · answered Apr 08 '23 at 05:25

0

In addition to previous answers (setting Runpath Search Paths) my solution was in increasing iOS Deployment Target from 11.0 to 12.4.

answered Apr 08 '23 at 05:25

deko

2,534
3
34
48

score 0 · Answer 56 · answered Aug 15 '23 at 20:28

In my case, I was trying to resolve an issue that is happening in iOS 14. So I downloaded iOS 14.0 for my simulator in Xcode settings. In that case, I encountered the same problem as the author mentioned.

No matter how many times I applied the suggested answers, it didn't work for me.

Then I simply downloaded iOS 14.1 version and deployed my code with it. Problem solved!

The good news is that our app was behaving the same with iOS 14.1 so that we could reproduce the issue and fix the bug.

score -1 · Answer 57 · answered Nov 11 '15 at 09:56

Following these steps worked for me:

Click on your project name (very top of the navigator)
Click on your project name again, (not on target)
Click the tab Build Settings
Search for Runpath Search Paths
Change its value to $(inherited) flag (remove @executable_path/Frameworks).

score -1 · Answer 58 · answered Dec 27 '17 at 07:15

-1

For me solution is here below Disable the "Embed Asset Packs in Product Bundle" and this issue will be gone

answered Dec 27 '17 at 07:15

ashish.surana

130
3
13

score -1 · Answer 59 · answered Oct 08 '22 at 03:10

-1

For me, I forget add two lines of code below to target 'Runner' do in Podfile

target 'Runner' do
   use_frameworks!
   use_modular_headers!
end

Add these codes solved, wish to help you!

answered Oct 08 '22 at 03:10

Story5

142
1
1
9

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

59 Answers59

I have an enterprise development certificate, creating a new one solved the issue.

Linked

Related