ld: framework not found Pods

Question

I'm trying to add a framework to my IOS project but when I build I always got the same message :

ld: framework not found Pods

clang: error: linker command failed with exit code 1 (use -v to see invocation)

I tried to remove my Pods directory and then run pod install I open the .xcworkspace like it is written in the logs on the pod install, I clean the project on xcode and then try to build but it won't works..

My podfile looks like this :

xcodeproj '/Users/guillaume/project/Mobile/iOS/FoodPin/FoodPin.xcodeproj'
source 'https://github.com/CocoaPods/Specs.git'
platform :ios, '8.0'
use_frameworks!
pod 'SwiftHTTP', '~> 0.9.2'

My version of xcode is 6.3.1

Thank you,

Did you check that `libpods.a` is in your "Linked Frameworks and Libraries" of your target ? And in your Build Phases too ? — BoilingLime, Apr 25 '15 at 17:04
This [answer][1] solved my problem! Hope it helps [1]: http://stackoverflow.com/a/31161871/1557663 — Mário Carvalho, Sep 29 '15 at 17:06
@MárioCarvalho Thats just a longer and more beginner-friendly version of my answer x) — Arbitur, Nov 27 '15 at 13:51
This is how I solved this issue. https://stackoverflow.com/a/46358379/2024878 — Vinay Kumar, Oct 26 '17 at 06:00
Best unser is here: https://stackoverflow.com/a/60496314/1151916 — Ramis, Mar 02 '20 at 20:40

Arbitur · Accepted Answer · 2016-02-29T15:03:41.727

547

In Project Navigator in the folder Pods I had a Pods.framework in there which was red. It was also present in Linked Frameworks and Libraries. I removed both references and the error disappeared.

TL;DR

Remove Pods.framework in:

Folder named Pods
Linked Frameworks and Libraries

edited Feb 29 '16 at 15:03

answered Jul 24 '15 at 10:20

Arbitur

36,899
22
86
123

6

I think I ended up with this problem after added use_frameworks! to my Podfile and subsequently commenting it out. Deleting the reference to Pods.framework fixed the issue. – StephenT Sep 08 '15 at 16:33
2

@StephenT Yes I believe thats what I did too, first use `use_frameworks!` and then without and perhaps the `Pods.framework` wasn't deleted properly during `pod install`. Might be a bug in Cocoapods. – Arbitur Nov 24 '15 at 08:36
This is a good answer, doesn't affect the example app, it still running well – Gabriel Goncalves Nov 27 '15 at 13:27
3

If this doesn't work, try using cocoapods-deintegrate. That just solved this problem for me. – nickdnk May 28 '16 at 15:00
This is a helpful quick solution, but note the answer below from @chris-trevarthen which provides the explanation and superior solution. It also is consistent with the current Firebase documentation (i.e. "open the ___.xcworkspace file") – Jeff Collier Jul 30 '16 at 16:47
Removing from *Linked Frameworks and Libraries* it worked for me :) – TheTiger Aug 09 '16 at 12:35
If you rename your project - then Cocoa pods doesn't automatically delete the framework file from linked library. Might be a bug.. but seems like an edge case – UKDataGeek Sep 03 '16 at 12:03
3

After running pod install, I somehow ended up with a "Pods_".framework file in my Pods folder. Deleting this file, cleaning, and rebuilding removed this error for me. – Caleb Faruki Oct 17 '16 at 17:10
I'm pretty sure this error occurred for me after adding several more pods to my project, then deciding to roll back by shelving the changes in Git. I have yet to resolve it using any of the methods I've found thus far – this thread included. – AndrewHenderson Mar 18 '17 at 03:40
Thank you so much, you saved my life <3 – Tà Truhoada Jul 13 '17 at 05:55
Thanks .Worked for me – Syed Abdul Basit Sep 17 '17 at 10:36
if this does not work, no way to undo your changes and all hell breaks loose on xcode.. – Siddharth Dec 30 '17 at 10:54
Also, check the deployment target version with pod's platform version – Brownsoo Han Mar 27 '18 at 07:28
I serached for pods and found the name of giving error pod-projectname.pod and removed it from dependencies... It worked thanks! – Rakshitha Muranga Rodrigo Dec 23 '19 at 19:58

score 258 · Answer 2 · answered Sep 03 '15 at 18:11

258

This is usually caused by having the .xcodeproj file open instead of .xcworkspace.

When you run 'pod install' for the first time, it will create an .xcworkspace file, which includes your original .xcodeproj and a Pods project. You'll need to close your .xcodeproj and open the .xcworkspace instead.

This is a common issue when creating a project through Xcode's new project wizard - I often forget that I'm not in a workspace, which is required to get Cocoapods to link correctly.

answered Sep 03 '15 at 18:11

Chris Trevarthen

4,374
2
13
10

Thanks ! It's confusing me at the first time – Phi Nguyen Mar 19 '16 at 04:40
12

Your explanation is much better than I have seen elsewhere. I didn't realize what was going on. Thanks! – Michael Yaworski Jul 04 '16 at 04:54
When done in combination with the answer by Arbitur, this resolves the issue. Thanks! – user1577390 Sep 13 '16 at 02:47
This was exactly my issue. Thanks! – Antonio Papalillo Sep 27 '18 at 08:05
there is no .xcworkspace file inside my project. what to do – Kartiikeya Mar 18 '19 at 10:36
You scored perfectly! – ken4ward May 19 '21 at 08:20

Ted · Answer 3 · 2020-06-10T10:31:56.337

135

Xcode 9, 10, 11, 11.5

install https://github.com/CocoaPods/cocoapods-deintegrate

pod deintegrate

then

pod install

edited Jun 10 '20 at 10:31

answered Sep 18 '17 at 09:46

Ted

19,425
10
78
99

1

Worked like a charm! Thank you. This got rid of an old reference to a renamed target that was causing this error. – Alex Obenauer Mar 29 '18 at 11:04
1

Wow You saved my day! was stuck from yesterday and finally solved with Xcode 10. Thanks! – Purushottam Padhya Oct 05 '18 at 04:52
3

This should be the correct answer, it's the safest approach. Don't do manual steps when using automated stuff like CocoaPods, unless it's a known bug that can't be fixed otherwise. – Gobe Mar 26 '19 at 16:44
Doesn't work for me. But Elliott Davies answer works. – Torben G Oct 11 '19 at 04:13
1

This was the only correct solution for me. Xcode 11.5 (11E608c). Thank you! – banana1 Jun 10 '20 at 06:37

theblang · Answer 4 · 2015-08-27T02:34:14.893

56

I cleared this error by deleting the red .framework files that were located in a folder Frameworks in the project navigator. I think this also automatically deleted corresponding red entries in the Linked Frameworks and Libraries section of the General settings.

I have been cleaning / reinstalling pods in order to fix another issue. Perhaps these red framework files and entries were just leftover from a previous pod install?

edited Aug 27 '15 at 02:34

answered Aug 27 '15 at 02:13

theblang

9,669
9
61
116

Yes! My issue was in Linked Frameworks and Libraries of the General settings and was difficult to find as it doesn't come up in a text search! – Alistair Cooper Mar 22 '19 at 15:36
In my case the framework files weren't even red, but just grayed out. But deleting them seems to have fixed the problem! – Swindler Jun 10 '19 at 06:13

score 35 · Answer 5 · edited Apr 04 '18 at 16:07

35

For who find this issue. I am using NativeScript and got the same error.

That happen becouse I opened the file .xcodeproj, but we must open the project by the file .xcworkspace.

edited Apr 04 '18 at 16:07

Gabriel Jensen

4,052
1
14
14

answered Sep 10 '16 at 19:01

calebeaires

1,593
17
27

Sharukh Mastan · Answer 6 · 2018-01-08T20:53:33.523

32

I had a similar issue as

framework not found Pods_OneSignalNotificationServiceExtension

It was resolved by removing the following. Go to target OneSignalNotificationServiceExtension > Build Phases > Link Binary with Libraries and deleting Pods_OneSignalNotificationServiceExtension.framework Hope this helps. Cheers.

edited Jan 08 '18 at 20:53

answered Nov 14 '17 at 15:46

Sharukh Mastan

1,083
14
15

