How to Fix “CocoaPods Out of Date” in Flutter on macOS

[rugularox]

🏷️ Discussion Type

Question

Body

How to Fix “CocoaPods Out of Date” in Flutter on macOS Sequoia and Sonoma

[rugularox]

Run pod --version first — if it’s below 1.11.0, that’s your actual problem, not Flutter.
Update CocoaPods with sudo gem install cocoapods (or via Homebrew if you went that route originally).
If the update itself fails or hangs, it’s almost always a Ruby version conflict introduced by the macOS upgrade, not a CocoaPods bug. source

[AhmedNaoum97]

This error usually means Flutter cannot find the latest iOS dependencies. A simple solution is to update CocoaPods and then refresh your Flutter project's iOS dependencies. If the problem continues, remove the old iOS dependency files and let Flutter recreate them. This forces Flutter and CocoaPods to download the latest compatible versions.

[saad0077-ss]

You can fix the “CocoaPods Out of Date” error on macOS Sequoia or Sonoma by reinstalling CocoaPods with the correct Ruby version and resetting Flutter’s iOS dependencies. On these newer macOS versions, system updates often break the Ruby environment that CocoaPods depends on, so Flutter can’t detect or run it properly. The cleanest fix is to install a fresh Ruby using Homebrew, reinstall CocoaPods using that Ruby, and then refresh your Flutter iOS setup. In practice, this means running brew install ruby to get a stable Ruby path, then installing CocoaPods again with sudo gem install cocoapods, and finally cleaning your Flutter project and reinstalling iOS pods using flutter clean followed by cd ios && pod install. After this, flutter doctor will correctly detect CocoaPods, and your iOS builds will work normally without warnings.

Flutter uses CocoaPods to manage iOS dependencies.
On macOS Sequoia/Sonoma, you may see:

Code => Warning: CocoaPods out of date

This happens because:

1 = macOS updates break Ruby or CocoaPods paths

2 = CocoaPods was installed with an older Ruby version

3 = Flutter can’t find the correct pod command

4 = Xcode command‑line tools changed after an update

So the fix is not just “update CocoaPods” — you must fix the environment.