Update Make sure your Podfile includes link_with on targets missing a config file. Cocoapods only sets the first target by default otherwise. e.g. platform :osx, ‘10.7’ pod ‘JSONKit’, ‘~> 1.4’ link_with ‘Pomo’, ‘Pomo Dev’, ‘Pomo Tests’ —— End Update Note: Please do note that you have to look into Project->Info->Configurations for steps below. I had … Read more
If the message says you are missing a lib: I got same problem and it was fixed after running pod setup and then pod install If the missing directory is the ruby dir you can do: You have probably updated your osx or ruby gem recently and its PATH is still linking to the old … Read more
If the project uses CocoaPods be aware to always open the .xcworkspace file instead of the .xcodeproj file.
This definitely works most of the time: Go to your target Build Settings -> Other linker flags -> double click . Add $(inherited) to a new line. If you have problem with “…target overrides the GCC_PREPROCESSOR_DEFINITIONS build setting defined in…” then you must add $(inherited) to your target Build Settings -> Preprocessor Macros
The Podfile.lock keeps track of the resolved versions of each Pod installed. If you want to double check that FlurrySDK is using 4.2.3, check that file. Note: You should not edit this file. It is auto-generated when you run pod install or pod update
If your Architectures and Valid Architectures are all right, you may check whether you have added $(inherited) , which will add linker flags generated in pods, to Other Linker Flags as below:
You could try running in verbose mode: pod install –verbose That’ll show you what cocoa pods are up to: Setting up CocoaPods master repo Cloning spec repo `master` from `https://github.com/CocoaPods/Specs.git` (branch `master`) $ /usr/bin/git clone ‘https://github.com/CocoaPods/Specs.git’ master Cloning into ‘master’… (as suggested here) For me the above step took quite a long time as the … Read more
Make sure you have the latest version of CocoaPods installed. $ pod update PODNAME was introduced recently. See this issue thread for more information: $ pod update When you run pod update SomePodName, CocoaPods will try to find an updated version of the pod SomePodName, without taking into account the version listed in Podfile.lock. It … Read more
I encountered this problem when upgrading to Mac OS High Sierra. This was my fix: sudo gem install cocoapods I found this answer on the CocoaPods issue list on Github.
Run following command brew cleanup -d -v Then run below command brew install cocoapods Note: If you see failed to link then run brew link cocoapods If linking is getting failed then run brew link –overwrite cocoapods This is how it get solved for me For someone who is having m1 chip system they need … Read more