SolvedCocoaPods Modules not found in test targets

🌈

• I've read and understood the *CONTRIBUTING guidelines and have done my best effort to follow.

Report

I am having trouble with "No such module 'MODULE_NAME'" errors.

Example Project

What did you do?

1. Created a new Xcode project
2. Created Podfile using template generated by running pod init
3. Added the pod Alamofire to the target "Demo App"
4. Added the pod OHHTTPStubs to the targets "Demo AppTests" and "Demo AppUITests"
5. Ran pod install --verbose
6. Opened workspace up in Xcode
7. Opened Demo_AppTests.swift and added the following to the top of the file:

import XCTest
import Alamofire
import OHHTTPStubs
@testable import Demo_App

8. Tried to use either of the libraries imported (Alamofire or OHHTTPStubs) and autocomplete wouldn't come up.
   Error on import Alamofire was "No such module 'Alamofire'".
   Error on import OHHTTPStubs was "No such module 'OHHTTPStubs'".

NOTE: Adding pod 'Alamofire' to the testing targets also results in the same behaviour.

These errors would sometimes disappear for around ~5 secs or until a key was pressed to make a change to the swift file if I build the targets generated by CocoaPods or ran both CMD + SHIFT + U and CMD + SHIFT + R.

Sometimes running CMD + U would let the test target compile and other times it would not.
I have also tried clearing derived data.

What did you expected to happen?

I expected that the pod Alamofire would be available for use in all targets.
I expected that the pod OHHTTPStubs would be available for use in all test targets.

What happened instead?

In the test targets the modules Alamofire and OHHTTPStubs could not be found.

That is:

Pod Alamofire is missing from the targets "Demo AppTests" and "Demo AppUITests".
Pod OHHTTPStubs is missing from the targets "Demo AppTests" and "Demo AppUITests".

Pod Env

Stack

   CocoaPods : 1.0.0.beta.4
        Ruby : ruby 2.3.0p0 (2015-12-25 revision 53290) [x86_64-darwin15]
    RubyGems : 2.5.1
        Host : Mac OS X 10.11.3 (15D21)
       Xcode : 7.2.1 (7C1002)
         Git : git version 2.5.4 (Apple Git-61)
Ruby lib dir : /Users/brettbest/.rubies/ruby-2.3.0/lib
Repositories : master - https://github.com/CocoaPods/Specs.git @ e77d73db1bdaebf03fee6dab82aae3a90c99d367

Installation Source

Executable Path: /Users/brettbest/.gem/ruby/2.3.0/bin/pod

Plugins

cocoapods-deintegrate : 1.0.0.beta.1
cocoapods-plugins     : 1.0.0.beta.1
cocoapods-search      : 1.0.0.beta.1
cocoapods-stats       : 1.0.0.beta.3
cocoapods-trunk       : 1.0.0.beta.2
cocoapods-try         : 1.0.0.beta.2

Podfile

platform :ios, '9.0'
use_frameworks!
inhibit_all_warnings!

target 'Demo App' do
  pod 'Alamofire'
end

target 'Demo AppTests' do
  pod 'OHHTTPStubs'
end

target 'Demo AppUITests' do
  pod 'OHHTTPStubs'
end

Thanks for the great ticket! So, pods would be passed to a target by inheritance here, but you're not inheriting them. To quote the guide

platform :ios, '9.0'
inhibit_all_warnings!

target 'MyApp' do
  pod 'GoogleAnalytics', '~> 3.1'

  # Has it's own copy of OCMock
  # and has access to GoogleAnalytics via the app
  # that hosts the test target

  target 'MyAppTests' do
    inherit! :search_paths
    pod 'OCMock', '~> 2.0.1'
  end
end

So in this case you want to do something like:

target 'Demo App' do
  pod 'Alamofire'

  target 'Demo AppTests' do
    inherit! :search_paths
    pod 'OHHTTPStubs'
  end

  target 'Demo AppUITests' do
    inherit! :search_paths
    pod 'OHHTTPStubs'
  end  
end

Though I bet you could improve that even further, I think, this is guesswork now though:

target 'Demo App'
pod 'Alamofire'

abstract_target 'tests' do
  target 'Demo AppTests'
  target 'Demo AppUITests'

  inherit! :search_paths
  pod 'OHHTTPStubs'
end

I believe this thread got off-topic. The initial issue is not the inheritance, but the fact that adding a pod to a test target doesn't work, as xCode says No Such Module 'Quick'. Is there any official fix for this? or maybe an official extra step that we need to do, that is not documented?

@AshleyDeng I got quite a long list of schemes, have you found a solution since that doesn't require all this manual work 😅 i've got the same issue.

Running pod deintegrate, changing the Podfile to

platform :ios, '9.0'
use_frameworks!

target 'Demo App' do
  pod 'Alamofire'

  abstract_target 'tests' do
    platform :ios, '9.0'
    target 'Demo AppTests'
    target 'Demo AppUITests'

    inherit! :search_paths
    pod 'OHHTTPStubs'
  end
end

and using CocoaPods/Core#308 together fix the issue

I know this issue has been closed but I just experienced this issue with Cocoapods 1.0.0 and the way i solved it is as follows... When I tried the new cocoapods 1.0.0 syntax for the Podfile like so:

target 'Chat_Example' do
    pod 'ChatKit', :path => '../'
    target 'Chat_Example_Tests' do
         inherit! :search_paths
    end
end

then my test target was not able to import the ChatKit module. However if I write the Podfile as so
then the tests are able to import the module:

def reusepods
    pod 'ChatKit', :path => '../'
end

target 'Chat_Example' do
     reusepods
end

target 'Chat_Example_Tests' do
    reusepods
end