Even if they fix in 3.10.1, you will probably never be able to allow 3.10.

I'd expect that once they publish 3.10.1 cocoapod will never resolve to the older 3.10.0?

🤷‍♀️ Depends on if other dependencies use GoogleMaps and their defined ranges. Ideally we should be explicit.

A list of version requirements can be specified for even more fine grained control.

https://guides.cocoapods.org/syntax/podfile.html#pod

I guess it can be something like: '< 3.10', '> 3.10' to "remove" the pin? (while excluding 3.10)

So, at the time GoogleMaps iOS SDK is in version 4.2.0 and the flutter_package still use the 3.9.0 SDK for iOS, also they announce drop ios 10 support for version 5.0, can the google maps flutter package use the latest iOS SDK?

https://developers.google.com/maps/documentation/ios-sdk/releases

Flutter 2 still has a minimum of Xcode 11.0, but recommends 12.0.1. In any case, the infra story is past Xcode 12 now.
Maybe the best thing is to totally unpin it, and then users can set pod 'GoogleMaps', '< 3.10' or whatever versions in their own Podfile depending on what Xcode they have installed, their minimum target iOS version, etc...
What do you think, @ditman?

@jmagman yep, I think it's worth a try. I created this issue while gardening and iOS is not my jam, but this looks safe.

After some time, the 3.10 dependency on a more modern XCode was documented, btw!

Note:

To build apps using the Maps SDK for iOS, the current minimum IDE version supported is Xcode 11.5.

If we're past that, we should be fine, I guess?

If we're past that, we should be fine, I guess?

Our infra is past that, but the minimum required on Flutter 2 isn't. I think unpinning is probably the best idea since individual users can have control over what GoogleMaps version they use. But if the plugin doesn't unpin, they can't upgrade past 3.9 even if the have the right SDK version installed.

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.