How To Remove Cocoapods From Mac

<Installing CocoaPods

• If yous are installing on macOS 10.9.0-10.9.ii, you may run into an issue when RubyGems tries to install the json jewel. To fix this follow these instructions.

• Afterwards upgrading from macOS 10.8 to ten.9 the installed CocoaPods gem doesn't work anymore, fifty-fifty after re-installing the gem. To solve this, y'all might need to uninstall the gem first and then re-install.

                                            $ gem uninstall cocoapods  $ precious stone install cocoapods                                      

• The gem might not be able to compile, to solve this you might need to symlink GCC.

• If you used an pre release version of Xcode you might need to update the control line tools.

• CocoaPods is not uniform with MacRuby.

• If you get the error "Error: While executing precious stone ... (Errno::EPERM); Operation not permitted - /usr/bin/fuzzy_match" then try: $ sudo jewel install -northward /usr/local/bin cocoapods

<Using the CocoaPods Project

1. Employ the Xcode workspace <Project>.xcworkspace, non the Xcode project.

2. If something doesn't seem to work, first of all ensure that yous are not completely overriding any options set from the Pods.xcconfig file in your project's build settings. To add values to options from your project's build settings, prepend the value list with $(inherited).

3. If Xcode tin't detect the headers of the dependencies:

   • Bank check if the pod header files are correctly symlinked in Pods/Headers and you are not overriding the HEADER_SEARCH_PATHS (encounter #1).
   • Brand sure your projection is using the Pods.xcconfig. To check this select your project file, so select information technology in the second pane over again and open the Info section in the tertiary pane. Under configurations y'all should select Pods.xcconfig for each configurations requiring your installed pods.
   • If Xcode still tin can't find them, as a last resort y'all can prepend your imports, due east.k. #import "Pods/SSZipArchive.h".

4. If you lot're getting errors well-nigh unrecognised C compiler command line options, e.thousand. cc1obj: mistake: unrecognised control line option "-Wno-sign-conversion":

   • Make sure your project build settings are configured to use "Apple LLVM compiler" (clang)
   • Are you setting the CC, CPP or CXX surround variable, e.g. in your ~/.profile? This may interfere with the Xcode build process. Remove the surroundings variable from your ~/.profile.

5. If Xcode complains when linking, due east.g. Library non found for -lPods, it doesn't find the implicit dependencies:

   • Get to Product > Edit Scheme
   • Click on Build
   • Add the Pods static library, and make sure it'south at the summit of the list
   • Clean and build again
   • If that doesn't work, verify that the source for the spec yous are trying to include has been pulled from GitHub. Do this by looking in <Project Dir>/Pods/<Proper name of spec you are trying to include>. If it is empty (it should not exist), verify that the ~/.cocoapods/master/<spec>/<spec>.podspec has the correct git hub url in it.
   • If yet doesn't piece of work, check your Xcode build locations settings. Become to Preferences -> Locations -> Derived Information -> Advanced and gear up build location to "Relative to Workspace".

• If you tried to submit app to App Store, and institute that "Product" > "Archive" produce nix in "Organizer":
  • In Xcode "Build Settings", find "Skip Install". Set up the value for "Release" to "NO" on your awarding target. Build again and it should piece of work.

Different Xcode versions tin can have various issues. Enquire for help and tell us what version you're using.

<Tin can I workaround 'Duplicate Symbol' errors with static libraries?

This usually occurs when you're using a closed-source third-party library that includes a common dependency of your application. One brute-force workaround is to remove the dependency from the static library, as described here

However, in general, the vendor should really prefix any dependencies information technology includes, so you don't need to deal with it. When this happens, please contact the vendor and ask them to fix it on their side and use the above method every bit a temporary workaround.

<I'm getting permission errors while running pod commands

As of CocoaPods 0.32.0 nosotros have removed the power to run the pod commands as root to foreclose CocoaPods from getting into an inconsistent state when you mix and match running equally root.

If you have ran CocoaPods as root at 1 stage you lot may start getting permission denied errors when performing certain operations. When yous meet permission errors you lot may need to delete old files which run every bit root such every bit the enshroud data. You can do this with the following commands.

                $ sudo rm -fr ~/Library/Caches/CocoaPods/ $ sudo rm -fr ~/.cocoapods/repos/master/                              

Alongside those global files, at that place may as well be a Pods directory in whatever identify you lot have a Podfile. If yous nonetheless receive permission errors you lot should delete this directory too, and afterwards run pod install.

<The Fix I want is in master / a branch, but I'g blocked on this right now

In that location is a guide for using a version of CocoaPods to try new features that are in discussion or in implementation phase.

<I didn't observe the solution to my trouble!

We have multiple avenues for back up, here they are in the society we adopt.

• Stack Overflow, get yourself some internet points. This keeps the pressure off the CocoaPods dev team and gives usa time to work on the project and not back up. Ane of the advantages of using Stack Overflow is that the answer is and so hands accessible for others.

• CocoaPods Mailing Listing, the mailing list is mainly used for announcements of related projects and for support.

• If your question is regarding a library (to exist) distributed through CocoaPods, refer to the spec repo.

<I call up this is a bug with CocoaPods

In this case we want to get information technology on a GitHub issues tracker, we utilize this to keep track of the development work we take to do.

• Search tickets earlier you file a new one. Add to existing tickets if you take new data nigh the issue.

• Only file tickets nigh the CocoaPods tool itself. This includes CocoaPods, CocoaPods/Cadre, and Xcodeproj.

• Go along tickets short simply sweet. Brand sure you lot include all the context needed to solve the upshot. Don't overdo information technology. Great tickets allow u.s. to focus on solving problems instead of discussing them.

Source: https://guides.cocoapods.org/using/troubleshooting

Share this post