My Experience Upgrading to CocoaPods 1.0

Background CocoaPods is a pretty solid dependency manager for third-party frameworks. The one painful part is how slow can be. Using offline mode () helps speed things up, but when you actually need to update, you're stuck sitting around for half the day. The good news is that version 1.0 significantly reduces update time, which was enough to convince me to finally upgrade. The Upgrade — High Hopes And this part is indeed straightforward. Running gets the job done easily. Note: When it was still in beta, you needed to add to install it. Upgrading the Project — Harsh Reality Of course, after the upgrade, the format needs to be updated — just check the documentation for the specifics. Once upgraded, naturally I had to "give it a spin." Running was noticeably faster. But when I tried to build, errors showed up: Even after fixing the issue here, and libraries still reported errors. This problem tortured me for months. Every time I upgraded to the 1.0 beta and ran , the same errors appeared. I kept assuming it was something wrong with my project configuration, and each attempt left the project settings in a mess — yet the errors persisted. I ended up rolling back to pods version 0.39 every single time. The Solution Eventually I found the answer on Stack Overflow: Cocoapods 1.0: Header files not found error using cocoapods "use_frameworks!" SWIFT It turned out to be related to , caching issues, and the need to upgrade the versions of and . So I ran and deleted everything under . I also updated to and to . Note that version requires Xcode 7.3 or later, so I pinned it to . Also be aware of this issue: 4.0.1 possibly breaks semver? #2704. After running again and building, there were no more errors. The CocoaPods upgrade was finally a success. I also tested archiving afterward, and that worked fine too.