CocoaPods end of life: here's what to do

CocoaPods, a widely-used dependency manager for iOS projects, will enter a read-only state on December 2, 2026, ceasing the acceptance of new pod versions and podspecs, though existing pods will remain accessible. This shift affects a range of iOS applications, including those built with native Swift, Objective-C, React Native, and Flutter, compelling developers to transition their dependencies primarily to Swift Package Manager (SPM) or consider manual XCFramework installation for unsupported libraries. The transition is driven by the goal of reducing security risks and maintenance burdens associated with a writable public registry. While the read-only status of CocoaPods will not prevent existing applications from building, it will curtail future updates through the platform, prompting developers to adapt their build systems accordingly. To minimize disruptions, particularly for critical services like push notifications, developers are advised to inventory their Podfiles, assess dependencies for SPM compatibility, and strategically plan their migration to maintain functionality and security.