You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
SwiftPM will be the default for all Flutter apps in the next stable release (3.44). To ensure your plugin remains compatible and prevents build failures for your users, please migrate to SwiftPM
Flutter will eventually deprecate and then remove support for CocoaPods. Adding Swift Package Manager support future-proofs your plugins.
How to add Swift Package Manager support to your plugins
If you run into issues or have questions, please reach out to the Flutter team. You can send a message to the #hackers-ios channel on Flutter's discord or open a GitHub issue.
Thank you for your wonderful contributions to the Flutter ecosystem!
Why is Flutter migrating to Swift Package Manager?
Swift Package Manager support is one of Flutter's most requested features: flutter#33850.
Flutter's Swift Package Manager integration has several benefits:
Access to the Swift package ecosystem. Flutter plugins can use the growing ecosystem of Swift packages.
Simplifies Flutter installation. Swift Package Manager is bundled with Xcode. In the future, you won't need to install Ruby and CocoaPods to target iOS or macOS.
Reacted by Yaroslav Lihachev, Nicola, Nimr 🇵🇸, Alty, Maen Khdour and Antonio Martin
Removes the Objective-C registration shim (SwiftPM can't mix Swift and Objective-C in one target). The Swift class is now AppleMapsFlutterPlugin, so pluginClass doesn't change.
Leaves the Dart API, channel names and map behaviour unchanged.
Tested on Flutter 3.50 / Xcode 27.2: the example builds with both SwiftPM and CocoaPods, flutter test passes, and the integration
tests pass on the simulator.
It requires Flutter 3.5+ (needed for the FlutterFramework package). I've also seen #80; happy to help merge the two approaches
if that's easier for the maintainers.
Activity
Faiz-rhm commentedon Jul 1, 2026
any update??
Likhachev17 commentedon Jul 6, 2026
voting for it too +1
felipeparente commentedon Aug 13, 2026
any update??
lucas-goldner commentedon Aug 17, 2026
We need this please 👍🏽
ZoftPranav commentedon Aug 20, 2026
Please consider this at the earliest
andrehungaro commentedon Aug 31, 2026
Any update?
laltyshai commentedon Oct 16, 2026
any updatee?
nimr77 commentedon Oct 20, 2026
I made this PR for this issue
master...nimr77:apple_maps_flutter:master
m3n99 commentedon Nov 12, 2026
I've opened #93, which adds Swift Package Manager support for iOS while keeping CocoaPods working.
What it does:
ios/apple_maps_flutter/Sources/apple_maps_flutterand addsPackage.swift(iOS 13,FlutterFrameworkdependency), following the Flutter plugin author guide:
https://docs.flutter.dev/packages-and-plugins/swift-package-manager/for-plugin-authors
AppleMapsFlutterPlugin, sopluginClassdoesn't change.Tested on Flutter 3.50 / Xcode 27.2: the example builds with both SwiftPM and CocoaPods,
flutter testpasses, and the integrationtests pass on the simulator.
It requires Flutter 3.5+ (needed for the
FlutterFrameworkpackage). I've also seen #80; happy to help merge the two approachesif that's easier for the maintainers.
Until it's merged, you can use the fork: