Error: ld: library not found for -lPods with CocoaPods

Question

after i installed DTCoreText (https://github.com/Cocoanetics/DTCoreText) with Cocoapods i always get an error when i try to run the simulator or device!

ld: warning: directory not found for option '-L/Users/example/Desktop/ios/Pods/build/Release-iphoneos'
ld: warning: directory not found for option '-L/Users/example/Desktop/ios/Pods/build/Debug-iphoneos'
ld: library not found for -lPods-example
clang: error: linker command failed with exit code 1 (use -v to see invocation)

in my "Link Binary With Libraries" the "libPods" Part is red:

enter image description here

Here are my build Settings:

The Settings of my Project:

enter image description here

The Settings of my Pods:

enter image description here

EDIT:

I´m not exactly sure what was the Problem, but I solved it when i deleted all the DTCoreText and Cocoapods stuff and reeinstalled everything again!

The pods manifest lock section is a script. It isn't an error. — John Stack, Oct 12 '14 at 13:30
did you solve this? I can build on simulator but not on device — laucel, Nov 12 '14 at 16:23

score 50 · Accepted Answer · answered Nov 03 '14 at 22:29

50

Suggest trying the following, that worked for me:

a) Search from 'Library' from the Target Settings view and double-click to inspect the value of Library Search Paths

b) There are two values listed $(inherited) and $(PROJECT_DIR)/Pods/build/Debug-iphoneos. Delete the latter.

c) Do a full clean, build & run

d) Run pod install again. Notice that the entry is not restored.

answered Nov 03 '14 at 22:29

gemmakbarlow

832
12
23

Your answer worked perfect! Why does this work, and where does the $(PROJECT_DIR)/Pods/build/Debug-iphoneos come from in the first place? – preynolds Jun 24 '15 at 09:02
1

