dyld: Library not loaded ... Reason: Image not found

Question

When trying to run an executable I've been sent in Mac OS X, I get the following error

dyld: Library not loaded: libboost_atomic.dylib
  Referenced from: /Users/"Directory my executable is in"
  Reason: image not found
Trace/BPT trap:5

I have installed the boost libraries and they are located in /opt/local/lib. I think the problem has something to do with the executable only looking in the directory it is in as when I paste the 'libboost_atomic.dylib' in there, it doesn't mind about it anymore. Unfortunately then it complains it can't find the next boost library.

Is there an easy way to fix this?

If you still has problem use method from this [topic](http://stackoverflow.com/questions/27116371/dyld-library-not-loaded-reason-no-suitable-image-found/43466989#43466989) — Tarik, May 15 '17 at 09:23
Try to uninstall python3.7.3 using this:- https://huybien.com/how-to-completely-uninstall-python-on-macos/ — Mr.Das, Feb 16 '21 at 06:25

score 216 · Accepted Answer · edited Sep 14 '21 at 14:51

216

Find all the boost libraries (where exefile is the name of your executable):

$ otool -L exefile
exefile:
        @executable_path/libboost_something.dylib (compatibility version 0.7.0, current version 0.7.0)
        /usr/lib/libc++.1.dylib (compatibility version 1.0.0, current version 65.1.0)
        /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 169.3.0)

and for each libboost_xxx.dylib, do:

$ install_name_tool -change @executable_path/libboost_something.dylib /opt/local/lib/libboost_something.dylib exefile

and finally verify using otool again:

$ otool -L exefile
exefile:
        /opt/local/lib/libboost_something.dylib (compatibility version 0.7.0, current version 0.7.0)
        /usr/lib/libc++.1.dylib (compatibility version 1.0.0, current version 65.1.0)
        /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 169.3.0)

Manpages: otool install_name_tool

EDIT A while back I wrote a python script (copy_dylibs.py) to work out all this stuff automatically when building an app. It will package up all libraries from /usr/local or /opt/local into the app bundle and fix references to those libraries to use @rpath. This means you can easily install third-party library using Homebrew and package them just as easily.

I have now made this script public on github.

edited Sep 14 '21 at 14:51

Alex Shroyer

3,499
2
28
54

answered Jul 17 '13 at 15:40

trojanfoe

120,358
21
212
242

5

@trojanfoe can you please explain here what is the exefile is it be a tool exec file path ? isnt it ? – VenushkaT Dec 02 '14 at 05:30
2

After recompiling the executable I have to repeat this process - quite annoying during development. – tglas Sep 14 '17 at 18:54
5

Actually the better way is to use `DYLD_LIBRARY_PATH` to modify the search path. The other answer has got this. – frankliuao May 27 '18 at 21:42
37

'exefile': No such file or directory – ScottyBlades May 29 '18 at 07:38
9

@ScottyBlades `exefile` stands for the executable file you're trying to run. In my case, `otool -L /usr/local/bin/php` did the trick. – brunouno Nov 25 '18 at 04:36
Thanks! Worked for me when Homebrew messed up bash. In my case I needed to run `install_name_tool` as root to get over the issue. This one-liner inspects all the dylibs for a binary: `otool -L /usr/local/bin/bash | awk -F' ' '{print $1}' | tail -n +2 | xargs -I{} ls {}` – Matt Kneiser Dec 27 '19 at 21:53
Here's the other way. Please take a look. https://github.com/eXolnet/homebrew-deprecated/issues/27 – YuAn Shaolin Maculelê Lai Jan 14 '21 at 09:12
@YuAnShaolinMaculelêLai Sorry I don't understand what you mean. – trojanfoe Jan 14 '21 at 10:35
1

