Pod Error in Xcode "Id: framework not found Pods"

Question

I am trying to clone a project from a bitbucket repository and am getting an error Id: framework not found Pods clang: error: linker command failed with exit code 1 (use -v to see invocation) when trying to run an Xcode project in workspace. These are the steps I have followed, if anyone could let me know what I am doing wrong, that would be great!

1. git clone (link to bitbucket)
2. changed the configuration settings in the Xcode pods project to none for both debug and release
3. performed pod install
4. opened Xcode workspace file
5. tried to build in Xcode and received the error Id: framework not found Pods clang: error: linker command failed with exit code 1 (use -v to see invocation)

Edit Here is the podfile:

# Uncomment this line to define a global platform for your project platform :ios, '8.0' use_frameworks! source 'https://github.com/CocoaPods/Specs.git'  target 'Oncarb' do   pod 'Alamofire'   pod 'SwiftyJSON', '~> 2.2.0' end  #target 'OncarbTests' do #  pod 'Alamofire' #  pod 'SwiftlyJSON', '~> 2.2.0' #end 

Is there a step I am missing?

Thank you!

Answer 1

Sometimes after renaming a target or moving something, you can corrupt your pods installation. Luckily, there's an easier way to fix it than sudo make install's solution.

1. Run pod deintegrate to remove any trace of Cocoapods from your project.
2. Run pod install again to add it all back.

That's it, fixed.

Answer 2

This has fixed it for me:

1. Open up the workspace.
2. Click on the blue project icon (that expands into your file tree) on the left hand side of the screen
3. Just to the right, select "Targets" (as opposed to "Project"--Project is blue, Target is like a pencil and a ruler and a paintbrush making a triangle)
4. Click on the General tab
5. Go to the "Linked Frameworks and Libraries" section (all the way at the bottom)
6. Delete the Pods frameworks
7. Add Alamofire and SwiftyJSON

In my case, it didn't work unless I removed the pods frameworks, but I get the feeling that this is a workaround. Perhaps someone with more experience can comment.