library not found for -lPods

Question

I got an error when archiving a project. This is my environment.

Mac OS Lion
Xcode 4.3.1
iOS SDK 5.1

The project deployment target is:

IPHONEOS_DEPLOYMENT_TARGET 3.2

The error shows:

ld: library not found for -lPods
clang: error: linker command failed with exit code 1 (use -v to see invocation)

I guess Pods is CocoaPods that I used to manage XCode project dependencies. https://github.com/CocoaPods/CocoaPods

This is my Podfile

platform :ios  
dependency 'libPusher', '1.1'

I am not sure what the error means?

A cause of the problem that none of the answer covered. check this answer here: https://stackoverflow.com/questions/24050012/error-library-not-found-for/29497314#29497314 — hasan, Oct 01 '17 at 10:22

score 623 · Accepted Answer · answered Apr 03 '12 at 07:25

623

Are you opening the workspace (that was generated by CocoaPods) instead of the xcodeproj?

answered Apr 03 '12 at 07:25

alloy

20,908
2
30
40

28

I did. The problem is resolved after changing Pods project's release architecture to 'armv6 armv7'. – angelokh Apr 05 '12 at 05:32
11

Aha, in your `Podfile`, specify the platform like so: `platform :ios, :deployment_target => "3.2"`. That should configure it correctly the next time you run `pod install`. – alloy Apr 05 '12 at 21:54
254

To be clear for newbies out there, you should be opening the `.xcworkspace` file, not the `.xcodeproj`. This way in addition to your project, Xcode knows about the project in the `Pods/` directory and how to build `libPods.a`. – Jonathan Tran Jul 08 '13 at 00:59
13

Following on from @JonathanTran's comment... if you have the `.xcodeproj` open you need to have it closed before you open the `.xcworkspace` file. – Ross Sep 18 '13 at 19:25
4

Note that the project you're using pods with should also have it's architecture set to armv6 armv7(if thats the option you're using on pods project architecture). If you don't do that you'll get the very same error. – Patrick Bassut May 26 '14 at 06:16
Another case might be when under "Product-.Scheme-.Edit Schema", wrong destination is selected. In my case it was 32 bit architecture iOS. I changed it to iPhone 64 bit and it worked. Hope this helps ) – sermilion Aug 15 '14 at 20:25
There was a mixup somewhere while install pods with xcode open. I restarted xcode and viola, pods was in the existing workspace. – Jacksonkr Aug 22 '17 at 14:50
1

Thank you. Why is this not mentioned in the CLI when running pod install? – Petrus Theron May 30 '18 at 16:09

score 172 · Answer 2 · answered Apr 15 '14 at 13:25

172

I separated the app and the test targets in the Podfile by using

target :App do
    …
end

target :AppTests do
    …
end

This resulted in two new products libPods-App.a and libPods-AppTests.a, respectively and they made the previous product libPods.a obsolete. I had to remove this product from the Link Binary With Libraries Section of the Build Phases configuration of both targets.

answered Apr 15 '14 at 13:25

Andras Hatvani

4,346
4
29
45

3

Yes, this was it for me, after trying a dozen other things earlier in this thread. My podfile has two targets as above, and so libPods.a was not being built. Deleting libPods.a from the Link Binary With Libraries section "fixed" it (though of course I now have 32 "Undefined symbols" messages to sort through, due to a missing SQLite lib, etc. – Hot Licks Nov 11 '14 at 22:37
This is the same fix as http://stackoverflow.com/a/21694261/581994 and a couple of others. – Hot Licks Nov 11 '14 at 22:56
Currently still an issue that occurs – nsantorello Aug 05 '15 at 16:43
"they made the previous product libPods.a obsolete. I had to remove..." – Vassily Nov 23 '15 at 13:32
This was mostly the issue for me. For some reason, I had a binary from an older test target in there as well. – LJ Wilson May 25 '16 at 16:36
Thank you very mach! Removing "libPods-OldTargetName.a" helps me – Алексей Алыбин Nov 27 '16 at 17:27

Besi · Answer 3 · 2014-02-14T10:05:36.323

120

I ran into a similar problem today.

I setup a new project
I installed cocoa pods
I created a new configuration Preview along with the existing Debug and Release
Now when compiling on this new Preview configuration, the compiler would not be able to link with Pods and giving me this message:
```
ld: library not found for -lPods
```

The solution:

What I had to do was to run

 pod install

again and thus configuring cocoapods for the new Preview configuration. It updated my project, the workspace and the Pod's project file and the problem disappeared

edited Feb 14 '14 at 10:05

answered Jan 02 '13 at 12:53

Besi

22,579
24
131
223

1

This caught me out as well. Particular as it continued working long after I created the configurations and it was only when I cleaned out my derived data that the issue occurred. – Daniel Wood Oct 21 '14 at 13:29
And pay attention to the warnings displayed in the "Sending stats" section of the output of either "pod install --verbose" or "pod update --verbose", such as "The \`yourApp [Debug]\` target overrides the \`HEADER_SEARCH_PATHS\` build setting defined in ..." or "... target overrides the \`OTHER_LDFLAGS\` build setting ...". – jk7 Mar 23 '16 at 02:28
change **Preview** configuration in **Per-configuration Build Products Path**, and then do **pod install**, pod doesnt save my value in pod project, any help? – liu pluto May 12 '18 at 08:25
Ah! The problem was occurring just after creating a new configurations for Extensions. First 3 steps help me to understand the issue. Thanks! – iHarshil Aug 23 '19 at 09:56

score 74 · Answer 4 · edited Feb 08 '16 at 08:46

74

Be sure that you open .xcworkspace, not .xcodeproj

edited Feb 08 '16 at 08:46

Hima

1,249
1
14
18

answered Jan 08 '13 at 23:03

Michal Gumny

1,770
1
16
24

This was my issue. I was opening the project from the regular Xcode project file. Once you start using cocoa pods you need to start opening your project from the .xcworkspace file, not the .xcodeproj. – HotFudgeSunday Dec 04 '14 at 15:14
hehe i always do this :) – yeahdixon Mar 20 '15 at 19:51
THIS THIS THIS THIS – bryan Oct 18 '18 at 15:15
OMG I want to hug you. Changed so many things that were never the issue to begin with! – kjonsson Nov 06 '19 at 22:19

score 56 · Answer 5 · answered Nov 04 '14 at 11:41

56

Not a solution worked for me, this is really unbearable, there's a file libpods.a(which was red coloured) I removed it and everything working fine! Cheers to me ;)

answered Nov 04 '14 at 11:41

Hemang

26,840
19
119
186

6

Happened to me too. I had renamed my target and it created this problematic artifact .a file. – seenickcode May 20 '15 at 22:45
If I do this, then the libs I added using Cocoapods are not being added to the project. – Francisco Corrales Morales Sep 07 '15 at 20:37
1

u made my day :D, there was 2 targets and i deleted one but its pods still and was failed to build, resolved by just delete reference of pods of that target – mohammad alabid Mar 21 '17 at 20:56
Same happened to me. It was an old project that I didn't touch for years, still had the old format Podfile etcetera. – Lucas van Dongen Aug 03 '18 at 21:41

score 47 · Answer 6 · answered Jan 22 '16 at 13:16

47

I had an old libPod.a file specified (probably caused by me changing targets).

Project Settings -> Build Phases -> Link Binary with Libraries

Usually, cocoapods would only include one library, such as libPods-target.a or libPods.a. I solved it by removing the duplicate.

answered Jan 22 '16 at 13:16

Sebastian Hojas

4,158
2
27
38

5

This worked for me. I was adding pod support for the test targets (*Tests and *UITests) and the base configuration changed from `Pods.debug` to `Pods-MyApp.debug`, so now I only need `libPods-MyApp.a` (there was a "faded" icon for the old `libPods.a`), – Nicolas Miari Feb 17 '16 at 09:39
There was no faded icon for me but this was the only solution that worked. – Yogesh Maheshwari May 08 '16 at 02:00
Same here. Thanks – rmvz3 Jul 10 '17 at 09:30
I changed the project name, and the error happens. Above solution worked for me. – guness Feb 01 '18 at 19:39

score 46 · Answer 7 · answered Jun 21 '14 at 11:23

46

I had divided my pod listings in the Podfile for different targets like:

target :ABC do
  pod 'KissXML', '~> 5.0'
  pod 'libPhoneNumber-iOS', '~> 0.7.2'
end

target :ABCTests do
  pod 'OCMock', '~> 2.2.1', :inhibit_warnings => true
end

And ran a pod install

This created a new library libPods-ABC.a to which my binary had to link to. But the bug was that it didn't delete the previous library i.e. libPods.a.

Solution : Remove the library libPods.a from Build Phases of Link Binary With Libraries.

answered Jun 21 '14 at 11:23

Ayush Goel

3,134
27
36

This is the same fix as http://stackoverflow.com/a/23085107/581994 and http://stackoverflow.com/a/21694261/581994 – Hot Licks Nov 11 '14 at 22:55
2

The solution is different. This fixed it for me using this exact solution. – cynistersix Jan 05 '15 at 22:51
Remove the library libPods.a and then, pod install fix the issue for me. – bisma Feb 22 '16 at 06:51
1

it resolved when error is export IPHONEOS_DEPLOYMENT_TARGET=9.0 with "ld: library not found for -lPods" – jacksonfdam Oct 18 '16 at 22:05
Works to me, after I rename the target. – alsantos123 Jan 26 '17 at 04:27
I removed both libPods.a and libPods-xxx.a. This solution works to me. – ManuQiao Mar 03 '17 at 10:52

johndpope · Answer 8 · 2014-01-06T00:08:23.750

44

if you are running into problems with this on cocoapods v25 / Xcode 5

The Pods Xcode project now sets the ONLY_ACTIVE_ARCH build setting to YES in the Debug configuration. You will have to set the same on your project/target, otherwise the build will fail.

https://github.com/CocoaPods/CocoaPods/wiki/FAQ#running-into-build-failures-after-migrating-to-xcode-5-and-cocoapods-0250

UPDATE Make sure you have latest gems / cocoapods

gem update system
gem update cocoapods

You will want to rebuild project using Pod Install to rebuild project.

edited Jan 06 '14 at 00:08

answered Oct 15 '13 at 09:10

johndpope

5,035
2
41
43

This was it for me, after adding CP to a very old project. – Josh Hudnall Feb 12 '14 at 23:59
Same for me - added CP to a very old project, could build on simulator, but as soon as I switched to build for device, the build failed. That answer helped a lot! – Florian Jul 29 '14 at 11:40

score 40 · Answer 9 · answered Sep 24 '13 at 16:40

40

If Xcode complains when linking, e.g. Library not found for -lPods, it doesn't detect the implicit dependencies.

Go to Product > Edit Scheme Click on Build Add the Pods static library, and make sure it's at the top of the list Clean and build again If that doesn't work, verify that the source for the spec you are trying to include has been pulled from github. Do this by looking in /Pods/. If it is empty (it should not be), verify that the ~/.cocoapods/master//.podspec has the correct git hub url in it. If still doesn't work, check your XCode build locations settings. Go to Preferences -> Locations -> Derived Data -> Advanced and set build location to “Relative to Workspace”.

http://docs.cocoapods.org/guides/getting_started.html

answered Sep 24 '13 at 16:40

HoratioCain

915
9
19

3

The first part fixed my issue (Product > Edit Scheme, add Pods to Build as first item). Thank you – William Power Jun 10 '14 at 22:38
I had this issue in xCode 6.3 with cocoapods 0.36.0, and this is what fixed it. Thank you! – ProgrammierTier Jun 18 '15 at 15:30
same as xcode 6.3 cocoapods 0.37 -> Thanks !! was getting crazy with target settings, while the issue was the scheme. just add Pods. – altagir Jul 22 '15 at 23:23

score 36 · Answer 10 · edited Jun 20 '20 at 09:12

36

I had the same problem when I edited the Podfile adding the target which I was using without a target before.

Podfile

target 'xxxx' do

pod 'xyz'
pod 'abc'    

end

After wondering around I found that under target properties >> General tab >> Linked Frameworks and Libraries section, There were the new libPods-xxxx.a and the old one libPods.a

I just removed libPods.a and everything worked fine.

edited Jun 20 '20 at 09:12

Community

1
1

answered Apr 06 '15 at 13:53

Khaled Annajar

15,542
5
34
45

