dyld: Library not loaded: @rpath/Alamofire.framework/Versions/A/Alamofire Reason: image not found

Question

I'm using CocoaPods v0.36 with my Swift project and the following pods: Alamofire, CocoaLumberjack, SwiftyJSON.

Everything was fine till I used my Developer ID. Compiler started to have problems to compile the project, after some fixes and updates for CocoaPods my project compiles but at runtime I get the following error:

dyld: Library not loaded: @rpath/Alamofire.framework/Versions/A/Alamofire   
Referenced from: /Users/Ivan/Library/Developer/Xcode/DerivedData/myApp-bsxfcnwqpaxnzbhencwzteasshzf/Build/Products/Debug/myApp.app/Contents/MacOS/myApp  
Reason: image not found

I read different posts related to this:

But none seems to solve the issue.

The only clue that I have is that the 3 frameworks are in red, so it seems that are not generated/linked.

enter image description here

Now, I've removed my Developer ID, but the issue is still there. Does anybody have an idea?

How are you adding the frameworks to your project? If you know the location of them I would recommend that you try adding them manually. — l'L'l, Apr 07 '15 at 06:27
Ivan, you're a lifesaver!…and can you post your solution as a full-fledged response? I spent hours trying other, useless solutions having intentionally skipped past this post since it's was labelled as having no solution. — clozach, Jul 19 '15 at 01:09

Ivan · Accepted Answer · 2018-04-29T23:05:25.233

26

Solved Below the steps I did:

pod deintegrate, pod update, pod install
Reimported the three swift library files (generated by cocoapods)
Imported the three frameworks only in the Linked Frameworks and Libraries
Full clean and a build

edited Apr 29 '18 at 23:05

answered Mar 09 '16 at 03:47

Ivan

666
1
7
17

1

I really don't understant step 2 and 3 – SinaMN75 Mar 15 '20 at 16:03

score 21 · Answer 2 · answered Dec 05 '15 at 08:12

21

dyld library not loaded @rpath/framework

please make sure that the framework is showing under target->general->embeded binaries and linked framework and libraries section

if not then add by clicking + sign add just add the framework only

done!

answered Dec 05 '15 at 08:12

NSurajit

413
4
10

nice one, fixed for me. – GordonW Dec 04 '18 at 21:32

score 10 · Answer 3 · answered Feb 13 '20 at 15:37

10

For iOS 13.3.1 : comment use_frameworks in podfile .

answered Feb 13 '20 at 15:37

Rishabh Shukla

461
6
19

1