This fixed the issue for me. My particular situation is that I had an iOS target MyApp. Then I needed to create a second target and had MyAppFirst, MyAppSecond targets. Cocoapods was able to build what it needed (Pods_MyAppFirst, Pods_MyAppSecond) but it was also trying to link to Pods_MyApp which no longer existed. I want to point out that in the process of trying to fix I did throw away my workspace file and Pods folder to have them recreated from scratch when I performed a “pod -install” but that did not help. – xdeleon Mar 15 '18 at 20:12
@Sharukh Mastan Would you have any idea how to make this happen after a pod install? Every time I pod install, the `Pods_OneSignalNotificationServiceExtension.framework ` comes back to haunt me in the linked frameworks and libraries of the `OneSignalNotificationServiceExtension` target. – Sethmr Apr 25 '19 at 19:06
@Sethmr Sadly, no. In my case, however, it doesn't always happen after a `pod install`, it's random. – Sharukh Mastan Apr 30 '19 at 08:26
@SharukhMastan My issue was opening the `*.xcodeproj/*.xcworkspace` over the `*.xcworkspace` with my vsts .yml automation script. I know better with a gui, but still getting used to the requirements in scripting land. – Sethmr Apr 30 '19 at 14:48
Thanks! I had to jump through some hoops to builds working on a new M1 mac. I was running out of patience by the time I got to this issue, so your solution really helped. – Jasper Blues Feb 25 '21 at 09:59

score 28 · Answer 7 · answered Jan 20 '17 at 14:58

28

This happened to me after updating my Podfile and doing a pod update.

For some reason, I had a "Pods_[ProjectName]".framework file appear under my project under 'Targets' > General > Linked Frameworks and Libraries.

Deleting this and then clean/rebuilding fixed the issue.

answered Jan 20 '17 at 14:58

Elliott Davies

726
7
6

2

This happens when you switch project names and need to clear the old one out. +1 – Babbz77 Oct 28 '17 at 07:02
This worked for me. I didn't change project names, but added Swift to a long running Objective-C project. – Luffy Dec 04 '18 at 05:40

score 15 · Answer 8 · answered Apr 29 '18 at 19:04

15

I was getting this error because i renamed my project and change the name of project in pod file too but my project was referring to old name which was not there and causing this error . I get rid of this by

pod deintegrate

followed by

pod install

answered Apr 29 '18 at 19:04

osama

1,218
16
22

Yes! I had the same problem when downgrading version from 12.0 to 9.0. The above worked after I'd modified the target version in my Podfile to match what was in the project. – Richard Bown Jun 11 '19 at 14:51
Good Answer. Thank you. – whdals0 Jun 18 '19 at 02:13

score 14 · Answer 9 · answered Mar 03 '17 at 07:38

14

you should delete your project some file as this picture.

answered Mar 03 '17 at 07:38

lingyfh

1,185
17
22

score 11 · Answer 10 · answered Sep 16 '17 at 22:25

11

Just Remove your .framework from the list of "Your Project->General->Linked Framework & Libraries".

answered Sep 16 '17 at 22:25

Md. Ibrahim

969
12
16

That was it, I had two after I renamed the project. Thanks! – Jimmy Nov 01 '17 at 17:28

Pengguna · Answer 11 · 2020-02-19T09:49:48.300

11

It's happened to me because I changed the Deployment Target in General but forgot to change the Deployment Target in Pods > General.

edited Feb 19 '20 at 09:49

answered Sep 05 '19 at 10:06

Pengguna

3,249
1
19
26

Fixed it for me as well, Xcode 11.2/Cocoapods 1.8.4. Irritating that the error message bears no resemblance to the root cause... – Jonathan Ellis Nov 13 '19 at 16:07
1

Fixed it for me - didn't have idea that I need to change this in both places. Thanks a ton! – hakazvaka Feb 10 '20 at 03:25

score 6 · Answer 12 · answered Feb 15 '16 at 05:45

6

In my case I can build it on devices and simulator but has the same errors when archiving. To solve it, I have to

remove Pods.framework
make sure Pods-<project-name>.framework is embedded

You will find the settings in TARGETS-->Linked Frameworks and Libraries.

answered Feb 15 '16 at 05:45

SeanChense

836
8
14

Could you check this out: https://github.com/CocoaPods/CocoaPods/issues/6203#issuecomment-261747869 – Esqarrouth Nov 24 '16 at 07:31