That was the problem for me too. I think the source of the problem was that I have upgraded CocoaPods and the format of the Podfile during the development. – gklka Aug 10 '15 at 12:52
2

I had exactly the same scenario after add target on pod. +1 for accuracy – Adriano Spadoni Oct 07 '15 at 17:24

score 27 · Answer 11 · edited Apr 04 '14 at 09:14

27

CocoaPods' wiki on GitHub has the answer right in their FAQ:

Go to Product > Edit Scheme
Click on Build
Add the Pods static library, and make sure it's at the top of the list
Clean and build again
If that doesn't work, verify that the source for the spec you are trying to include has been pulled from github. Do this by looking in <Project Dir>/Pods/<Name of spec you are trying to include>. If it is empty (it should not be), verify that the ~/.cocoapods/master/<spec>/<spec>.podspec has the correct github url in it.
If still doesn't work, check your XCode build locations settings. Go to Preferences -> Locations -> Derived Data -> Advanced and set build location to "Relative to Workspace".

Screen shot

edited Apr 04 '14 at 09:14

Joachim Kurz

2,875
6
23
43

answered Nov 30 '13 at 23:46

Chris Schiffhauer

17,102
15
79
88

6

I've run into this issue as well but I cannot seem to do these steps. I get stuck at "Add the pods static library and make sure it's at the top of the list". The static library doesn't show up with I click to add it to the Build scheme. Any idea? – Bay Phillips Dec 03 '13 at 15:51
@BayPhillips Close your current project and open the .xcworkspace created in your project folder. then the static library show up – junho Dec 27 '18 at 04:32

score 12 · Answer 12 · answered Feb 11 '14 at 05:58

12

I was renaming the project to "NBSelector" from "Partners".

I had "Library not found for libPods-Partners" error after renaming the project. Xcode was trying to link to old Partners.a file. Just remove it if you have podInstalled after renaming.

enter image description here

answered Feb 11 '14 at 05:58

Naloiko Eugene

2,453
1
28
18

perfect solution for my problem :) but after removing the pods need to added it again if you want to use it – satheesh Nov 27 '15 at 00:27

score 11 · Answer 13 · answered Jan 30 '14 at 09:53

Using ONLY_ACTIVE_ARCH=NO in all pods solved the problem for me. To make this persistent, I added a post_install hook to my Podfile:

post_install do |installer_representation|
  installer_representation.project.targets.each do |target|
      target.build_configurations.each do |config|
            config.build_settings['ONLY_ACTIVE_ARCH'] = 'NO'
      end
  end
end

pod install and you're done.

i4niac · Answer 14 · 2012-05-23T05:29:32.343

Did you create 'Distribution' or similar configuration to make Ad-Hoc and App Store archives? Like many others I followed Apple's recommendations and dubbed 'Release' configuration, called it 'Distribution' and set different signing rules to it. Well, maybe that was a recommendation before they introduced schemes and "Distribute" option in Organizer, anyway, I just had it from before.

Then I had same problem with Pods. It all worked well when debugging, but archiving failed with link error. After trying this and that I changed Archive configuration of my original project from 'Distribution' to 'Release' and the link error was gone.

Yet the archive did not show up in Organizer, though I could locate it in file system, but it had 0 size.

Final step to fix all this was to change "Skip Install" setting for 'Release' configuration to "NO". Note, that you have to do this only for your main project, but not for Pods project. Better leave Pods project as is, since it's generated every time you run 'pod install'.

Update Just got an answer from CocoaPods devs It doesn't seem to work for me, since I had Pods configuration properly set. But it could help someone else.

score 8 · Answer 15 · answered May 29 '13 at 00:00

8

In my case the problem was that Xcode's Derived Data location was set to the "Legacy" option. The CocoaPods target (libPods.a) was being built correctly, but Xcode was looking in the wrong place for it.

Switching it to "Unique" (the default) solved the issue. You can do this by going to Preferences > Locations and clicking the Advanced... button.

answered May 29 '13 at 00:00

Adam Sharp

3,618
25
29

But I'm in a situation that I have to use "Legacy", continue searching for another solution... – CocoaBob Sep 29 '15 at 11:07

score 5 · Answer 16 · answered Feb 13 '13 at 23:38

