Flutter is making a significant shift in its iOS and macOS dependency management. Starting with Flutter 3.44, Swift Package Manager (SwiftPM) becomes the default tool, replacing CocoaPods. This change simplifies setup, removes the need for Ruby dependencies, and aligns with Apple's supported ecosystem. CocoaPods will enter maintenance mode, becoming read-only on December 2, 2026. To help you navigate this transition, we've answered the most pressing questions below.
What major change is coming to Flutter's iOS and macOS dependency management?
Starting with Flutter's next stable release (version 3.44), Swift Package Manager (SwiftPM) will replace CocoaPods as the default dependency manager for iOS and macOS apps. This means you no longer need to install Ruby or manage CocoaPods configurations just to run your Flutter app. The Flutter CLI automatically migrates your Xcode project when you build or run your app. While CocoaPods will still work temporarily for unsupported plugins, the transition ensures access to Apple's modern package ecosystem. The change applies to both app developers and plugin maintainers, with the goal of unifying dependency management across all platforms.
Why is Flutter switching from CocoaPods to Swift Package Manager?
The primary reason is that CocoaPods is officially in maintenance mode and its registry will become read-only on December 2, 2026. After that date, no new versions or pods will be added. Relying on a deprecated tool would leave Flutter developers without future updates and compatibility with Apple's evolving ecosystem. Swift Package Manager, on the other hand, is Apple's supported solution, integrated directly into Xcode. It offers better performance, tighter integration, and simplified project configuration. By migrating now, Flutter ensures that apps continue receiving dependency updates and can leverage Swift packages. The transition also reduces friction for new developers, who no longer need to troubleshoot Ruby installations or CocoaPods version mismatches.
When will CocoaPods become read-only and fully deprecated?
CocoaPods' registry will permanently become read-only on December 2, 2026. Existing builds will still work after this date, but no new pods or versions will be added to the trunk. Flutter will continue to support CocoaPods as a fallback for plugins that haven't migrated, but that fallback will eventually be removed entirely. The exact removal date for the fallback hasn't been announced, but plugin developers are encouraged to migrate as soon as possible. App developers can temporarily opt out of SwiftPM if needed (see question below), but should plan to fully transition before CocoaPods support is dropped.
How will this transition affect regular app developers?
For app developers, the Flutter CLI handles most of the work automatically. When you run or build your iOS or macOS app with Flutter 3.44+, the CLI updates your Xcode project to use Swift Package Manager. If your app depends on plugins that haven't adopted SwiftPM yet, Flutter will print a warning listing those unsupported dependencies and temporarily fall back to CocoaPods for them. Eventually, CocoaPods support will be removed entirely, so if a critical plugin hasn't migrated, you should file an issue with its maintainer or find an alternative package. The transition is designed to be smooth—your existing code and workflow remain largely unchanged, except that you no longer need to install CocoaPods manually. For detailed steps, check the Flutter migration docs for app developers.
What should plugin developers do to support Swift Package Manager?
Plugin maintainers must add SwiftPM support by including a Package.swift file and restructuring their source files to match the standard Swift package layout. If you already migrated during the 2025 pilot, you need one additional step: add FlutterFramework as a dependency in your Package.swift file. Currently, only 61% of the top 100 iOS plugins have migrated. To encourage adoption, packages without SwiftPM support now receive lower pub.dev scores. Without migration, app developers will eventually be unable to use your plugin. The Flutter team provides migration documentation to guide you through the process. If you haven't started, now is the time—before CocoaPods disappears entirely.
What happens if some plugins haven't migrated yet?
If your app relies on plugins that haven't adopted Swift Package Manager, Flutter will print a warning during build, listing exactly which dependencies are unsupported. For these plugins, Flutter temporarily falls back to CocoaPods, so your build still succeeds for now. However, this fallback is not permanent—CocoaPods support will be removed entirely in a future Flutter release. If an unsupported plugin breaks your build, you should file an issue with the plugin's maintainer requesting Swift package support, or search for an alternative package. The warning is designed to give you time to push for migration. In the meantime, you can also temporarily disable SwiftPM if you encounter major issues.
How can developers temporarily disable SwiftPM if they encounter issues?
If Swift Package Manager causes a breaking issue in your project, you can opt out temporarily. Open your pubspec.yaml file, navigate to the flutter section, and under the config block, set enable-swift-package-manager to false like this:
flutter:
config:
enable-swift-package-manager: falsePlease note this is a temporary workaround. If you disable it, you must file a bug report using the Flutter GitHub issue template and include error details, a list of your plugins and versions, and copies of your Xcode project files. This feedback helps the Flutter team resolve issues before CocoaPods support is fully removed. Opting out should only be used as a last resort—ideally, work with plugin maintainers to migrate so your projects stay current.