Starting with the upcoming stable release of Flutter 3.44, the Swift Package Manager (SwiftPM) becomes the default dependency manager for iOS and macOS apps, replacing CocoaPods. This transition eliminates the need for Ruby or CocoaPods installations. CocoaPods has entered maintenance mode, with its registry becoming read-only on December 2, 2026. While existing builds remain functional, no new updates or pods will be added after that date. To ensure ongoing dependency updates and access to the Swift package ecosystem, Flutter is moving to Apple's officially supported solution. Below are key questions and answers to help you navigate this change smoothly.
1. Why is Flutter moving from CocoaPods to Swift Package Manager?
Flutter is transitioning to Swift Package Manager because CocoaPods has officially entered maintenance mode. Apple's registry will become read-only on December 2, 2026, meaning no new versions or pods will be added after that date. While existing CocoaPods projects will still build, they will no longer receive dependency updates. Swift Package Manager is Apple's actively supported dependency management solution, offering tighter integration with Xcode, improved performance, and better alignment with the Swift ecosystem. By adopting SwiftPM as the default, Flutter ensures developers have access to ongoing updates and a more robust toolchain. This change also removes the requirement to install Ruby and CocoaPods, simplifying the setup process for many developers.
2. What does this change mean for app developers?
For app developers, the Flutter CLI now handles the migration automatically. When you run or build your iOS or macOS app, the CLI updates your Xcode project to use Swift Package Manager behind the scenes. You do not need to manually modify project files. However, if your app depends on plugins that have not yet adopted SwiftPM, Flutter will display a warning listing exactly which dependencies are unsupported. In such cases, Flutter temporarily falls back to CocoaPods for those plugins until they migrate. Since CocoaPods support will eventually be removed entirely, if a plugin breaks your build due to lack of SwiftPM support, you should file an issue with the plugin maintainer or look for an alternative. The migration process is designed to be seamless for most developers, but a safety net is provided.
3. How can I migrate my existing Flutter iOS/macOS project?
Migration is handled automatically by the Flutter CLI. Simply run or build your app as usual – the CLI will update your Xcode project to use Swift Package Manager. No manual steps are required for app developers. For detailed guidance, consult the Flutter migration docs for app developers. If you encounter issues, the CLI will print a warning listing unsupported plugins. You can then either wait for plugin updates or, as a temporary measure, opt out of SwiftPM (see question 5). The goal is a painless transition, but if something goes wrong, Flutter provides a fallback mechanism that relies on CocoaPods for unadopted plugins.
4. What should I do if a plugin I use hasn't adopted SwiftPM yet?
If you rely on plugins that haven't migrated to Swift Package Manager, Flutter will temporarily fall back to CocoaPods for those specific dependencies. However, this fallback will be removed once CocoaPods support ends. To avoid future build failures, you should check whether the plugin has a SwiftPM version. If not, file an issue with the plugin maintainer requesting Swift Package Manager support. Alternatively, look for another package that already supports SwiftPM. Flutter's CLI will warn you about unsupported plugins, so you can track which ones need updates. Eventually, all plugins must adopt SwiftPM to remain compatible. The Flutter team encourages app developers to prioritize using plugins that have already migrated.
5. Can I temporarily opt out of Swift Package Manager? How?
Yes, you can temporarily disable Swift Package Manager for your project if it causes a breaking issue. Open your pubspec.yaml file, navigate to the flutter section, and under the config block set enable-swift-package-manager to false. Here's an example:
flutter:
config:
enable-swift-package-manager: false
If you opt out, please file a bug report using the Flutter GitHub issue template. Include error details, a list of your plugins and versions, and copies of your Xcode project files. This helps the Flutter team resolve issues before CocoaPods support is completely removed. Remember, opting out is a temporary measure – you should eventually migrate to SwiftPM.
6. What are the new requirements for plugin developers?
Plugin developers must add Swift Package Manager support to their iOS or macOS plugins if they haven't already. This involves adding a Package.swift file and restructuring source files to match the standard Swift package layout. If you already migrated during the 2025 pilot, there's an additional step: you must include FlutterFramework as a dependency in your Package.swift. Currently, 61% of the top 100 iOS plugins have migrated. To encourage adoption, packages without SwiftPM support receive lower pub.dev scores. The migration documentation provides detailed instructions. Plugin developers are urged to complete the migration to avoid leaving app developers reliant on deprecated CocoaPods.
7. How will this transition affect CocoaPods in the long term?
CocoaPods is officially in maintenance mode and will not receive new features. Its registry will become read-only on December 2, 2026, meaning no new versions or pods can be added. Existing projects will still build, but they will not receive dependency updates. Once CocoaPods support is fully removed from Flutter (expected in a future release), any plugins relying solely on CocoaPods will break. This transition ensures that the Flutter ecosystem remains aligned with Apple's long-term direction. Developers are strongly encouraged to migrate to Swift Package Manager before the cutoff date to avoid disruptions.
8. What is the status of plugin migration so far?
As of the announcement, 61% of the top 100 iOS plugins have adopted Swift Package Manager. This is a significant milestone, but the remaining plugins need to migrate to ensure a smooth transition for app developers. Packages without SwiftPM support now receive lower pub.dev scores, incentivizing plugin authors to update. The Flutter team expects adoption to increase as the deadline for CocoaPods read-only status approaches. App developers should check their plugin dependencies and, if necessary, encourage maintainers to accelerate their migration. The community is encouraged to contribute to open-source plugins to help reach full adoption.