CODEWITHSUNDEEP
iosxcodegitcocoapodsios-frameworks
Pami
Pami

Reputation: 423

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

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!

Upvotes: 42

Views: 51564

Answers (5)

Gerd Castan
Gerd Castan

Reputation: 6869

One possible cause in an explicit import of a Cocoapods framework into a test class / into the test target.

Example:

import XCTest
//import AlamofireImage
@testable import MyProject

// instead of importing AlamofireImage:
#if os(iOS) || os(tvOS) || os(watchOS)
    import UIKit
    public typealias Image = UIImage
#elseif os(macOS)
    import Cocoa
    public typealias Image = NSImage
#endif

I first imported AlamofireImage because I explicitly used typealias Image in my test as defined in AlamofireImage.

If it is as easy to prevent an import as in my example, do it. I just copied the definition of Image into my test class file.

If you think you really need that import, go on with the answer of William Hu. A footnote to his answer:

target 'MyProjectTests' do
   pod 'OnlyThatFrameworkYouImportIntoYourTest' 
end

You need to add only those pods to your test target, that you (need to) import explicitly.

Upvotes: 1

William Hu
William Hu

Reputation: 16189

My issues is when i ran test i got this error. Because i just install it in my 

target 'Project' do
   pod 'xxx'
end

You should also add it into your test target:

target 'ProjectTests' do
   pod 'xxx'
end

Upvotes: 5

Andrew
Andrew

Reputation: 239177

In my case, I had several frameworks listed in red. These were left over from previous Podfile configurations. I simply removed these frameworks listed in red and the problem was fixed.

Upvotes: 1

NiñoScript
NiñoScript

Reputation: 4593

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.

Upvotes: 31

sudo make install
sudo make install

Reputation: 5669

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.

Upvotes: 141

Related Questions