Xcode 5 iOS 7 CocoaPods Linker Error

Question

I just upgraded my old project to new iOS 7. It was already using Cocoapods. I compile and run and everything works fine on the simulator and the device. I tried to archive it using Xcode and I get the following error.

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

Any ideas!

UPDATE:

The architecture for the Pods project is set as the following:

Standard architectures (armv7,armv7s)

SOLUTION :

Cocoapods has been removed from my project. Everything is good now!

Answer 1

Sounds like you just needed to update cocoapods. For anyone else who doesn't want to solve the problem by simply removing cocoapods from your project, do this:

1. Check your version of cocoapods:

   pod --version

2. If it's less than 0.25.0, you need to do an update (don't forget "sudo" if necessary):

   gem update cocoapods

3. Make sure your pods are updated:

   pod install

4. Finally, open your .xcworkspace file.

You should be good to go.

Answer 2

I had this problem when experimenting with adding CocoaPods to an existing project.

It turned out that CocoaPods got the Architectures setting right, but missed on the Build Active Architecture Only setting. Both must be in perfect sync with your main project, or it will fail when building for a real device (at least if you got more than one ARM arch, which you usually do (armv7, armv7s and now arm64)).

Solved the problem for me, hopefully this will help others with a similar problem.

Answer 3

I just fixed this issue in my workspace. In my case, it wasn't related to upgrading to iOS 7; instead, it was related to archiving for App Store submission. I created an App Store configuration (a duplicate of the Release configuration), and I was trying to use the App Store configuration for the Archive action (configured under Product > Scheme > Edit Scheme... > Archive > Build Configuration). The problem was that I had created an App Store configuration for my app's project, but I hadn't created an App Store configuration for the Pods project (the project that CocoaPods adds to your app's workspace). Once I did this (again, just a duplicate of the Release configuration), the Archive action succeeded.

Answer 4

The solution of @john doe (owner of this thread) is correct, you must set up CocoaPods for your project first by running

pod setup

And then

pod install

Answer 5

Variety of reasons why is this happening. This page is really helpful:

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

For some reason, I changed the workspace build location to Legacy. Changing it back to Custom: Relative to Derived Data solved it for me!

Answer 6

1. Try to remove arm64 from Build Setting -> Architectures (armv7, armv7s)
2. Set Build Active Architectures Only to NO

Worked for me just now.

cocoapods version 0.34.1

Answer 7

I had different problem - dublicate files.
Maybe you have dublicates in your project too. Like the ones from Pods and the other are old files which you didn't delete before you start using Cocoapods.
Double check them.

Answer 8

set the architecture of pods.

Click on Pods>Build Settings>Architecturs>armv7,armv7s