Reputation: 8685
I've been banging my head against a wall with this for the last few days but despite multiple Google/SO/Github searches I can't find a resolution to the issues I'm having!
All I'm trying to do is create some unit tests for my app which makes use of Firebase pods.
I'm using Xcode 7.3.1 & Cocoapods 1.0.1. Update: Issue remains with Xcode 8.0
With this podfile:
platform :ios, '9.0'
use_frameworks!
inhibit_all_warnings!
target 'MyApp' do
pod 'Firebase'
pod 'Firebase/Auth'
pod 'Firebase/Database'
pod 'Firebase/Storage'
target 'MyAppTests' do
inherit! :search_paths
end
end
In my XCTest class I get
Missing required module 'Firebase'
error at @testable import MyApp
Alternatively with this podfile:
platform :ios, '9.0'
use_frameworks!
inhibit_all_warnings!
def common_pods
pod 'SwiftyTimer'
pod 'Firebase'
pod 'Firebase/Auth'
pod 'Firebase/Database'
pod 'Firebase/Storage'
end
target 'MyApp' do
common_pods
end
target 'MyAppTests' do
common_pods
end
The tests build but my console is littered with warnings e.g.:
Class <-FirebaseClassName-> is implemented in both ...MyApp... and ...MyAppTests... One of the two will be used. Which one is undefined
Upvotes: 141
Views: 50467
Reputation: 641
$(SRCROOT)/Pods
with recursive, then Xcode will resolve the path for you.Here is Example
Upvotes: 62
Reputation: 503
A simpler method that also works:
target 'MyApp' do
pod 'Firebase/Auth'
pod 'Firebase/Database'
pod 'Firebase/Storage'
target :MyAppTests
end
Upvotes: 8
Reputation: 3082
Missing required module Firebase
NO CocoaPods solutionFor those who encounter the same problem but NOT using CocoaPods:
If you're using Firebase, than you have some folder containing Firebase.h
and module.modulemap
file. For example - YOUR_PROJECT_DIR/Linking
If your Main project target is working correct way, than you should go to ProjectSettings -> Targets. Select test target. Search for User headers
and add the path to YOUR_PROJECT_DIR/Linking
. Select recursive
option and you should be good to go.
See the screenshot for more details:
Upvotes: 0
Reputation: 11774
Adding ${SRCROOT}/Pods/Firebase/CoreOnly/Sources
into the unit test target's "Header search paths" fixed the problem.
Steps:
After this the tests can run and the error will disappear.
Upvotes: 10
Reputation: 524
I tried all the above and ran into various different errors, originally starting with Missing required module 'Firebase'
, then getting "Class ... is implemented in both ... "
or linker issues if I tried to add Firebase Pods to my test target.
The solution that worked for me was to:
$(inherited) non-recursive
$(SRCROOT)/Pods/Headers/Public recursive
$(SRCROOT)/Pods/Firebase recursive
At this point cleaning the build folder, re-building then re-running the tests worked for me. Hope this helps someone!
Upvotes: 5
Reputation: 1451
As @Will mentioned an issue around Header Search Paths after CocoaPods installation.
I have a project with multiple targets where pod 'Firebase' embedded into separate module, lets say MyProject-Shared
. Firebase pod at 'Podfile' installed only for 'MyProject-Shared' target. Other modules, which wants to use 'MyProject-Shared' can't be compiled due an error:
'missing required module "Firebase" '
The trick in my case was to add following missing header search path at each target's Build Settings referencing to Analytics-Framework:
"${PODS_ROOT}/Firebase/CoreOnly/Sources"
Hope it will save your time.
Upvotes: 1
Reputation: 37505
The problem is recorded in the firebase project here:
https://github.com/firebase/firebase-ios-sdk/issues/58
There is a workaround:
Add "${PODS_ROOT}/Firebase/Core/Sources" to your Tests target only under Build Settings -> Header Search Paths
but this is also fixed by upgrading to CocoaPods 1.4.0 or later, which is a better solution.
At the time I'm writing this (November 2017) cocoapods 1.4.0 is still in beta, so to install it you need to explicitly request the beta:
gem install cocoapods --pre
This and then doing a pod install
solved the problem running my tests.
Upvotes: 7
Reputation: 1073
Three Steps before I could get this to work:
CocoaPods : 1.5.0 Swift 4 Firebase : 4.13.0
Step 1: Make sure to add the following target block into your podfile.
# Uncomment the next line to define a global platform for your project
platform :ios, '11.3'
target 'TIMII' do
# Comment the next line if you're not using Swift and don't want to use dynamic frameworks
use_frameworks!
# Pods for TIMII
pod 'Firebase/Core'
pod 'Firebase/Database'
pod 'Firebase/Auth'
pod 'Firebase/Storage'
target 'TIMIITests' do
inherit! :search_paths
pod 'Firebase/Core'
end
end
Step 2: Within the YourAppTests Project Navigator Build Settings tab. Find the Header Search Path row and add to Debug the following line
$(inherited) ${PODS_ROOT}/Firebase/Core/Sources
Step 3: In terminal run:
pod update
Upvotes: 9
Reputation: 431
Add "${PODS_ROOT}/Firebase/Core/Sources" to your Tests target only under Build Settings -> Header Search Paths
Upvotes: 1
Reputation: 4270
The issue is that Firebase does something special with the Header Search Paths after CocoaPods generates its own value for the setting so CocoaPods doesn't pick up on this change in order to carry it over to the test target. You can solve this one of two ways:
Locate MyAppTests.<configuration>.xcconfig
in the file navigator and add the following to HEADER_SEARCH_PATHS
:
${PODS_ROOT}/Firebase/Analytics/Sources
[*]
Find the setting for Header Search Paths in Build Settings and add that same value as in option 1 to the list. You shouldn't need to set it as recursive.
* As per AKM's comment, this changed to ${PODS_ROOT}/Firebase/Core/Sources
in version 3.14.0
Upvotes: 35
Reputation: 864
Try changing the inheritance to :complete
, as in:
target 'MyAppTests' do
inherit! :complete
end
Importantly it allows anyone else checking out your repo to just do a pod update
as usual without having to copy .xcconfig
files or other hackery just to build.
Upvotes: 64
Reputation: 413
I had a similar problem. Phrased in terms of your question, I copied the contents of my MyApp.<configuration>.xcconfig
file to my MyAppTests.<configuration>.xcconfig
file. I cleaned and built the tests, and it worked.
Upvotes: 2
Reputation: 8685
The solution for me was to update cocoapods to version 1.1.0.rc.2.
sudo gem install cocoapods --pre
Upvotes: 4
Reputation: 1517
I had the same issue. I solved it by moving pod 'Firebase'
to my test target. Change your Podfile to this:
platform :ios, '9.0'
use_frameworks!
inhibit_all_warnings!
target 'MyApp' do
pod 'Firebase/Auth'
pod 'Firebase/Database'
pod 'Firebase/Storage'
target 'MyAppTests' do
inherit! :search_paths
pod 'Firebase'
end
end
Upvotes: 97