5

Only adding the "Library Search Paths" (in Build Settings of 'MyProject') to "Pods/build/Debug-iphonesimulator" worked for me (when using the simulator).

Got it from here: https://github.com/CocoaPods/CocoaPods/issues/121#issuecomment-5452473

answered Feb 13 '13 at 23:38

Jan M

447
5
9

score 4 · Answer 17 · answered Sep 22 '13 at 22:13

4

If you are Archiving for iOS7 and Xcode5 and got these errors, please refer to this link. It seems like Apple is dropping an architecture that cocoa pods needed https://github.com/CocoaPods/CocoaPods/pull/1352

answered Sep 22 '13 at 22:13

John Paul Manoza

1,735
25
22

score 4 · Answer 18 · answered Jul 08 '14 at 16:42

4

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:42

StackRunner

1,463
2
16
22

Also running pod install again can help once following these steps. – StackRunner Aug 19 '14 at 09:11

score 4 · Answer 19 · answered Aug 20 '14 at 19:30

4

I went through every answer on here, but for me it was insanely simple...Go to Target -> Build Phases, then remove libPods-YourProject.a, then add it again using the "+". Don't worry about the library being red, it's fine.

answered Aug 20 '14 at 19:30

cph2117

2,651
1
28
41

Tried everything but only this solution works! – hiew1 May 19 '23 at 06:47

score 4 · Answer 20 · answered Oct 12 '18 at 06:17

4

I did open the workspace, but got the same error.

Build Active Architecture Only set to YES

solve my problem.

answered Oct 12 '18 at 06:17

Joeful6

171
8

That helps. Thank you. Somehow it was set "YES" for Debug only while the rest configs has it "NO" and I've seen that error for all builds but Debug. – Pavel Yakimenko Oct 15 '19 at 14:23
This only helped me. Such answer 'Open as .workspace' is too boring. I think developers should first check install guide documents thoroughly enough.. – KoreanXcodeWorker Jan 09 '20 at 02:28

Bhavin_m · Answer 21 · 2016-06-15T06:00:37.900

I used old cocoapod version after update the cocoapods it suggest me to update my installed pod because of major update as i update after long time. I update it and new version pods was updated fine. But after that i got the error like library not found for -lPods-xxxprojectName-xxxxxpodName

After tried so many solutions given as answer of in this thred, non of this worked for me. Then i went to my project setting and found that pods path was change which was on Other Linker Flag

Check your Manage Schemes for correct pod name and compare it in Other Linker Flag, Change it if not similar

Old pod path was -l"lPods-xxxprojectName-xxxxxpodName"

But new pods was only xxxxxpodName so i replaced Other Linker Flag with new one like below

Changed to pod path -l"xxxxxpodName" and it's worked.

I don't know the perfect reason behind this but might be this help some one.

score 2 · Answer 22 · answered Sep 25 '13 at 11:26

2

Solved it by taking the steps below:

Update your cocoapods installation. ($ [sudo] gem install cocoapods)
Re-install your dependencies under your project. (pod install)
Clean and re-build / archive.

answered Sep 25 '13 at 11:26

SarpErdag

781
1
8
19

This actually worked very well. I had updated one of the pods in my project and that broke it. I followed these steps and it worked. It was a quick fix. Thanks – agarcian Oct 06 '13 at 17:56

score 2 · Answer 23 · answered Nov 27 '13 at 08:25

2

In my case pod install fixed the problem, after creating distribution and release schemes.

answered Nov 27 '13 at 08:25

kernix

7,970
3
28
44

score 2 · Answer 24 · answered Aug 18 '20 at 07:34

Nothing that was written here helped me - but it did set me on the right path. What I ended up doing was the following:

Analyze the error message.

It says Library not found: -lPods-... So it cannot find that particular library. How to resolve it? Well, make sure that this library is in the search path. So where is this library located?
Search where the library is located.

I typed find . | grep -e 'Pods-.*\.a' in a terminal in my ~/Library/Developer/Xcode/DerivedData folder. I found out my libPods-... library is located in a bunch of places, for example ~/Library/Developer/Xcode/DerivedData/[generated-name]/Build/Products/Release-iphonesimulator/libPods-[name].a
Add one of these folders to the library search path

If we add one of these folders to the library search path, then the problem will disappear. However, all the paths have a [generated-name] folder somewhere, in my case [Project]-guyraaahpczkqmhghlwgsdsqyxxs.

So how do we add that folder to the search path responsibly? By using a build time variable! We can get a list of which variables exist by looking at this answer. It turns out one of the variables that's defined is called ${PODS_CONFIGURATION_BUILD_DIR}, and in that exact folder my libPods-[Product].a is located!
Now add that folder to the library search path.

This is the easy part, and my actual answer to this question. Go to Build Settings -> Search paths -> Library search, make sure it is collapsed, and double click on <Multiple Values>.

In the dialog that pops up, click on the little '+' sign in the bottom left. Now type "${PODS_CONFIGURATION_BUILD_DIR}", and leave the drop-down option at "non-recursive". Type <Enter>. Now drag this entry all the way back up so that it sits directly under $(inherited).
You're done. Rebuild your product!

My error had now disappeared. Upvote this answer, close the tab, and forget the problem ever existed

OMG I was following the same line of thought after trying so many things, found where the thing had been placed, was thinking about how to include that gibberishian folder and then I found your answer about the build time variables. Hooray. Thanks, sir. — nacmartin, Aug 27 '21 at 00:14

score 1 · Answer 25 · answered Jul 31 '13 at 07:46

I got the same problem when archiving for submit. Discussion on this issue can be found here: https://github.com/CocoaPods/CocoaPods/issues/155

In summary, two methods work for me:

Setting "Preferences -> Locations -> Advanced" to "Custom(Relative to Workspace)" OR
Set Podfile to - platform :ios, :deployment_target => "5.0"

score 1 · Answer 26 · answered Oct 09 '13 at 00:32

1

Using Xcode 5 with iOS 7

This is what I did after being stuck for an hour. Remove ARM64 from the Build Setting > Valid Architecture.

ADDED: Also, for my case, it was not derived data location. I chose unique for build location.

answered Oct 09 '13 at 00:32

ytbryan

2,644
31
49

score 1 · Answer 27 · answered Feb 06 '14 at 09:03

1

if You're using iOS7 and Xcode 5, do:

Select your Pods Project.
Go to the Target Pods and in Build Settings, select Architectures-> Standard architectures (armv7, armv7s).
Do the same for every Target of your Pods Project.

answered Feb 06 '14 at 09:03

rabenson

9
2

score 1 · Answer 28 · answered Apr 30 '14 at 10:36

I tried EVERY answer in this thread to no avail. Finally resolved my issue by matching the "Pre-Configuration Build Products Path" in my target project with the value in the Pods project. Turns out they were building to two different output locations. None of the other suggestions in this thread were relevant for me. Would be great if XCode gave a useful error description (like WHY it can't use the lib - File Not Found, No matching architecture found, etc.).

score 1 · Answer 29 · answered Jun 05 '14 at 14:20

In this issue,If you have already installed & update pod in your system then your Xcode not being able to find the Pods library.To resolve this issue, please check for following causes that may take place:

You are using the workspace.
The Pods library builds.
The Pods library is referenced in the products group of your project.
Your target includes the Pods library in the link with frameworks build phase.

score 1 · Answer 30 · answered Oct 28 '14 at 16:04

1

try

link_with 'YouTarget1', 'YouTarget2' ...

My project worked, the targets suddenly stopped compiling. Then added "link_with" and returned to normal.

Apparently, now it just connects to the first target, is what the link says:

http://guides.cocoapods.org/syntax/podfile.html#link_with

answered Oct 28 '14 at 16:04

Wagner Sales

1,448
2
10
14

this one fixed it for me... had the problem, that the first target was building and the second target failed with "ld: library not found for -lPods..." – Muxor Nov 16 '14 at 16:08

score 1 · Answer 31 · answered Aug 29 '16 at 10:45

1

If you are still getting this issue, try:

pod update

Did the work for me, hope this helps you.

answered Aug 29 '16 at 10:45

Shobhit C

828
10
15

score 0 · Answer 32 · answered May 11 '13 at 04:23

0

try open xcworkspace file instead of xcodeproj file

answered May 11 '13 at 04:23

Nick Hoàng

417
2
6

score 0 · Answer 33 · answered Jun 12 '13 at 16:55

0

In my case nr 4 of the FAQ in this link helped out: https://github.com/CocoaPods/CocoaPods/wiki/Creating-a-project-that-uses-CocoaPods

There are a couple of additional things you can try out if the problem persists.

answered Jun 12 '13 at 16:55

user511

154
1
7

I guess just throwing in a link deserves a downvote. But instead of rephrasing or copying the text from there.I found it worth mentioning however – user511 Jun 13 '13 at 09:39
I found it worth mentioning that there are other possible reasons for this particular error and ways to solve them. It can occur even if you open the .xcworkspace file instead of the .xcodeproj. – user511 Jun 13 '13 at 09:49
I don't get why you were downvoted. Your answer is perfectly valid and there are other answers here that have just copy/pasted the content you were linking :/ The link is broken tho, this is the new one http://guides.cocoapods.org/using/troubleshooting.html – josebama Apr 29 '14 at 10:18

score 0 · Answer 34 · answered Sep 12 '13 at 03:41

0

renamed some_project.workspace file to some_project.workspace.backup and ran $pod install. It created a new workspace file and the error went away.

answered Sep 12 '13 at 03:41

Jdizzle Foshizzle

314
1
3
18

score 0 · Answer 35 · answered Nov 27 '13 at 23:48

0

I had that too, Cocoapods version 0.28.0

Easy fix here, no lengthy reading: - uninstall the Cocoapods (Command line or AppCode) - erase the Podfile, Podfile.lock, Pods folder

reinstall the Cocoapods
start the newly created workspace.

answered Nov 27 '13 at 23:48

brainray

12,512
11
67
116

score 0 · Answer 36 · answered Jan 21 '14 at 22:41

0

I had the same issue. It turned out to be an xCode bug in my case. All I had to do was remove the "Valid Archs", do a clean, re-add them and I was good to go. Also try updated cocoapods in general.

answered Jan 21 '14 at 22:41

anders

4,168
2
23
31

score 0 · Answer 37 · answered Apr 01 '14 at 10:56

I solved this problem with setting architectures and valid architectures same for all pods as for my project. So the hole solution in my case was:

update cocoa pods: sudo gem update cocoa pods
update pods: pod update
In your Pods go to to your Build settings > Architectures and set here Architectures and Valid Architectures to exact same values as in main project.

score 0 · Answer 38 · answered Aug 10 '15 at 18:42

To simplify @i4niac's answer:

Another common cause for this is a mismatch in the Scheme's Build Configuration. In our case, our 'AppName-AppStore' Scheme had "Release" as the Archive Build Configuration instead of "AppStore" (could be the other way around for others).

score 0 · Answer 39 · answered Dec 05 '15 at 10:16

I was missing libPods.a in target, so the first thing to do is add it to linked frameworks and libraries.

Next, Product -> Build for -> Profiling (Or before adding libPods.a, if you completely missing it)

and finally check your Copy Pods resources script in Build phases (If its the same as your second target - it depends on Podfile and its targets sometimes). Then you should build successfully.

score 0 · Answer 40 · edited Jun 20 '20 at 09:12

0

I ran into an issue where I had created my own .xcworkspace which kept pods form createing it's own (where is where it attaches it's library).

solution

I moved the .xcworkspace I had created, ran pod install again and then manually merged my .xcworkspace with the one pods created by openeing both workspaces and dragging files from one workspace to the other.

edited Jun 20 '20 at 09:12

Community

1
1

answered Apr 19 '17 at 15:24

Jacksonkr

31,583
39
180
284

score 0 · Answer 41 · answered Dec 21 '17 at 09:59

0

Removing CocoaPods cache folders ~/Library/Caches/CocoaPods and the install pod works for me.

answered Dec 21 '17 at 09:59

kaushal

1,553
18
25

score -1 · Answer 42 · answered Jul 05 '15 at 11:41

I tired all the answers and in the end i was able to fix it by adding pod library into the Xcode Build scheme , after i was able to run it, tried to remove this from the build scheme and still it worked fine for me. couldn't figure out the exact reason.

library not found for -lPods

42 Answers42

The solution:

Podfile

solution

Linked

Related