Flutter is making a significant change to its dependency management for iOS and macOS apps. Starting with the upcoming stable release (version 3.44), Swift Package Manager (SwiftPM) will replace CocoaPods as the default tool for managing dependencies. This move aligns with Apple’s supported ecosystem and simplifies the development workflow by eliminating the need for Ruby and CocoaPods installations.
Why the Change?
CocoaPods has been the go-to dependency manager for iOS and macOS for years, but it is now in maintenance mode. Its registry will become permanently read-only on December 2, 2026. After that date, no new versions or pods will be added to the trunk. While existing builds will continue to work, Flutter must transition to a solution that remains actively supported and provides access to the growing Swift package ecosystem. Swift Package Manager, integrated directly into Xcode and maintained by Apple, offers a more seamless, native experience.
What App Developers Need to Know
For most app developers, the migration is handled automatically by the Flutter CLI. When you run or build your iOS or macOS app, the CLI updates your Xcode project to use SwiftPM. If your app relies on plugins that haven’t yet adopted SwiftPM, Flutter will print a warning listing the unsupported dependencies. It will temporarily fall back to CocoaPods for those plugins, but this fallback is only a short-term solution. Eventually, CocoaPods support will be fully removed, so it’s crucial that plugin maintainers update their packages.
Opting Out Temporarily
If SwiftPM causes a breaking issue in your project, you can disable it temporarily. Open your pubspec.yaml file and add the following under the flutter section:
flutter:
config:
enable-swift-package-manager: falseThis will revert to CocoaPods for your project. However, this is only a stopgap measure. If you opt out, please help the Flutter team improve by filing a bug report.
Reporting Issues
If you encounter problems, use the Flutter GitHub issue template. Include error details, a list of your plugins with versions, and copies of your Xcode project files. This will help the team resolve issues before CocoaPods is completely phased out.
What Plugin Developers Must Do
Plugin authors who maintain iOS or macOS plugins need to add SwiftPM support if they haven’t already. Currently, 61% of the top 100 iOS plugins have migrated. To encourage the remaining 39%, packages without SwiftPM support will receive lower scores on pub.dev until they adopt the new system.
Steps to Migrate Your Plugin
- Add a
Package.swiftfile to your plugin’s root directory. - Move your source files to match the standard Swift package structure (typically under
Sources/). - Declare your package dependencies in the
Package.swiftfile.
If you already migrated your plugin during the 2025 pilot, you must complete one additional step: add FlutterFramework as a dependency in your Package.swift file. This ensures proper integration with the Flutter SDK.
Timeline and Future
Flutter 3.44 will mark the beginning of the default use of SwiftPM. CocoaPods will remain as a fallback for a limited time, but developers are strongly encouraged to migrate as soon as possible. The December 2026 read-only registry means that after that point, CocoaPods will no longer receive updates. The Flutter team plans to remove CocoaPods support entirely in a future release.
Conclusion
This transition is a positive step forward for Flutter’s iOS and macOS development, aligning with Apple’s ecosystem and reducing complexity. App developers will benefit from automatic migration, while plugin developers need to act to ensure their packages remain compatible. By working together, the Flutter community can make the switch smooth and ensure continued access to the best tools available.