@frankliuao - Which answer exactly is the "other answer"? – Security Hound Nov 25 '22 at 23:23
@SecurityHound [This is the one](https://stackoverflow.com/a/35027026/2988929). – frankliuao Nov 27 '22 at 17:03
Using DYLD_LIBRARY_PATH doesn't seem to work for me. Thankfully install_name_tool does. – Sridhar Sarnobat Feb 07 '23 at 04:22

score 165 · Answer 2 · answered May 09 '18 at 20:14

165

This worked for me:

brew upgrade node

answered May 09 '18 at 20:14

oshaiken

2,593
1
15
25

14

What is this doing, though? – diegoaguilar Jun 01 '19 at 04:45
7

@diegoaguilar this is reinstalling `node` using homebrew. Probably another installation broke node path. Also worked for me. – Hugo Nogueira Aug 15 '19 at 14:25
It worked for me after updating macOS Catalina. Thanks! – Cadu De Castro Alves Jul 10 '20 at 09:42
Same here, I fixed it with `brew upgrade node` (OSX Catalina) – inaki Mar 10 '21 at 08:46
This should be the accepted answer. Save most people a lot of hassle. – Jeremy Moritz Oct 28 '21 at 16:17
@JeremyMoritz Except that the question doesn't even mention `node` and is not tagged with `node`. It's an answer to a different question. – trojanfoe Nov 09 '21 at 10:21
This worked for my Mac OSX Catalina – Mike En Aug 23 '23 at 15:22

Himanshu padia · Answer 3 · 2020-01-29T06:17:31.533

126

In the target's General tab, there is a section called Frameworks, Libraries, and Embedded Content

Click on the + sign, add required framework and the crash is resolved.

edited Jan 29 '20 at 06:17

answered May 10 '16 at 07:22

Himanshu padia

7,428
1
47
45

3

what should i add ? there's a lot of files – Joe Sleiman Jan 08 '19 at 08:15
@Himanshu I have libcppreset for my project! it has a lot of dependency from boost and ... I run a bash script to change them with install_name_tool but for the `LC_ID_DYLIB` I can't so need to make a symlink in usr/loca/opt ! is there any way to figure out ? :| It's painfull :( – Mo Farhand Mar 26 '20 at 23:14
Add the framework and set the framework to `Embed & Sign` – desu sai venkat Oct 07 '21 at 07:46
I just removed and added again the library and it worked – Khaled Annajar Aug 22 '22 at 13:38

Michael Klishevich · Answer 4 · 2020-02-07T10:13:59.437

113

After upgrade Mac OS to Mojave. I tried to install npm modules via yarn command I got error:

dyld: Library not loaded: /usr/local/opt/icu4c/lib/libicui18n.60.dylib
  Referenced from: /usr/local/bin/node
  Reason: image not found
Abort trap: 6

Was fixed with:

brew update
brew upgrade

edited Feb 07 '20 at 10:13

answered Jan 07 '19 at 10:39

Michael Klishevich

1,774
1
17
17

2

My intelliJ started throwing this error when I recently updated xcode. I was trying to run a node.js server through intellij. I wasn't sure what went wrong. Running `node --version` on my system resulted in the same error. Running the above two commands solved my problem. – Ishan Dec 16 '19 at 09:31
5

In my case, I also ran the `brew cleanup` command, which is good to do at times if you want to get rid of old versions. – Michael Behrens Dec 28 '19 at 17:26
Regarding to @MichaelBehrens's comment, I run `brew cleanup` then it fixed. – Buraco May 01 '20 at 14:19

score 45 · Answer 5 · edited May 23 '17 at 11:55

45

For some, this could be as easy as setting the system path for dynamic libraries. On OS X, this is as simple as setting the DYLD_LIBRARY_PATH environment variable. See:

Is it OK to use DYLD_LIBRARY_PATH on Mac OS X? And, what's the dynamic library search algorithm with it?

edited May 23 '17 at 11:55

Community

1
1

answered Jan 27 '16 at 01:04

markshiz

2,501
22
28

4

It may seem stupid, but I wonder what value should I set `DYLD_LIBRARY_PATH` to? – Leo Mar 21 '17 at 01:13
2

@Caesar Set it to the directory of wherever the dylibs you're trying to link are located. – markshiz May 02 '17 at 14:01
1

You cannot expect your users to change `DYLD_LIBRARY_PATH`. The correct solution is to include non-standard libraries with the `.app` and the user won't have to do anything. The developer, however, may still have to hack the loader path as per my answer. – trojanfoe Feb 04 '19 at 08:00
@trojanfoe .app? Have a test executable, trying to link some .dylib . Linux is same with LD_LIBRARY_PATH – Sam Ginrich Apr 25 '22 at 14:26
So easy. Thank you! Wonder, what other answers are about, and how brew would do a similair thing ... – Sam Ginrich Apr 25 '22 at 14:29

score 39 · Answer 6 · answered Jun 20 '20 at 08:39

39

this should fix the issue

brew update
brew upgrade
brew cleanup

answered Jun 20 '20 at 08:39

Walterwhites

1,287
13
9

Using this worked for me, unfortunately, I still don't know what cause of the issue to begin with or why updating, upgrading and cleaning up solve the issue – Onema Jun 27 '20 at 19:36
2

this worked totally for me, however, while trying to do the cleanup, i ran into some permission issue, if you also have this trouble, try running sudo chown -R $(whoami) /usr/local/lib then try running the brew cleanup again – Pianistprogrammer Jun 29 '20 at 07:08
I still get `ImportError: cannot import name 'ssl' from 'urllib3.util.ssl_' (/Users/foo/.local/share/virtualenvs/TMIWqqTS/lib/python3.7/site-packages/urllib3/util/ssl_.py) ` after running this – Harry Moreno Jul 01 '20 at 05:44
I fixed my follow up error by reinstalling python. I use asdf to manage my language versions so I did `asdf uninstall python 3.7.3` (I was using 3.7.3, specify here the version you have) and then ran `asdf install python 3.7.3`. – Harry Moreno Jul 01 '20 at 05:54
if till not work : brew services start php – shorol Mar 18 '21 at 10:22
I had to follow this as well: https://stackoverflow.com/a/72820874/3342981 – user3342981 Nov 01 '22 at 16:26

score 12 · Answer 7 · edited Mar 20 '17 at 10:18

12

I got this error when I tried to install ruby 2.3.1 using rvm. It first told me to run brew update, which I did, and then when I tried running rvm install ruby-2.3.1, I received the error in this SO question.

The fix was to first run brew upgrade, apparently according to this superuser.com question you need to do both brew update && brew upgrade. Once that was done, I could finally install ruby 2.3.1.

edited Mar 20 '17 at 10:18

Community

1
1

answered Oct 21 '16 at 11:41

JackDev

4,891
1
39
48

2

People need to stop recommending doing `brew upgrade` just like that. This can be a massive disruptor for one's entire system. Instead, isolate what needs to be upgraded and upgrade that only. – Jivan Apr 12 '20 at 11:25

score 12 · Answer 8 · edited Nov 07 '19 at 07:13

Now that Xcode has upgraded their IDE, they have changed a little bit how this functions.

It used to be split up into separate section as demonstrated above with 'Embedded Binaries' and 'Linked Frameworks and Libraries' as separate sections.

Now, it is one combined section with drop-downs on the right as to what should be embedded.

This was confusing to me at first, but makes perfect sense now.

score 11 · Answer 9 · answered Nov 30 '19 at 18:48

11

If you're using Xcode 11 onwards:

Go to General tab and add the framework in Frameworks, Libraries, and Embedded Content section.

Important: By default it might be marked as Do Not Embed, change it to Embed Without Signing like shown in the image and you are good to go.

For Xcode versions below 11:

Just add the framework in Embedded Binaries section and you are done.

Cheers!

answered Nov 30 '19 at 18:48

atulkhatri

10,896
3
53
89

I had the same problem. In my case choosing "Embed & Sign" worked. – soundflix Jan 15 '23 at 11:12
Yes it depends on the library if it was signed by the developer or not. Most of the times frameworks are not signed. But there may be cases when these are signed. I also had to select 'Embed & Sign' for a Google framework. – atulkhatri Feb 02 '23 at 04:45

score 10 · Answer 10 · answered May 25 '20 at 21:35

10

To resolve the error below on my Macbook Catalina 10.15.4:

dyld: Library not loaded: /usr/local/opt/openssl/lib/libssl.1.0.0.dylib
    Referenced from: /usr/local/bin/mongoexport
    Reason: image not found
Abort trap: 6

I ran the command below and got round the problem above:

brew switch openssl 1.0.2s

answered May 25 '20 at 21:35

Kwex

3,992
1
35
28

any explanations on this would be helpful. – Ejaz Karim Nov 30 '20 at 09:08
Looks to me like the executable shouldn't even be linking against `libssl.1.0.0.dylib`, but rather `libssl.1.dylib`, which will be symlinked to the exact version on the system while maintaining API compatibility. See [this](https://www.usenix.org/legacy/publications/library/proceedings/als00/2000papers/papers/full_papers/browndavid/browndavid_html/index.html). – trojanfoe Jan 14 '21 at 10:39

score 8 · Answer 11 · answered Jul 17 '13 at 15:26

You can use the otool command with the -L option for the executable, which will display where the executable is expecting those libraries to be.

If the path to those need changing, use the install_name_tool command, which allows you to set the path to the libraries.

Pradeep Reddy Kypa · Answer 12 · 2021-03-12T00:59:12.963

7

Making the Frameworks in the Build Phases Optional worked for me.

In Xcode -> Target -> Build Phases -> Link Binary with Libraries -> Make sure the newly added frameworks if any are marked as Optional

edited Mar 12 '21 at 00:59

answered Aug 28 '20 at 01:50

Pradeep Reddy Kypa

3,992
7
57
75

Lucio Paiva · Answer 13 · 2015-06-30T21:38:45.813

5

I got here trying to run a program I just compiled using CMake. When I try to run it, it complains saying:

dyld: Library not loaded: libboost_system.dylib
  Referenced from: /Users/path/to/my/executable
  Reason: image not found

I circumvented the problem telling CMake to use the static version of Boost, instead of letting it use the dynamic one:

set(Boost_USE_STATIC_LIBS ON)

edited Jun 30 '15 at 21:38

answered Jun 30 '15 at 02:35

Lucio Paiva

19,015
11
82
104

score 3 · Answer 14 · answered Mar 16 '18 at 05:49

3

I fix it by brew install libpng

answered Mar 16 '18 at 05:49

user3835452

79
2

score 3 · Answer 15 · edited Nov 07 '19 at 07:14

If you use cmake, add DYLIB_INSTALL_NAME_BASE "@rpath" to target properties:

set_target_properties(target_dyLib PROPERTIES
        # # for FRAMEWORK begin
        # FRAMEWORK TRUE
        # FRAMEWORK_VERSION C
        # MACOSX_FRAMEWORK_IDENTIFIER com.cmake.targetname
        # MACOSX_FRAMEWORK_INFO_PLIST ./Info.plist
        # PUBLIC_HEADER targetname.h
        # # for FRAMEWORK end
        IPHONEOS_DEPLOYMENT_TARGET "8.0"
        DYLIB_INSTALL_NAME_BASE "@rpath" # this is the key point
        XCODE_ATTRIBUTE_CODE_SIGN_IDENTITY "iPhone Developer"
        DEVELOPMENT_TEAM "${DEVELOPMENT_TEAM}"
    )

or in Xcode dynamic library project Target -> Build Setting set Dynamic Library Install Name Base to @rpath

I create a cocoa framework dynamic library project, it works, and compared with my bad cmake generated project find this different, and fixed it, it works on iOS. — cn00, Feb 27 '19 at 06:54

score 3 · Answer 16 · edited Dec 18 '19 at 09:12

3

I fixed this issue by using Product > Clean Build Folder (CommandShiftK), which makes a new clean build, really odd.

edited Dec 18 '19 at 09:12

pkamb

33,281
23
160
191

answered Mar 21 '19 at 05:27

Douglas Pfeifer

147
1
8

score 3 · Answer 17 · answered Dec 18 '19 at 09:48

For my framework I was using an Xcode subproject added as a git submodule.

I believe I was getting this error because I was signing the framework with a different signing Team than my main app. (switched teams for app; forgot to switch for framework)

Solution is to not sign within the framework project. Instead, in the main app's Target > General > Frameworks, Libraries, and Embedded Content section, sign the framework via Embed & Sign.

If I select Do not Embed or Embed Without Signing I instead get the error:

FRAMEWORK not valid for use in process using Library Validation: mapped file has no cdhash, completely unsigned? Code has to be at least ad-hoc signed.

score 2 · Answer 18 · answered Dec 12 '16 at 06:39

2

You can use sudo install_name_tool -change change dylib path And sudo install_name_tool -id change dylib name

answered Dec 12 '16 at 06:39

hailuodev

764
5
9

Saranjith · Answer 19 · 2020-02-26T07:41:02.893

Xcode 11.1 & Swift 5.1

Quick Fix

First make sure that external added library has option embed is selected in General Tab, Embbed Binaries.

If still not works..

This happens because you have different, unmatched versions of libraries present.

Update the Pods

pod update

Important: Check all libraries are included in the Build Settings -> libraries and frameworks list and you have given option to embbed in the build

Just working awesome

score 2 · Answer 20 · answered Nov 26 '19 at 16:50

2

if you use virtualenv just remove the folder of your environment and recreate it with this command virtualenv --python=/usr/local/bin/python3 the_name_of_my_env

answered Nov 26 '19 at 16:50

bormat

1,309
12
16

score 2 · Answer 21 · answered Jul 06 '20 at 21:04

In our case, it's an iOS app, built on Xcode 11.5, using cocoapods (and cocoapods-binary if you will).

We were seeing this crash:

dyld: Library not loaded: @rpath/PINOperation.framework/PINOperation
  Referenced from: /private/var/containers/Bundle/Application/4C5F5E4C-8B71-4351-A0AB-C20333544569/Tellus.app/Frameworks/PINRemoteImage.framework/PINRemoteImage
  Reason: image not found

Turns out that I had to delete the pods cache and re-run pod install, so Xcode would point this diff:

bolnad · Answer 22 · 2016-04-17T11:30:27.607

For anyone coming to this page because they got this error trying to link a third party framework to their project using Xcode 6.3.1, the problem I ran into was because the library was being created with an older version of the compiler using a different version of swift. The only way to fix this for me was to re-build the framework.

Another reason you might get this is stated in an Apple technical doc..

If you are building an app that does not use Swift but embeds content such as a framework that does, Xcode will not include these libraries in your app. As a result, your app will crash upon launching with an error message looking as follows:

set the Embedded Content Contains Swift Code (EMBEDDED_CONTENT_CONTAINS_SWIFT) build setting to YES in your app

Here is the link to the full Apple doc that explains it here

score 1 · Answer 23 · answered Nov 25 '18 at 06:42

For anyone experiencing the same thing with a different library or package, @user3835452 is on the right track. I found this message while trying to run composer:

dyld: Library not loaded: /usr/local/opt/openldap/lib/libldap-2.4.2.dylib
  Referenced from: /usr/local/opt/php@7.1/bin/php
  Reason: image not found
Abort trap: 6

After trying a lot of different ways I just ran brew install openldap and it fixed it. Note that I had already ran brew update and brew upgrade but only after I manually installed openldap did it actually work.

I had a similar problem dyld: Library not loaded:/usr/local/opt/fftw/lib/libfftw3f.3.dylib. After checking many possible solutions I just did brew install fftw and it worked for me. Thanks @brunouno — Joana Carvalho, Mar 22 '22 at 15:38

score 1 · Answer 24 · answered Sep 19 '19 at 10:18

1

Is there an easy way to fix this?

I just used brew upgrade <the tool>. In my case, brew upgrade tmux.

answered Sep 19 '19 at 10:18

confused00

2,556
21
39

score 1 · Answer 25 · answered Dec 23 '20 at 11:04

1

In my case it was node that was out of date, you need to upgrade it after goin up to BigSur - brew upgrade node

answered Dec 23 '20 at 11:04

Gino

11
1

score 1 · Answer 26 · answered Apr 14 '21 at 11:29

1

As said in https://gist.github.com/berkedel/d1fc6d13651c16002f64653096d1fded, you could try

brew uninstall --ignore-dependencies node icu4c
brew install node
brew link --overwrite node

answered Apr 14 '21 at 11:29

serv-inc

35,772
9
166
188

score 1 · Answer 27 · answered Nov 03 '21 at 15:46

1

Quick Fix

Remove the pod (whose name is in the error) by commenting it in your Podfile, like #Podname
Run pod install
Uncomment the pod that you commented earlier
Run pod install again.

It worked for me and is easy to do so sharing it.

answered Nov 03 '21 at 15:46

Ammar Mujeeb

1,222
18
21

score 0 · Answer 28 · edited Nov 07 '19 at 07:16

I faced the app crash issue quoting SIGABRT error in thread.Overview of the crash is dyld library not loaded and image not found something like that.

This was seen in Xcode 9.3. The reason I found out was Xcode is not picking up libraries dynamically so I had to do it manually which solved my crash issue.

Follow the below steps:

Go to Build Phases
Hit the '+' button at the top and select "New Copy File Phase"
Select Destination as Frameworks and Hit the '+' button below to add files.
Select Add Other at below, click CMD+SHIFT+G and paste the below path, /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/lib/swift/iphoneos

Now you will be able to see some swift dylibs, Select all the swift libraries with .dylib extension and click on open.

These will get added to the embedded binaries in the general tab of app.

Create a new group in project folder and add all these libraries.

Now run your app.

score 0 · Answer 29 · answered Apr 22 '20 at 11:05

0

If you are using Conda environment in the terminal, update the samtools to solve it.

conda install -c bioconda samtools

answered Apr 22 '20 at 11:05

Shrm

426
4
8

sandroid · Answer 30 · 2020-05-17T22:06:51.130

0

Best one is answered above first check what is the output of

otool -L

And then do the following if incorrect

set_target_properties(
    MyTarget
    PROPERTIES
    XCODE_ATTRIBUTE_LD_RUNPATH_SEARCH_PATHS
    "@executable_path/Frameworks @loader_path/Frameworks"
)

And

set_target_properties(
        MyTarget
        PROPERTIES
        XCODE_ATTRIBUTE_DYLIB_INSTALL_NAME_BASE 
        "@rpath"

edited May 17 '20 at 22:06

answered May 17 '20 at 09:29

sandroid

175
1
8

score 0 · Answer 31 · answered Jul 23 '20 at 16:55

I got this error after using asdf to switch my python version. When you activate the virtualenv it gets confused.

Instead recreate the virtualenv like so

$ rm -rf venv
$ python -m venv venv

This time when you activate the virtualenv it will find the correct python.

score 0 · Answer 32 · answered Apr 06 '21 at 14:43

0

It is an dynamic linker error which links binary in load or runtime

[@rpath]

answered Apr 06 '21 at 14:43

yoAlex5

29,217
8
193
205

score 0 · Answer 33 · edited Apr 10 '21 at 10:36

0

Select your project
Go To Targets
Go To Frameworks, Libraries, and Embedded Content
Click at the + icon
You should get a prompt => Search for your missed library; -in my case was OpenSSL-.
Select it and add it.
clean your project.
Re-build.

edited Apr 10 '21 at 10:36

Suraj Rao

29,388
11
94
103

answered Apr 10 '21 at 10:28

Amir

349
3
4

score 0 · Answer 34 · answered Oct 26 '21 at 19:33

FIXED: This approach cleared this up for me with ease ...

My particular CLI tool that triggered the same issue (i.e., netdiscover), was looking for:

/usr/local/opt/libnet/lib/libnet.1.dylib

When I searched that path for, libnet.1.dylib, ls returned a file, but a newer version: libnet.9.dylib

Following the approach presented in this article, How to Fix ‘Dyld: Library not Loaded’ Error on MacOS, I was able to fix the issue by simply creating a symlink pointer to the file that the tool was looking for (i.e., libnet.1.dylib), to that of the new file version listed on my system (i.e., libnet.9.dylib), ...

ln -s /usr/local/opt/libnet/lib/libnet.9.dylib /usr/local/opt/libnet/lib/libnet.1.dylib

... now when I run the tool, it finds the dependancies it needs without complaint!, : )

--AA

Reference:

Naloiko Eugene · Answer 35 · 2022-11-26T06:30:00.910

This was my reason of the issue:

dyld: Library not loaded: /System/Library/Frameworks/AVFAudio.framework/AVFAudio   Referenced from: /private/var/containers/Bundle/Application/B6724E76-E704-46A2-8637-F43277018CE2/MyFrameworkUsageSample.app/Frameworks/MyFramework.framework/MyFramework Reason: image not found dyld: launch, loading dependent libraries DYLD_LIBRARY_PATH=/usr/lib/system/introspection DYLD_INSERT_LIBRARIES=/Developer/usr/lib/libBacktraceRecording.dylib:/Developer/usr/lib/libMainThreadChecker.dylib:/Developer/Library/PrivateFrameworks/DTDDISupport.framework/libViewDebuggerSupport.dylib

I was creating own framework MyFramework - where the Apple Framework was used. And build the xcframework with latest deployment target - iOS 16. While in the TestApp required to run on iOS 13+. And The Test Devices were using iOS 15.

Thus the TestApp with MyFramework was launching on Simulator (iOS16) successfully. But not on the Devices.

Resolution: In MyFramework - change the deployment target to needed iOS. And re-generate your framework. Or if you are using the 3d-party framework - ask the provider to support you minimal deployment target.

So missed to change the min deployment target in the xcframework before building - and Apple logs were as usual super helpful)))