My suspicion is that when you do `pod install` the install script expects a certain state (and can't handle things very effectively if that state is not present). I'm not sure where the `$(PROJECT_DIR)/Pods/build/Debug-iphoneos` came from originally, but deleting it and running a clean install seems to restore the expected state and allow the setup to complete appropriately. (Please note this is all speculative). – gemmakbarlow Jun 24 '15 at 12:51
Seems logical. I think this is the second time this error has happened to me, so I wanted to make sure there wasn't something fundamental I was misunderstanding. Many thanks for the insight! – preynolds Jun 24 '15 at 17:40
I think this should be reported back to Cocoapods guys. It's certainly bug and It should be easy to track down since this strange path "build/Debug-iphoneos" – Paweł Brewczynski Dec 15 '15 at 04:37
Great point Paul - I had assumed it was a known issue, but because the +1 keep coming for this question it might be worth mentioning to the guys and gals of Cocoapods. I'll open something now on their Github. – gemmakbarlow Dec 17 '15 at 01:14

score 37 · Answer 2 · edited Sep 07 '15 at 22:04

37

Also this may help:

In your main project (not Pods) select the main target
Go to the Build Phases tab
Go to Link Binary with Libraries
Remove the library that is causing the problem (it would probably be in red color)

edited Sep 07 '15 at 22:04

Francisco Corrales Morales

3,676
1
37
64

answered Mar 04 '15 at 08:36

kudinovdenis

625
6
12

1

Out of the gazillions of solutions to this problem, this is by far the simplest one. Did the trick for me. Thanks. – Christian Dechery Jan 05 '16 at 23:23

score 29 · Answer 3 · answered Nov 29 '14 at 07:11

29

Make sure you are opening the .xcworkspace file, not the .xcodeproj

answered Nov 29 '14 at 07:11

Hsm

1,510
17
16

Exactly what was my problem. – Rubberduck Jul 03 '17 at 12:23
Thanks a ton. Just started iOS development. – pradyot1996 Jul 04 '21 at 12:37

score 27 · Answer 4 · edited Jan 13 '20 at 11:25

27

In my linked binaries I had both libPods.a and libPods-MyProj.a. I had previously updated my Podfile to have TWO separate targets (to get it compile tests in Swift with bridging), which meant I had to manually delete the old libPods.a dependency.

edited Jan 13 '20 at 11:25

Stunner

12,025
12
86
145

answered Dec 01 '14 at 20:24

bobics

2,301
2
23
25

how do you do this thing? I did remove everything of type libPods-* from LInked Binary Libraries, but still getting the same issue. I've started a new thread here: http://stackoverflow.com/questions/31921701/ios-duplicate-symbols-for-architecture-armv7 – meteors Aug 10 '15 at 15:57
YES! This was my problem as well; I was writing an app with an App Extension, which wasn't allowed to use some of the code in a few of the pods I was using, so I split it into two targets in the Podfile. Didn't realize that while it added linking to my two new targets, BOTH targets in the project still were trying to link the original unified Pods library. Thank you so much for this answer! – DanM Oct 03 '15 at 03:22
I'd like to bump this. I started off without defining the pods per target, and then had to due to test, so had 2 targets, and one which was no longer being used, so delete the libPods.a to solve this issue – Alex Trott Feb 16 '16 at 13:30
This is a very common issue, and the proper solution. Might happen as when your project has multiple targets, but only one has a pod dependency. Also may happen when the pod file is updated. – alcamla Jan 13 '17 at 17:35

score 8 · Answer 5 · answered Feb 05 '15 at 16:49

8

I've found that $(inherited) was missing from my Other Linker Flags build setting. Applying this option fixed a missing library issue I was seeing.

answered Feb 05 '15 at 16:49

John Dunne

387
1
6
12

Can you provide more details please? Where should I add this? – Nuno Gonçalves Mar 16 '15 at 10:58
1

@NunoGonçalves In Xcode, click on your Project File, you'll see the Project Targets listed to the right. Click on the **Project Target**, then under the Build Settings, search for the settings **Other Linker Flags** and you should see it already listed there. Check this link [link](http://docs.millennialmedia.com/iOS-SDK/iOSAddingLinkerFlag.html) – John Dunne Mar 16 '15 at 13:24

score 5 · Answer 6 · answered Jul 08 '14 at 16:50

5

I found that selecting "Find implicit Dependencies" (under product / edit scheme) will resolve this issue instead of having to add pods as a target.

answered Jul 08 '14 at 16:50

StackRunner

1,463
2
16
22

3

Normally selected as default. – John Stack Oct 12 '14 at 13:28
At the same place the Pods have to be on the top of the list – brainray Oct 22 '14 at 14:15

score 4 · Answer 7 · answered Jun 24 '14 at 02:18

4

Look for "Library Search Path" in you target's Build Settings page. change the folder name of Debug from Debug-iphoneos to Debug-iphonesimulator

answered Jun 24 '14 at 02:18

Kent Ke

1,239
1
8
6

score 3 · Answer 8 · answered Apr 19 '16 at 12:16

Make sure the missing pods library gets actually built. To do so, open the Build Scheme

Product > Scheme > Edit Scheme... > Build

add the Pods target and put it before the target that complained about the library missing (in my case this were the UI tests – I just struggled with this for hours...)

score 2 · Answer 9 · answered Dec 09 '14 at 06:50

2

There are so many reason caused this problem.

We need to check:

Build setting $(inherited)
Detect all implicit dependencies
.......

Troubleshooting: http://guides.cocoapods.org/using/troubleshooting.html

answered Dec 09 '14 at 06:50

Tony

4,311
26
49

score 2 · Answer 10 · answered Jul 01 '16 at 15:17

For me the error was: that the Pods target did not contain the required architecture slice for i386. So i clicked on the Pods project --> Pods-ProjectName target, and in Build Settings, turned Build Active Architecture Only to NO for both Debug and Release. This makes sure both the Simulator and Device slices are built. The simulator uses the i386 architecture, and the actual devices use x86-64. So you have to make sure all dependent targets for all dependent projects are building both, if you want to run on both Simulator and side loading to devices also.

score 0 · Answer 11 · answered Dec 30 '14 at 09:17

0

When you use App extension, navigate to the extension target, and filter to Library Search Path, delete the path the compiler warning to you.

answered Dec 30 '14 at 09:17

tounaobun

14,570
9
53
75

score 0 · Answer 12 · answered Jan 13 '20 at 11:28

0

Removing armv7 from VALID_ARCHS within Build Settings resolved this issue for me (Xcode 10.3). I was able to submit after having only armv7s, arm64, and arm64e in VALID_ARCHS.

answered Jan 13 '20 at 11:28

Stunner

12,025
12
86
145

score 0 · Answer 13 · answered May 30 '21 at 20:13

0

First I ran

sudo rm -r /Library/Developer/CommandLineTools

to remove the command line tools directory. Then I installed command line tools again with

xcode-select --install

This solved the issue for me.

answered May 30 '21 at 20:13

rpontual

85
5

Error: ld: library not found for -lPods with CocoaPods

13 Answers13

Linked