The definitive guide to installing and updating pods The difference between and is subtle, and it isn’t always clear which you should use. But having a good understanding of what these commands do gives you much finer control over how dependencies are managed in your project, so it’s worth knowing the difference. pod install pod update In the first part of this article I’ll give you a list of recipes showing whether you should run or in some common situations. Then in the second part I’ll explain why the different commands do different things, and how uses the file to make it all happen. pod install pod update CocoaPods Podfile.lock Part 1: Recipes For these recipes to work, ensure that and are committed to source control. Podfile Podfile.lock You are setting CocoaPods up in a project for the first time and have created your Podfile pod install This will install the latest version* of each of the pods you specified in your new . It will also create a file if one didn’t already exist. Podfile _MyProject_.xcworkspace You added a new pod to your Podfile pod install This will install the latest version* of any new pods added to your Podfile, leaving your other pods unchanged. If you were to run instead, it would install the new pods update each of your existing pods to its latest version*. pod update and You want to get the latest version of all pods in your Podfile pod update This will go through all of your pods and make sure that the latest version* of each is installed in your project. You want to get the latest version of only one pod in your Podfile pod update _SomePod_ This will make sure that the latest version* of the pod you specify is installed, whilst leaving your other pods unchanged. You are working with a development pod and want to get your latest changes pod update _MyDevelopmentPod_ This will make sure that the latest version of your pod is installed, whilst leaving your other pods unchanged. You have downloaded the source for an existing project that uses CocoaPods pod install This will install all pods in the Podfile at the that were previously installed in this cut of the source code. exact versions If you were to run instead, it would install the latest version* of each of the pods in the Podfile. This could prevent the project from building if the latest versions weren’t compatible with other code in the project. I’d recommend running to get the code building, then updating pods as necessary in a controlled manner. pod update pod install You are writing a script to build a project on a build server pod install This will install all pods in the Podfile at the exact versions that were installed in the version being built. This is important for a stable build, because these are the versions that the code was developed against, and it means that every build of that cut of code will use the same pod versions. If you were to use instead, your build could potentially use different versions of pods each time it builds. pod update Xcode is reporting weird build errors relating to pods This occasionally happens after updating pods, or after switching between branches of a project that contain the same pods at different versions. Delete the directory, then run /Pods pod install This will reinstall all pods in the Podfile at the exact versions that were previously installed, and is usually enough to straighten out any issues that Xcode can find itself with. Sometimes people suggest deleting the directory the file, then running . This will solve any issues with Xcode, but will also upgrade each of the pods in the Podfile to its latest version*. /Pods and Podfile.lock pod install Part 2: How it works The difference between and lies in how they interact with the file. This file is used to store the exact version of each pod that is currently installed in your project. pod install pod update Podfile.lock The easiest way to understand how it works is to look at the following diagram (disclaimer: ). this is a simple schematic rather than an accurate technical diagram pod update ignores when checking for versions. It looks for the the latest available version* of a pod, and installs it if it isn’t already installed. pod update Podfile.lock pod install looks in first when checking for versions. If a version of the pod is listed in , it will install If that pod isn’t listed in (or if doesn’t exist yet), it will behave as for , i.e. it finds the latest available version* and installs it. pod install Podfile.lock Podfile.lock that exact version. Podfile.lock Podfile.lock pod update In both cases, CocoaPods then updates with any new version numbers that were installed. Podfile.lock This is what allows you to use pod versions consistently across different installs of a project (i.e. when installing from a repository, across multiple team members, or on a build server), and is why should be committed to source control. Podfile.lock Summary In this article I’ve given recipes showing whether to run or in a number of common situations. I’ve then described how and why the two commands work in different ways. If you’ve found it useful, please give it a clap and / or share, and follow me for other useful articles. pod install pod update [*] By I mean . See the section on in the official guide to for more information. latest version latest version that satisfies the requirements and dependencies in your Podfile Specifying pod versions The Podfile Gabrielle is an iOS specialist who leads technical teams creating mobile apps. For app development and more, please contact her at Intercept IP (formerly Control F1), look her up on Linked In or say ‘hi’ on twitter at @GabEarnsh . Read more of my stories: _Change text styles in Xcode as easily as in your design file_medium.com Implementing a Sketch text design system in your Xcode project _How to create all of your icon sizes in seconds_medium.com Painless icon generation for iOS apps with Sketch and Xcode — Part 1 _Make unit tests easier to code, review and maintain_medium.com Next-level Swift unit tests using the builder pattern
