Flutter Embraces Swift Package Manager: Navigating the Post-CocoaPods Era

Flutter's upcoming stable release, version 3.44, marks a pivotal change for iOS and macOS development: Swift Package Manager (SwiftPM) will become the default dependency manager, replacing CocoaPods. This shift streamlines the setup process, eliminating the need for Ruby installations or CocoaPods configurations. Here's what this transition means for app developers and plugin maintainers.

The Shift to Swift Package Manager

CocoaPods has long been a staple for managing dependencies in Apple ecosystems, but its maintenance mode status signals a clear end. According to the announcement, CocoaPods' trunk will become read-only on December 2, 2026, meaning no new pods or versions will be added after that date. While existing builds remain functional, the community is urged to migrate to Apple's official solution—Swift Package Manager. Flutter's adoption ensures continued access to dependency updates and integration with the broader Swift package ecosystem.

Flutter Embraces Swift Package Manager: Navigating the Post-CocoaPods Era

What App Developers Need to Know

Automated Migration

The Flutter CLI handles the heavy lifting. When you next run or build an iOS or macOS app, the tooling automatically updates your Xcode project to use SwiftPM. No manual steps are required—just ensure your Flutter version is 3.44 or later. For detailed guidance, refer to the Flutter migration docs for app developers (scroll down).

Handling Unsupported Plugins

If your app depends on plugins that haven't yet adopted SwiftPM, Flutter will display a warning listing the unsupported dependencies. In the meantime, the framework temporarily falls back to CocoaPods for those plugins. However, CocoaPods support will eventually be removed entirely. If a migration issue arises, you should contact the plugin's maintainers to request SwiftPM support or seek an alternative package. Plugin developers: see the section below for migration requirements.

Opting Out Temporarily

Migrations can encounter hiccups. If SwiftPM causes a breaking problem in your project, you can temporarily disable it:

Open your pubspec.yaml file.
Locate the flutter section.
Under the config block, set enable-swift-package-manager to false.

flutter:
  config:
    enable-swift-package-manager: false

After opting out, please file a bug report on the Flutter GitHub issue tracker with error details, a list of plugins and versions, and copies of your Xcode project files. This feedback helps resolve issues before CocoaPods is fully deprecated.

What Plugin Developers Must Do

Migration Requirements

If you maintain an iOS or macOS plugin, adding SwiftPM support is now essential. Currently, 61% of the top 100 iOS plugins have already migrated. To catch up, you need to:

Add a Package.swift file to your plugin's repository.
Restructure your source files to match the standard Swift package layout.
If you migrated earlier during the 2025 pilot, a new step is required: add FlutterFramework as a dependency in your Package.swift file. Refer to the official Flutter migration documentation for complete instructions.

pub.dev Score Penalty

To encourage adoption, packages without SwiftPM support now receive lower pub.dev scores until they complete the migration. This scoring penalty serves as a nudge—keeping your package’s score high requires updating to Swift Package Manager.

Preparing for the Future

The end of CocoaPods is not immediate, but the timeline is clear: after December 2, 2026, the registry will be read-only. App developers should verify that their plugins have migrated, while plugin maintainers should prioritize adding SwiftPM support. Flutter's fallback mechanism offers a grace period, but reliance on CocoaPods will become riskier over time. By embracing Swift Package Manager now, you ensure smoother builds, access to the latest packages, and full compatibility with future Flutter releases.

For more details, consult the Flutter migration docs for app developers and the plugin developer section above.

Flutter Migration Documentation

Note: This anchor link is provided for reference; the official documentation can be found on the Flutter website.

Tags: