DEV Community

Israr Kundi
Israr Kundi

Posted on Originally published at israr-kundi.web.app

CocoaPods read-only 2 December: check your Flutter app

CocoaPods read-only 2 December: check your Flutter app

CocoaPods read-only 2 December is the date to know if your Flutter app runs on iOS. From that day, no new pod or pod version can be published to the CocoaPods trunk registry. Your app will still build on 3 December, and nothing already published disappears. What stops is new updates — including security fixes — for any plugin that only ships through CocoaPods.

Many Flutter apps still use CocoaPods under the hood, even though Swift Package Manager has been the default since Flutter 3.44. If you have never thought about CocoaPods, this is the one to read.

CocoaPods read-only 2 December: what changes, and what does not

CocoaPods trunk is the public registry behind pod install. On 2 December 2026 it becomes permanently read-only. The CocoaPods team ran a test of the same lock from 2 to 6 November, so publishing tools already saw it coming. The team also says the date can slip later, never earlier.

What keeps working: every pod already published stays installable from the specs repo and the CDN. Your current build still works.

What stops: new pods, and new versions of existing pods. If Apple ships an iOS change that breaks a plugin, the maintainer cannot publish a patch to CocoaPods. If a security hole is found in a plugin, the fix cannot reach you through CocoaPods either.

So the risk is not a crash on 3 December. The risk is a slow freeze: your app keeps working while the fixes it needs stop arriving.

Firebase already left — and that is the proof

Firebase Apple SDK 13.0.0, released 7 October 2026, is not on CocoaPods at all. Version 12.19.0 was the last scheduled CocoaPods release. On 22 October, Firebase shipped 12.19.3, a Firestore security fix, and only the Firestore-related pods got that version on CocoaPods.

FlutterFire followed with firebase_core 5.0.0 on 15 October 2026 — but that release pins both ways. Under Swift Package Manager it resolves Firebase 13; under CocoaPods it stays on 12.19.0. Upgrading FlutterFire does not by itself move your app to Swift Package Manager.

If your app uses Firebase and still runs on CocoaPods, you are on Firebase 12, and you will stay on Firebase 12.

The audit: 10 minutes that tells you where you stand

Flutter has handled the switch itself since 3.44: upgrade Flutter, run the app once, and the tool adds Swift Package Manager support on its own. The migration is not the hard part. Finding the one plugin with no Swift Package Manager support is.

  1. Upgrade Flutter to 3.44 or newer and run the app once:
flutter upgrade
flutter run
Enter fullscreen mode Exit fullscreen mode

If Swift Package Manager was switched off before, turn it back on first with flutter config --enable-swift-package-manager. Flutter prints a warning naming the plugins that have not adopted Swift Package Manager yet — read that list, because it is your audit.

  1. Open ios/Podfile.lock. Any plugin still named there has no Swift Package Manager support yet — that list is your real work. One CocoaPods-only plugin anywhere in the tree keeps the whole fallback alive.

  2. Check each plugin on that list for a newer version with a Package.swift file. Upgrade the ones that have it. ML Kit shows how fast this moves: google_mlkit_commons 1.0.0 moved its iOS plugin to Swift Package Manager, and 1.0.1 on 6 November fixed installing it from pub.dev. Note the ML Kit route runs through a community repackaging of Google's SDK and needs manual Xcode steps, so budget time for it.

  3. For a plugin with no Swift Package Manager version, look for a maintained replacement that has one. If it is core to your app and has no replacement, budget the move yourself or ask the maintainer — after 2 December, its CocoaPods releases stop reaching you.

  4. Once nothing needs CocoaPods, remove it cleanly: run pod deintegrate, then delete ios/Podfile, ios/Podfile.lock, the ios/Pods folder, and ios/.symlinks. Also remove any leftover lines referencing Pods in ios/Flutter/Debug.xcconfig and ios/Flutter/Release.xcconfig, or the build can break. Build again and test sign-in and push notifications.

A mixed setup — some plugins on Swift Package Manager, some still on CocoaPods — is normal right now. Start with the audit; do not wait for a fully clean list.

When to get help instead of doing it yourself

Do the audit yourself — it is reading a file and a warning list, not changing code. Get help if the audit turns up a plugin with no Swift Package Manager support and no replacement, and that plugin runs something your app cannot lose, like payments or sign-in. Get help too if your app still has the switch turned off in pubspec.yaml (enable-swift-package-manager: false) and you are not sure why. Flutter's docs say switching it off will not be allowed in future.

What not to do

Do not delete the Podfile before the audit — that just breaks the build and tells you nothing. Do not assume upgrading FlutterFire moved you to Swift Package Manager; check the Podfile.lock. And do not leave this to the last week of November: the audit is short, but a plugin with no replacement takes real time.

If this is your app, contact me through https://israr-kundi.web.app

Top comments (0)