score 0 · Answer 36 · answered Jan 25 '23 at 06:58

0

install_name_tool -add_rpath new_path executable install_name_tool -delete_rpath old_path executable

answered Jan 25 '23 at 06:58

user3833678

121
1
2

sidonaldson · Answer 37 · 2019-03-14T15:11:51.900

-1

I fixed this by reinstalling Homebrew

Uninstall

ruby -e "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/master/uninstall)"

Install

/usr/bin/ruby -e "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/master/install)"

edited Mar 14 '19 at 15:11

answered Mar 14 '19 at 15:02

sidonaldson

24,431
10
56
61

score -1 · Answer 38 · answered Feb 28 '20 at 18:40

-1

For anyone that might still be having this problem:

This is an ongoing problem on Apple's side, and what worked for me is upgrading to ios 13.4(beta). Installed that and worked like a charm.

answered Feb 28 '20 at 18:40

asterisk12

394
2
9

this is not IOS issue. – JBarros35 Mar 10 '20 at 15:56

score -1 · Answer 39 · answered Apr 28 '21 at 08:44

-1

I forgot to add use_frameworks! in my podfile. I added it back and it worked.

answered Apr 28 '21 at 08:44

Prashuk Jain

67
1
4

score -2 · Answer 40 · answered Sep 25 '19 at 07:59

-2

None of the above worked for me, but brew reinstall icu4c did.

answered Sep 25 '19 at 07:59

Pierre Monico

982
8
16

dyld: Library not loaded ... Reason: Image not found

40 Answers40

Xcode 11.1 & Swift 5.1

Quick Fix

Linked

Related