For developers · Checked 1 October 2026

CocoaPods goes read-only: what changes and when

Short answer: CocoaPods is in maintenance mode, and its central Specs repo, trunk, is due to stop accepting new pods and new versions on December 2, 2026, after a test run on November 1–7, 2026. Existing pods stay installable and existing builds keep working; what ends is updates published through trunk. Firebase already made 12.19 its last scheduled CocoaPods release, and Firebase 13 ships only through Swift Package Manager and binary downloads. If you want new versions of your dependencies, plan a move to Swift Package Manager.

Key dates

From the CocoaPods blog and Firebase documentation, read 1 October 2026. CocoaPods says its dates are not set in stone.

WhenWhat happens
May 2025New pods using prepare_command are no longer accepted
September 9, 2026Firebase 12.19.0, its final scheduled release on CocoaPods
October 2026Firebase stops publishing new versions to CocoaPods
November 1–7, 2026CocoaPods test run of read-only trunk
December 2, 2026Trunk stops accepting new Podspecs permanently

What still works after December 2

The CocoaPods team plans to reject every new Podspec at the server and archive the CocoaPods/Specs repo on GitHub. The Specs repo and its CDN keep serving existing pods, so pod install on a project that already resolves will keep working, and your shipped builds are unaffected. What stops is new pods and new versions through trunk, which means no more security fixes or SDK updates for dependencies that only ship there. Private spec repos, and dependencies you vendor yourself or pull from npm, aren’t affected. The team says the date could move later within reason, but not earlier.

Firebase, Flutter and React Native

Firebase: 12.19.0 was the final planned 12.x minor and the final scheduled CocoaPods release; 13.0 and later come only through Swift Package Manager and the binary zip. Existing Firebase pods keep working. This also affects FlutterFire and the Firebase Unity and C++ SDKs. Flutter: the 3.47 release calls CocoaPods maintenance mode and says plugins that don’t move to Swift Package Manager will eventually stop working; 92 of the top 100 iOS plugins have moved, and flutter config --enable-swift-package-manager turns SwiftPM back on if you disabled it, see Flutter 3.47. React Native: CocoaPods is still the default; 0.87 added experimental SwiftPM support that the team says isn’t ready for production, see React Native 0.87. CocoaPods notes that most React Native libraries come from npm rather than trunk.

Moving a native app to Swift Package Manager

Firebase’s migration guide gives the general path. First check that every dependency supports Swift Package Manager; if some don’t, Firebase suggests its manual XCFramework install rather than mixing CocoaPods and SwiftPM in one target, which can cause dependency cycles and build errors. Then, with Xcode closed, run pod deintegrate and delete the generated .xcworkspace. Open the .xcodeproj, add each package with File > Add Package Dependencies, and pick libraries for your target under Frameworks, Libraries, and Embedded Content. Projects that rely on CocoaPods install scripts or custom configurations need extra work. With the 27 SDKs required from April 2027, see Xcode 27 requirements for the other changes to plan alongside.

Where Censuus fits

Keeping dependencies current keeps your app shipping; being found brings people to it. Censuus ranks apps by the visits they draw, and adding your app is free through the List my app form. Placement comes from traffic and sponsorship: apps climb on the visits they draw, and a sponsor can pay to rise higher.

Frequently asked questions

Is CocoaPods deprecated?

Its maintainers describe it as in maintenance mode, and its central trunk is due to go read-only on December 2, 2026. Existing pods keep working, but no new pods or versions will be added.

When does CocoaPods become read-only?

December 2, 2026, after a test run on November 1–7, 2026. The CocoaPods team says the dates aren’t set in stone.

Will my app stop building when CocoaPods goes read-only?

No. The Specs repo and CDN keep serving existing pods, so existing builds keep working. You just won’t get new versions through trunk.

Is Firebase still available on CocoaPods?

Existing versions are. Firebase 12.19.0 was its final scheduled CocoaPods release, and Firebase 13 and later ship only through Swift Package Manager and binary distributions.

Does this affect Flutter apps?

Indirectly. Plugins that depend on pods from trunk, such as FlutterFire with Firebase, stop getting new versions there, and Flutter says plugins that don’t migrate to Swift Package Manager will eventually stop working. 92 of the top 100 iOS plugins have migrated.

Guides for app developers

Put your app in the ranking

Censuus ranks apps by the visits they draw and by sponsorship, no bots. Listing is free; sponsorship raises placement.