AnthoPak · Answer 13 · 2018-10-23T12:40:13.837

6

This issue was driving me crazy as it suddenly happened without doing any changes to the project. I've tried all suggested solutions in this thread (and other related) and none of them solved the problem.

The only thing that differed from my other projects (which compiled fine), was that this project name was containing an accent (a french accent, "é"). I've renamed the project and all related files, and it finally worked !

Maybe this is related to updating to Xcode 10, because this project was working well before...

EDIT : it also seems to failed when using a project with - in project name…

edited Oct 23 '18 at 12:40

answered Oct 23 '18 at 12:20

AnthoPak

3,531
3
18
34

1

You saved my life – Florian Mac Langlade Nov 05 '18 at 14:01
1

Saved my life too! – Dan Nov 19 '18 at 14:24
Any solution besides renaming the project? – anestis Oct 15 '19 at 09:45
@anestis I don't think so. To quickly rename the project, I suggest commands from this answer https://stackoverflow.com/a/48004237/4894980 which do a very great job! – AnthoPak Oct 15 '19 at 12:06
My life is saved. – Skoua Apr 03 '21 at 17:40

score 5 · Answer 14 · edited Sep 24 '15 at 11:00

Step 1

The first thing that you will need to do is remove the Podfile, Podfile.lock, the Pods folder, and the generated workspace.

Step 2

Next, in the .xcodeproj, remove the references to the Pods.xcconfig files and the libPods.a file.

Step 3

Within the Build Phases project tab, delete the Check Pods Manifest.lock section (open),Copy Pods Resources section (bottom) and Embed Pod Resources(bottom).

Step4

Remove Pods.framework.

The only thing you may want to do is include some of the libraries that you were using before. You can do this by simply draging whatever folders where in the pods folders into your project (I prefer to put them into my Supporting Files folder).

It worked for me.

Step 3 worked in my case, step 3 -> cmd+alt+shift+k. – ViruMax Oct 05 '18 at 08:25 — ViruMax, Oct 05 '18 at 08:25

score 5 · Answer 15 · answered Jul 31 '20 at 10:19

5

[Xcode 11.2.1]

For me it was different app target version in Podfile(platform :ios, '11.0') and in Xcode project file .

It causing Archiving job fail in CI pipeline.

Matching both value fixed an issue! Hope this help anyone.

answered Jul 31 '20 at 10:19

Hemant

83
1
7

It did solve my problem too, I had extension and the extension deployment version was different. Thank you @Hemant – MBH Oct 05 '20 at 13:23

score 4 · Answer 16 · answered Aug 12 '17 at 00:59

Using Xcode 8.3 the accepted answer didn't work for me. I had tried many other solutions but @Elliott Davies answer is what fixed it for me. I'm adding a screenshot for clarity. For some reason, Xcode was trying to link previous podfile setups that no longer existed. All I had to do was delete the extra references and everything worked.

score 4 · Answer 17 · edited Dec 22 '17 at 03:11

4

You're more than likely trying to get the pods to work into you project right? The only way to do so is by creating a separate project that uses CocoaPods.

Close all work-spaces that you are using.

Next, make sure you have your Podfile completely ready to go.

In the command line, wherever your file is, type the command:

pod deintegrate

Then, install your pod agian.

pod install or pod update

Now you can use your project's new workspace to develop from. Look for a file called .workspace. Use that file!

Here is a guide on using CocoaPods

edited Dec 22 '17 at 03:11

Spoody

2,657
1
21
34

answered Dec 21 '17 at 21:22

Emmanuel Mbaba

41
2

Only this one worked for me after struggle of 2 days with the error. – Mitesh Dobareeya Jan 11 '18 at 09:05

score 4 · Answer 18 · answered Oct 31 '18 at 17:52

4

In my case, after comparing the difference between a branch I knew built correctly, I noticed this line in my Podfile:

platform :ios, '11.0'

I had inadvertently up'd my target version from 10 to 11 while my targets in Xcode remained set to 10. Reverting back to 10 solved my issue for me.

Ensure your target iOS versions are properly set.

answered Oct 31 '18 at 17:52

joels

1,252
14
20

