CocoaPods Blog

CocoaDocs documentation sun-setting

TL;DR: CocoaDocs will stop generating DocSets for new libraries and versions using CocoaPods towards the end of May.

I started CocoaDocs back in February 2013, and have been running and maintaining it for the last 4 years. CocoaDocs started as a way to generate documentation for Objective-C projects via Appledoc. When Swift came out, Jazzy support was added to the app. Since then, CocoaDocs has grown organically over the years into a tool to generate useful metadata for any CocoaPods library used in the website.

I intend to remove the support for generating HTML pages and DocSets for new libraries uploaded to trunk by the end of May.

Read on β†’

CocoaPods Specs Repo Sharding

In March, CocoaPods hit an unfortunate problem with our Specs Repo being rate limited.

We announced that we were planning on Sharding the Specs Repo, but were hesitant to do it instantly. Now over six months later we are planning on running the scripts.

  • If you are using CocoaPods 1.x - you should not see any changes.
  • If you are using CocoaPods 0.39 and below, you will see an error saying that your version of CocoaPods is not supported. Previous to this, our minimum version was 0.32.

For people who want to continue using 0.x versions, we will be replicating the Specs repo from the commit before the repo was sharded. This means you can add:

source ""

To the top of your Podfile, and CocoaPods will only use the archived repo, instead of using the new repo structure. You will also need to set your local Specs repo to a version before the transition:

cd ~/.cocoapods/repos/master/
git fetch origin master
git checkout v0.32.1

To run pod install, you will also need to use --no-repo-update.

We do not have the resources to maintain multiple versions of CocoaPods in our spare time, and so we recommend that instead of doing the above, you migrate to the latest versions of CocoaPods in your projects.

We are planning to do it on Friday November the 11th, so there will be scheduled downtime on pushing new Pods to Trunk during the process of updating and verifying that it was successful.

2016 CocoaPods State of the Union

Apple have their annual WWDC keynote and Developer State of the Union. We have ours. We're planning a great opening event to WWDC week: The CocoaPods Alt State of the Union. You should join us, and hear about what's happened in CocoaPods in the past year, and what's to come in the next. This year's is going to be extra-special, as we'll all get to celebrate the release of CocoaPods 1.0 together πŸŽ‰

Read on β†’

CocoaPods App 1.0

After about a year of work, with the release of CocoaPods 1.0, the corresponding Mac App is also ready for public usage.

This is no big reveal, we've been advertising it's existence on our websites for a while. I've already talked a little bit about the tech behind the Mac App, so this post is the one that makes you say your team "we should use this instead of the gem".

So let me put my best hat on, and try to pursuade you that using the CocoaPods Mac App is a great idea.

Read on β†’

CocoaPods 1.0

I'm incredibly happy to say that, after an incredible four and a half years of development, we just released CocoaPods 1.0. It's been a long road to get here, but the journey has told the story of the larger Cocoa open source community -- from new versions of Xcode to new languages and platforms, CocoaPods has grown over the years to support a staggering number of developers.

Read on β†’

CocoaPods Socks available for the next four weeks.

​ TL;DR: We’re doing crowd-funded socks for charity, using Knitout. With all profit going to charity: water.

CocoaPods was started in 2011. We are a community run project, with no large-scale corporate backing. We're often asked if we'd do something like t-shirts or hoodies.

We don't want to use CocoaPods' popularity to make money. So, we are putting all profits into a charity. Want to know more? Go see