I will answer this question using an example. I have a fork of TTTAttributedLabel with some extra functionality I added here: https://github.com/getaaron/TTTAttributedLabel In order to use this in a Cocoapods project, I: Push my changes to my fork Configure my Podfile to get the changes & update Once you’ve pushed your changes to your fork, … Read more
Clearing a specific pod pod cache clean –all # will clean all pods pod cache clean ‘FortifySec’ –all # will remove all installed ‘FortifySec’ pods Sample output of pod cache clean ‘FortifySec’, for pods not using semantic versioning, this could result in many copies of same pod in cache: pod cache clean ‘FortifySec’ 1: FortifySec … Read more
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
Do the following things and you can import any swift file from “Pods” 1) Clean your project 2) Make sure that all your “Pods” > “Build Settings” > “Build Active Architecture Only” is set to “NO”. 3) Don’t run, just build your project. 4) Now, import any file from “Pods” to any swift file E.g.: … Read more
To update cocoapods just do sudo gem install cocoapods and then you should be at the correct version
I had the same problem. My solution was to open the project using the .xcworkspace, not the .xcodeproj. .xcodeproj only contains the main project; .xcworkspace includes everything including Restkit.
If you landed here on or after January 30th 2014, there is a break in CocoaPods causing this. Please read the related blog post found here: http://blog.cocoapods.org/Repairing-Our-Broken-Specs-Repository/ or do: pod repo remove master pod setup
It probably means their binary file has non-aligned pointer when they compile their code. In those cases the alignment basically defaults to 1 byte and hypothetically might impact performance. After updating to Xcode 8.3 public release I am still seeing this error, so Google might need to compile their static library with different settings to … Read more