You saved my day!! Thank you – Mayank Patel Jan 01 '20 at 06:32

score 4 · Answer 19 · edited Apr 15 '19 at 01:28

This is the way i fix my problem. and it now work when i writing this answer:

Firstly, i try all the most fix way above,

remove Pods_xxx.framework from the link libraries and framework in target's build phases is helpful, and the issue will disappear, but the coming problem is i can't import the Pods.framework anymore.

And Then, i try to reinit the xcworkspace config, so that i can figure out the real problem. so i run

pod deintergate

and then install my pod again:

pod install

this work prefectly, but the problem is still in there, but i figure out the real problem is the Pods_xxx.framworks not be compiled succeed by cocoapods build script. I think this is the true way to fix the problem.

Finally, i try to edit my project's scheme:

and i add Pods scheme into manage:

and build this Pods.framework separately, and you will find the Pods.framework icon become truly again:

and i think now you have fix your "framework not found Pods_xxxx.framework" problem but actually i have another problem coming:

so i go to the build setting, and edit the "Framework Search Path" with "${inherited}", and now all the problems goes out, cheer!!!!:)

Adding Pod target and building it actually showed what was wrong with the pod build. In our case this was swift version conflict. Thanks! — green0range, Apr 26 '19 at 16:16
I didn't follow all the steps. I just added that `${inherited}` path, then did `Product->Clean Build Folder`, and that's it, now it builds without a hitch. — Starwave, Dec 30 '19 at 15:08

score 3 · Answer 20 · answered Nov 04 '20 at 21:19

3

in my case, my problem was the following: ld: framework not found UserMessagingPlatform.xcframework

for me, the solution was the following:

open a finder window and go to the ios folder
look for the following files:

Pods-[YOUR PROJECT NAME].release.xcconfig

Pods-[YOUR PROJECT NAME].debug.xcconfig

open those files and remove the following text: -framework "UserMessagingPlatform.xcframework" in both files

answered Nov 04 '20 at 21:19

Deyson

706
8
17

it doesn't crash if i do it, but.. everytime I do pod install then that line is added again and crashes. Also, what happens if I need this framework in the future? I think that is not the solution – NullPointerException Dec 04 '20 at 11:54

score 2 · Answer 21 · answered Nov 08 '17 at 11:58

2

After removing and updating pod I still had same issue.

I've found that previous developer put flag in 'Build Settings -> Other Linker Flags' with Framework name (in my case -framework 'OGVKit') that made the issue.

After deleting that flag, project builds properly.

answered Nov 08 '17 at 11:58

Babac

741
10
21

Thank you so much! You always have to keep an eye on stuff that are **bold** in Build Settings! – Marcio Granzotto Nov 20 '19 at 19:03

score 2 · Answer 22 · answered Jul 11 '18 at 09:03

2

I did experience this problem because I did not set the platform correctly.

So in my macOS app I had the platform set to:

platform :ios

instead of

platform :osx

answered Jul 11 '18 at 09:03

Besi

22,215
23
120
205

score 2 · Answer 23 · answered Jan 06 '20 at 19:14

None of the previous answers pointed out the root problem in my situation. So I hope this may be useful to someone else.

In my case I ended up having to edit my podfile at the root of my project. When I first created my podfile, swift static libraries were not supported. So I had been using use_frameworks! in my podfile under each of my targets as such:

BEFORE

...
target 'targetName' do
   use_frameworks!
   pod 'podName', '~> 0.2'
end

AFTER

...
target 'targetName' do
   pod 'podName', '~> 0.2'
end

I removed use_frameworks! from my podfile which kept installing the frameworks every time I ran pod install. After removing this line, make sure to run pod install again and remove any of the red .framework references from your Frameworks folder in Xcode. (Though mine appeared differently as attached below.)

Image of Removing .framework files that are no longer necessary

You can also read more about use_framework! here.

score 1 · Answer 24 · edited Dec 30 '16 at 01:21

1

I resolved this issue by selecting the project which downloaded from CocoaPods and built it, you can click Manage Schemes so that it can be appeared in Run bar. Then you can rebuild your project. Hope it help.

edited Dec 30 '16 at 01:21

Media

774
2
13
40

answered Dec 29 '16 at 22:27

vinhsteven

21
4