Doesn't work for me... but this only happens on real device, simulator's fine... – Tieda Wei Feb 28 '20 at 23:33
@TiedaWei same was happening with me , try pod deintegrate and then pod clean and then again install your pods , this will remove your pofile and remove all pods so be careful on that :) – Rishabh Shukla Mar 01 '20 at 13:57
Thanks , it work. Comment and then pod install again. – iGhost Mar 18 '20 at 03:26
I notice when I comment `use_framework` in **podfile**, Xcode throw another error `...Proyect_Name.framework: 'No such file or directory'`. For resolve it, you need to do all yours pods as static libraries. Check [here](https://stackoverflow.com/a/60059840/7278926) for more details. Finally clean and build project and **pod install** – iGhost Mar 18 '20 at 18:40

score 6 · Answer 4 · answered Aug 14 '15 at 18:59

we were running into this issue here at work and one person's project would run while the other would get this strange error.

We did some comparison and realized that error is being generated when in the Xcode project's target, under Build Phases its missing some of the run scripts that Cocoapods is supposed to generate.

Check your project to make sure that these 3 scripts are there

Check Pods Manifest.lock
 Embed Pods Frameworks
 Copy Pods Resources

If they aren't I've attached a screenshot of them so that you can add them manually

i did the same..but not working.please give some idea – Madhumitha Jul 16 '16 at 07:13 — Madhumitha, Jul 16 '16 at 07:13

score 5 · Answer 5 · answered Apr 03 '19 at 09:25

5

Try this:

Find your Target --> Build Phases --> Add New Copy Files Phase -->Choose Destination Option,Frameworks --> Click add AFNetworking.framework --> ✓.

answered Apr 03 '19 at 09:25

Vladyslav Panchenko

1,517
1
19
23

score 2 · Answer 6 · answered Apr 26 '16 at 10:39

2

Solved by Unchecking Copy Only when installing.

answered Apr 26 '16 at 10:39

Atef

2,872
1
36
32

score 2 · Answer 7 · answered Aug 14 '18 at 11:21

2

Make sure you have set valid certificate and provisioning profile in XCode!

answered Aug 14 '18 at 11:21

Dhaval H. Nena

3,992
1
37
50

score 2 · Answer 8 · answered Mar 18 '20 at 13:10

2

I have tried all the above solutions but no luck.

For me, Just run your app using an enrolled account instead of a free apple account.

Note: Free account is not worked in 13.3

answered Mar 18 '20 at 13:10

Hitesh Surani

12,733
6
54
65

Just ran into this today. Thank you! The error makes no sense. – Myxtic Mar 20 '20 at 11:18

score 1 · Answer 9 · answered Dec 09 '15 at 03:43

1

I solved that trouble just by uncheck the "copy only when installing" on copy frameworks in Build Phases

answered Dec 09 '15 at 03:43

Qun Li

1,256
13
13

score 1 · Answer 10 · answered Jan 08 '20 at 06:35

After wasting two days and applying every solutions this worked for me. Hope it helps to you too.

Go to Keychain Access -> Certificates -> Double click on Apple Worldwide Developer Relations Certification Authority -> Click on the dropdown of trust -> When using this certificate -> set to Use System defaults

score 0 · Answer 11 · answered Mar 12 '19 at 08:05

None of the other stuff worked for me. So what did solve it for me in the end was a change in the podfile. I changed the code for the target in which it happened to:

target 'UITests' do
inherit! :search_paths
end

After a pod install it finally worked.

score 0 · Answer 12 · answered Mar 05 '20 at 18:43

0

in iOS 13.3.1 you can't run your application in your apple device without paid developer account

you can read complete explanation in this link

complete explanation click here

answered Mar 05 '20 at 18:43

Behnam Rakhshani

514
6
9

score 0 · Answer 13 · answered Jun 13 '20 at 20:46

I solved the problem in another way. The missing library was used inside of a framework that the application has a dependency on that. Also, In the Podfile the framework's pod target was outside of the application's target, so I moved the framework's target inside it like below:

target 'MyApplication' do
  use_frameworks!
  #blah blah 

  target 'MyFramework' do
    use_frameworks!
    pod 'The crashing library'
    #more blah blah

  end
end

and then I ran the 'pod install' command and Boom! The crash was gone.

score 0 · Answer 14 · answered Jun 26 '20 at 18:29

0

After wasting full day i found the solution. I changed

pod 'Alamofire' or pod 'Alamofire', '~> 5.2'

to

pod 'Alamofire', '~> 5.0.0-rc.3'

And this worked for me.

answered Jun 26 '20 at 18:29

Mandeep Singh

857
8
13

score 0 · Answer 15 · answered Apr 09 '23 at 08:01

First step: add use_frameworks! at the beginning of your podfile.

Second step: Add the bellow code at the end of your podfile. Which means after the end of your target.

dynamic_frameworks = ['Alamofire']
pre_install do |installer|
  installer.pod_targets.each do |pod|
    if !dynamic_frameworks.include?(pod.name)
      puts "Overriding the static_framework? method for #{pod.name}"
      def pod.static_framework?;
        true
      end
      def pod.build_type;
        Pod::BuildType.static_library
      end
    end
  end
end

Third step: run pod install

dyld: Library not loaded: @rpath/Alamofire.framework/Versions/A/Alamofire Reason: image not found

15 Answers15

Linked