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
As far as I can tell we are blocked on adding any Swift code to google_maps_flutter_ios, as doing so triggers the same category of problem that led to this complicated SwiftPM support design doc, as captured in this appendix.
I just re-tested this from scratch with the current version of google_maps_flutter_ios to make sure this wasn't operator error or a quirk of that version of Xcode. Testing now with Xcode 26.2, if I take the example app for google_maps_flutter_ios and:
add a single trivial Swift file
add .swift to the podspec pattern for sources
change the example Podfile and Xcode project to set iOS 15, rather than 14, as the deployment version
then building fails with:
Swift Compiler Error (Xcode): Compiling for iOS 14.0, but module 'GoogleMapsUtils' has a minimum deployment target of iOS 15.0
If I change google_maps_flutter_ios.podspec to s.platform = :ios, '15.0', then do a flutter clean/flutter build, that problem goes away, so clearly the 14.0 in that error is coming from the plugin podspec.
So it appears that just as SwiftPM proved incompatible with the dynamic GoogleMaps version resolution used by google_maps_flutter_ios, any use of Swift is incompatible with that as well.
This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of flutter doctor -v and a minimal reproduction of the issue.
Activity
[-][google_maps] iOS Swift migration[/-][+][google_maps_flutter] iOS Swift migration[/+][google_maps_flutter] Remove use of OCMock (#10863)
stuartmorgan-g commentedon May 8, 2026
Moving discussion here and expanding on what I learned in last year's PR:
As far as I can tell we are blocked on adding any Swift code to
google_maps_flutter_ios, as doing so triggers the same category of problem that led to this complicated SwiftPM support design doc, as captured in this appendix.I just re-tested this from scratch with the current version of
google_maps_flutter_iosto make sure this wasn't operator error or a quirk of that version of Xcode. Testing now with Xcode 26.2, if I take the example app forgoogle_maps_flutter_iosand:.swiftto the podspec pattern for sourcesthen building fails with:
If I change google_maps_flutter_ios.podspec to
s.platform = :ios, '15.0', then do aflutter clean/flutter build, that problem goes away, so clearly the14.0in that error is coming from the plugin podspec.So it appears that just as SwiftPM proved incompatible with the dynamic GoogleMaps version resolution used by
google_maps_flutter_ios, any use of Swift is incompatible with that as well.24 remaining items
[google_maps_flutter] Convert top-level classes to Swift in `_sdk*` p…
[google_maps_flutter] Convert heatmap controller to Swift (#12713)
[google_maps_flutter] Convert simple object controllers to Swift (flu…
[google_maps_flutter] Convert overlay controllers to Swift (flutter#1…
[google_maps_flutter] Convert marker controllers to Swift (flutter#12662
[google_maps_flutter] Convert heatmap controller to Swift (flutter#12713
[google_maps_flutter] Convert simple object controllers to Swift (flu…
[google_maps_flutter] Convert overlay controllers to Swift (flutter#1…
[google_maps_flutter] Convert marker controllers to Swift (flutter#12662
[google_maps_flutter] Convert heatmap controller to Swift (flutter#12713
[google_maps_flutter] Convert remaining code to Swift (flutter#12768)
[google_maps_flutter] Indicate that default iOS impl is discoraged (#…
github-actions commentedon Sep 26, 2026
This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of
flutter doctor -vand a minimal reproduction of the issue.