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

User · Answer

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

User · Answer

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

User · Answer

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

User · Answer

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

User · Answer

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

User · Answer

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

User · Answer

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

User · Answer

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

User · Answer

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

User · Answer

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   gt   5 0

User · Answer

Be sure that you open  xcworkspace  not  xcodeproj

User · Answer

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

User · Answer

In this issue If you have already installed  amp  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

User · Answer

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

User · Answer

I did open the workspace  but got the same error   Build Active Architecture Only   set to YES  solve my problem

User · Answer

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

User · Answer

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

User · Answer

try open xcworkspace file instead of xcodeproj file

User · Answer

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

User · Answer

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

User · Answer

I had divided my pod listings in the Podfile for different targets like   target  ABC do   pod  KissXML      gt  5 0    pod  libPhoneNumber-iOS      gt  0 7 2  end  target  ABCTests do   pod  OCMock      gt  2 2 1    inhibit warnings   gt  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

User · Answer

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 - gt  Search paths - gt  Library search  make sure it is collapsed  and double click on  lt Multiple Values gt   In the dialog that pops up  click on the little     sign in the bottom left  Now type  quot   PODS CONFIGURATION BUILD DIR  quot   and leave the drop-down option at  quot non-recursive quot   Type  lt Enter gt   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

User · Answer

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

User · Answer

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

User · Answer

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

User · Answer

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

User · Answer

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

User · Answer

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

User · Answer

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

User · Answer

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

User · Answer

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

User · Answer

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  gt  gt  General tab  gt  gt  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

User · Answer

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

User · Answer

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

User · Answer

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

User · Answer

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

User · Answer

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

User · Answer

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

User · Answer

CocoaPods  wiki on GitHub has the answer right in their FAQ    Go to Product  gt  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  lt Project Dir gt  Pods  lt Name of spec you are trying to include gt   If it is empty  it should not be   verify that the    cocoapods master  lt spec gt   lt spec gt  podspec has the correct github url in it  If still doesn t work  check your XCode build locations settings  Go to Preferences - gt  Locations - gt  Derived Data - gt  Advanced and set build location to  Relative to Workspace

User · Answer

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

User · Answer

If you are still getting this issue  try   pod update   Did the work for me  hope this helps you

User · Answer

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

[iphone] library not found for -lPods

Examples related to iphone

Examples related to objective-c

Examples related to ios

Examples related to xcode4.3

Examples related to cocoapods