In a decisive move that accelerates Apple platform development, the Flutter team announced that starting with version 3.44, Swift Package Manager (SwiftPM) will replace CocoaPods as the default dependency manager for iOS and macOS projects. The change, effective immediately upon the stable release, eliminates the need for developers to manage Ruby-based CocoaPods installations.
"This transition marks the end of an era for Flutter on Apple platforms," said a Flutter engineering lead. "CocoaPods has been a reliable workhorse, but Swift Package Manager is Apple's modern, natively supported solution. It's time to move forward."
Background
CocoaPods, the Ruby gem that has been the de facto standard for managing iOS and macOS dependencies for over a decade, officially entered maintenance mode earlier this year. Its registry will become permanently read-only on December 2, 2026. While existing projects will continue to build, no new pod versions or packages will be added after that date.
The Flutter team has been piloting SwiftPM support since 2025, and feedback from early adopters has shaped the final migration path. With 61% of the top 100 iOS plugins already migrated, the project is confident that the ecosystem is ready for the switch.
What This Means
For app developers, the migration is largely transparent. The Flutter command-line interface will automatically update Xcode projects to use SwiftPM when you run or build your app. If a plugin has not yet adopted SwiftPM, Flutter will temporarily fall back to CocoaPods for that dependency, but will display a warning listing unsupported packages.
"Developers won't be left in the cold overnight," assured a Flutter product manager. "But we strongly encourage everyone to ensure their dependencies are updated. The fallback is a safety net, not a long-term solution."
How App Developers Should Handle the Change
To check for unsupported plugins, simply build your Flutter iOS or macOS app. The CLI output will clearly indicate which dependencies still rely on CocoaPods. If any are missing SwiftPM support, file an issue with the plugin maintainer or seek an alternative package.
If SwiftPM causes a breaking issue in your project, you can temporarily disable it by setting enable-swift-package-manager: false under the config block in your pubspec.yaml. However, this is intended only as a workaround. The Flutter team asks that developers who opt out file a bug report with full details, so the issue can be resolved before CocoaPods support is permanently removed.
Guidance for Plugin Developers
Plugin authors who maintain iOS or macOS packages must add SwiftPM support now to avoid losing visibility. Packages without SwiftPM support receive lower pub.dev scores, which directly impacts discoverability. To migrate, add a Package.swift file and restructure source files according to the standard Swift package layout.
For those who already participated in the 2025 pilot, there is an additional requirement: you must include FlutterFramework as a dependency in your Package.swift. The Flutter team provides detailed migration documentation to guide this process.
"We need the remaining plugin authors to step up," said a Flutter core contributor. "The ecosystem depends on it. 61% of the top plugins have already made the jump—we can't let the rest hold back app developers."
Deadline and Support
CocoaPods will remain functional until December 2026, but no new features or updates will be provided. Flutter's official migration docs offer step-by-step instructions for both app and plugin developers. The project's GitHub issue tracker is open for reporting problems.
"This is a necessary evolution," concluded the engineering lead. "By embracing Swift Package Manager, Flutter aligns with Apple's roadmap and ensures long-term maintainability for thousands of apps."