CocoaPods Super User with Outdated and Update

In this lesson

To become a CocoaPods super user, you might want to learn these couple tips! pod outdated and pod update are great ways to stay up to date with any CocoaPods you might be using. pod outdated will help you figure out which pods you are behind on and pod updated can be used to update them right then and there regardless of any versions set in your Podfile. 

Kyle Roberts
Swift Guru at Large

Kyle's Series


Tap on time to skip ahead


Hello world. Kyle here with I’ve got a few tips for being a CocoaPods super user. What I mean by that is that I will be demonstrating some commands that will not always be used in typical or normal CocoaPods development. Usually, you create your Podfile, you define all your Pods and then you just run a pod install. But, there are a few useful commands that you can see just to make sure that your Podfile, and your app itself, is up to date with the most recent code.


I’m going to run pod outdated now. When that completes, we’ll see that it prints that Alamofire and the version we’re currently using is 3.3.0, now has a newer version of 3.4.0. That’s all the pod outdated command does. It doesn’t actually change anything. It just compares what’s in our Podfile.lock to what’s actually out there on GitHub or on


Let’s say that we want to actually update our Alamofire CocoaPods to 3.4.0. We’ve checked the documentation, we think that everything is going to be fine or that we are willing to make any changes that we need to make to run version 3.4.0. To do that, all you have to do is pod update and that will go through all of the Pods in your Podfile.lock and update them to the newest versions. That is completed. We can see that it has installed Alamofire 3.4 and that it was 3.3.0. All of the other CocoaPods are the most recent versions that we’re using.


One gotcha with this is that it does not update your Podfile. You can see that we’re still pointing to 3.3.x right now. One thing you have to remember to do when you’re running pod outdated and that you do run a pod update is to update your Podfile as well. Since pod outdated and pod update only deal with your Podfile.lock, which is what is actually included in the Pods project, if we had not updated our Podfile, our Podfile.lock would say that we’re using version 3.4.0 of Alamofire, which we were even though the Podfile was still referencing 3.3.x. That’s just something you have to remember to do when you’re running Pod update.  


One thing you can do after you run a pod outdated, it’s going to tell us that none of the Pods are actually different. No Pod updates are available. We just updated Alamofire. You can run a pod update and then the Pod name just to only update that one Pod. In that situation you’re also going to have to update the Podfile again.


Just stuff to keep in mind. I hope those are some tips to become a CocoaPods super user. Those are some pretty useful things. Running a pod outdated every once in a while is a pretty good practice to make sure that you are at least aware of any new versions of the frameworks that you’re using.

Additional Info

Register to get access to additional resources and info.