score 1 · Answer 25 · answered Sep 04 '19 at 04:34

1

For me, the problem was about changing the deployment target. I changed it to 9.0+ but changing it to 11.0+ worked.

answered Sep 04 '19 at 04:34

Joseph Francis

825
1
13
20

score 1 · Answer 26 · answered Nov 27 '19 at 14:19

1

In my case, there was a reference to the library I removed on

Targets > Build Settings > Runpath Search Paths

Removing the library from Podfile and updating it obviously didn't remove it, so I had to do it manually and now everything works.

answered Nov 27 '19 at 14:19

Marina Aguilar

1,039
6
25

score 1 · Answer 27 · answered Jun 12 '20 at 06:14

1

I have resolved this issue.

delete these three files.

Podfile.lock
Pods folder
.xcworkspace

Then open your project in terminal and run pod deintegrate command, and after then run pod install command

answered Jun 12 '20 at 06:14

Akbar Khan

1,442
13
17

score 0 · Answer 28 · answered Mar 09 '18 at 17:56

0

If you opened .xcworkspace file and you still got the same error:

delete all the contents of Pods directory and from command line write "pod install" to resolve the issue.

answered Mar 09 '18 at 17:56

Alp Altunel

2,588
1
19
25

score 0 · Answer 29 · answered Mar 17 '18 at 09:07

0

Delete the frameworks folder created after pod install or update

answered Mar 17 '18 at 09:07

Xcoder

228
1
5
12

score 0 · Answer 30 · answered Sep 21 '18 at 16:12

0

Other thing that solved my problem is to go under Target -> Build Settings -> Other linker Flags and delete the "-framework" and your framework "name".

It happened when i tried to remove a pod.

answered Sep 21 '18 at 16:12

atacand1920

23
3

score 0 · Answer 31 · answered Mar 06 '19 at 14:43

I resolved this by dragging .framework file to the Linked Framework and Libraries

Let say I was having this problem due to error FIRAnalyticsConnector not found and I just drag FIRAnalyticsConnector.framwork file to Linked Framework and Libraries and my problem solved

score 0 · Answer 32 · answered Jun 11 '19 at 01:08

0

I tried every answer on here and none of them worked. I ended up getting it working by upping the deployment target from 10.0 to 11.0. I have no idea why that fixed it, but I suspect it has to do with upgrading to Xcode 10.2.1.

answered Jun 11 '19 at 01:08

Swindler

722
7
8

score 0 · Answer 33 · answered Jun 16 '19 at 03:35

0

maybe you suddenly open the wrong file of .xcodprj and you should open .xcworkspace

answered Jun 16 '19 at 03:35

amirtutunchi

43
5

It is better to post such this as a comment. – Masoud Rahimi Jun 16 '19 at 03:57

score 0 · Answer 34 · answered Jul 23 '19 at 15:14

Please check your Executable file inside .Framework like

The executable file name should like this without any extension.
Some frameworks showing like this
Using Terminal goto .framework directory use below command lipo -create FrameworkName-x86_64 FrameworkName-armv7 FrameworkName-armv7s FrameworkName-i386 FrameworkName-arm64 -output FrameworkName

after creating single executable file delete this files

score 0 · Answer 35 · answered Oct 18 '19 at 07:49

0

another great things is using this rule to disable the input & output paths of the CocoaPods script phases (Copy Frameworks & Copy Resources):

 install! 'cocoapods',
        :disable_input_output_paths => true

answered Oct 18 '19 at 07:49

Alessio Campanelli

902
10
18

score 0 · Answer 36 · answered May 28 '20 at 23:49

0

In my case, I created the workspace before installing the pods, so when I installed the pods, the workspace included my project only, add the Pods project to your workspace, clean and rebuild solved the issue in my case

answered May 28 '20 at 23:49

Yaman

963
16
28

score -2 · Answer 37 · answered Jan 21 '21 at 02:42

-2

pod init
close current xcode project
reopen xcode project with the xcworkspace suffix

enter image description here

answered Jan 21 '21 at 02:42

caoyanglee

1

In question is is already mentioned that they are are using .xcworkspace – ibnetariq Jan 21 '21 at 04:54

ld: framework not found Pods

37 Answers37

Linked

Related