I've got an iOS project on Xcode that uses Firebase, which was downloaded through Cocoapods. Everything was working fine - running on both simulators and devices - until I tried to run the app on an iPad 7th generation simulator and this error was thrown:
ld: framework not found GoogleAppMeasurement
clang: error: linker command failed with exit code 1 (use -v to see invocation)
Now the project won't build on any device or simulator. I navigated through the Pods folder to check if GoogleAppMeasurement had its framework and it does. Besides this one error, there's no frameworks highlighted in red (like some other related questions mention) or other indication of what could have gone wrong.
Here's my pod file in case it helps:
# Uncomment the next line to define a global platform for your project
# platform :ios, '9.0'
target 'my project's name' do
# Comment the next line if you don't want to use dynamic frameworks
use_frameworks!
# Pods for my project's name
pod 'Firebase/Auth'
pod 'Firebase/Firestore'
pod 'Firebase/Core'
end
This same error has popped up on another one of my firebase-reliant projects and I've had no luck getting rid of it there either. Any suggestions on how to keep troubleshooting are welcome.
Related
I have just made a podfile for firebase in my app however I am getting this error and the podfile has everything in it. It is telling me Error Message: Showing Recent Errors Only ld: framework not found GoogleToolboxForMac clang: error: linker command failed with exit code 1 (use -v to see invocation)
I go onto the Pods.xcodeproj xcode project and GoogleToolBoxForMac is there.
I researched everything to fix it and nothing helped.
Podfile: firebase instructions said to put 'Firebase/Core'
target 'Game' do
# Comment the next line if you're not using Swift and don't want to use dynamic frameworks
pod 'Firebase/Core'
use_frameworks!
# Pods for Game
target 'GameTests' do
inherit! :search_paths
# Pods for testing
end
target 'GameUITests' do
inherit! :search_paths
# Pods for testing
end
end
I tried running on XCWorkSpace it ran however my app did not load like it always has. I also did every answer the possible duplicate had. I don't even see all my swift source files(like viewcontrolller gamescene and node files) on the XCWorkSpace for my game.
Having a react-native project, which won't build on target "Staging" since I've setup cocoapods and using xcworkspace file since then (needed for firebase integration of react-native-firebase). When trying to build for taget "staging", I'll get this error:
ld: library not found for -lPods-[app]
clang: error: linker command failed with exit code 1 (use -v to see invocation)
It works on debug, and (well at least it doesn't throw an error) when I archive the project.
I've having a "staging" target because of code-push. Using react-native at version 0.48.4 and Xcode 9 (created it following this guide, but before using cocoapods)
My podfile:
platform :ios, '9.0'
target 'xx' do
#use_frameworks!
# Pods
pod 'Firebase/Core'
pod 'Firebase/Analytics'
pod 'Firebase/Database'
pod 'Firebase/Messaging'
pod 'Firebase/Auth'
pod 'Firebase/Storage'
end
Tried with and without use_frameworks!, cleaning project, deleted DerivedData, deintegrating and reintegrating pods.
What could cause this? (Please tell me if you need more information)
What worked for me:
Deintegrated all pods using pod deintegrate (using enter link description here)
pod install
Removed [Project name] > Frameworks > Pods_[Project name].framework (which was red, but there are actually more files being red)
Build succeeded
Was doing this with the help of this post. Thanks also to Maurice for trying to help me.
I had this issue. In my case it was a react-native app added Firebase Analytics. As of July 2018, all apps must be built with iOS 11 per Apple: developer.apple.com/ios/submit/
Once I went to my General tab and scrolled down to Deployment Info / Deployment Target and changed it from 10.x which is what I was targeting, to 11.x - the app built/archived and I was able to submit.
Set your PODS_CONFIGURATION_BUILD_DIR of "staging" as "release" ${PODS_BUILD_DIR}/Release$(EFFECTIVE_PLATFORM_NAME).
Check the Frameworks folder and remove red files.
check whether the SEARCH_PATHS is correct at Pods-XXXX.debug.xcconfig or Pods-XXXX.release.xcconfig
LIBRARY_SEARCH_PATHS = $(inherited) "$(PODS_ROOT)/path/to/your folder"
I have already raised this kind query, still I did not get any helpful answers, so that, I am posting this again.
I am installing firebase, googlesigin, twitterkit and fabric to my swift application by Cocoapods.
If I installed only Fabric I am able to compile and run the application. But, If I tried to install GoogleSignIn and TwitterKit, Fabric, its installing successfully, but, not able to run, getting compiler error of following.
ld: framework not found FileProvider for architecture x86_64
clang: error: linker command failed with exit code 1 (use -v to see invocation)
And my podfile is like following.
# Uncomment the next line to define a global platform for your project
# platform :ios, '9.0'
target 'pod installation' do
# Comment the next line if you're not using Swift and don't want to use dynamic frameworks
use_frameworks!
pod 'Fabric'
pod 'TwitterKit'
pod 'Firebase/Database'
pod 'Fabric'
pod 'GoogleSignIn'
# Pods for sample pod
# Pods for pod installation
target 'pod installationTests' do
inherit! :search_paths
# Pods for testing
end
end
Attached screenshot, any help from anyone. I am trying to fix this from two days and Really thanks for who helping this fix.
Note : I am using Xcode 8.3.2 and I don't have any real device with me now, and I am not using any FileProvider framework in my application.
Perhaps your pods using FileProvider-framework.
FileProvider-framework is available from iOS11.0 + with Xcode 9 hence You should upgrade with Xcode 9 to avail this framework.
I am trying to install the Facebook SDK using Cocaopod. I managed to install fine.
This is what is inside the Podfile.
# Uncomment the next line to define a global platform for your project
# platform :ios, '9.0'
target 'Login-FB' do
# Comment the next line if you're not using Swift and don't want to use dynamic frameworks
use_frameworks!
# Pods for Login-FB
pod 'FBSDKCoreKit'
pod 'FBSDKShareKit'
pod 'FBSDKLoginKit'
end
However, after installation, when I run Build in the App, I get the error shown below:
ld: framework not found Bolts
clang: error: linker command failed with exit code 1 (use -v to see invocation)
It seems like my Pod files are not really pulling the framework down from its source. I am not sure why. Because I think this Pod install command should create a folder called Framework and it should have the Frameworks readily available, but it is not so in my case.
I am currently having problems installing Pure Layout using Cocoa Pods. Ive managed to install it fine in a blank project with no problems. But when installing into my project i keep getting the following error:
ld: framework not found PureLayout
clang: error: linker command failed with exit code 1 (use -v to see invocation)
Ive had a search through stack overflow for any possible solutions and have tried adding the framework search path to the target, trying to delete cocoa pods and do a fresh install onto the project.
Initially before adding 'PureLayout' to the pod file i got a similar error:
ld: framework not found Pods
To resolve this i removed the red pod framework file from the linked library and framework folder. Which then built fine.
Thank you in advance for anyone who helps me solve this.
Below is my Podfile:
# Uncomment this line to define a global platform for your project
platform :ios, '8.1'
# Uncomment this line if you're using Swift
use_frameworks!
target '****' do
pod 'Google/Analytics'
pod 'Fabric'
pod 'Crashlytics'
pod 'PureLayout'
end
target '****Tests' do
end
Managed to solve this issue by:
-Select Pods Project
-Build Settings
-Set BaseSDK to iOS SDK (since pod install clears it)
-Set Build Valid Architecture Only to NO.
Following this process the project now builds. I was able to import Pure Layout into my Bridging Header and access the pure layout functions in any of my view controller classes.