I’m working with a client to update one of their iOS apps. The Xcode project uses CocoaPods for dependency management. I’m not a fan of CocoaPods, but I grin and bear it when working with existing client projects.
Yesterday I needed to update a class, one .h file and one .m, from an open source project, so I ran pod update on the project. This told me I needed to update my install of CocoaPods, so I did. This in turn updated a ton of other Ruby Gems on my system. It was annoying having to go through the update process when all I needed was two files that I could have copied from github in less time, but no harm done, right? WRONG!!!
Today I go to publish a new blog post. I use Jekyll to convert my site to static HTML. Guess what? Yesterday’s CocoaPods update has now broken my Jekyll install, and I cannot publish the blog post I just finished writing. WTF!?
ALL I WANTED TO DO WAS GET THE LATEST FREAKIN’ VERSION OF TWO FILES, A .h AND .m, AND NOW I HAVE TO WASTE TIME TRYING TO FIX WHAT WAS NOT BROKEN UNTIL YESTERDAY JUST SO I CAN PUBLISH A BLOG POST.
This is why I don’t like using things like CocoaPods, plug-ins, and other simular widgets.
Posted in rant. Tagged in cocoapods, gems, ios, ruby.
Related Articles
- Advice for new iOS freelancers
- How I post to my Jekyll site using my iPhone
- The Experienced Programmer's Guide to Getting Started with Swift
- From Trace To Slopes
- How To Do A Case Insensitive Search Using Parse SDK
- How To Present An Alert View Using UIAlertController When You Don't Have A View Controller
- My Upcoming Share Extension Talk At 360idev-Min
- Wish I Could Help But It's Not My App
- Maintain Your iOS App With Peak App Care
- Boston Area Mac And iOS Dev Community Is Awesome