stuartmorgan-g

> A PR for iOS has not been created yet due to an issue with the `GMSPinImage` not rendering on the map. Does @caio1985 have an update on whether this...

Capturing some information and discussion from comments in issues and Discord: - According to comments in https://github.com/flutter/packages/pull/8288, SPM support for `google_maps_ios` requires dropping support for iOS 14, which Flutter still...

The comment above assumes that we do in fact need to drop iOS 14 for `google_maps_flutter` SPM support. @jokerttu, @wangela, could you elaborate as to why that is necessary? I...

That message is far better than the situation we had with CocoaPods, so while a wrapper message with instructions would be nice, I don't think we need to block on...

> I don't think a broad dependency range of `[8.4.0, 10.0.0)` would allow us to lower the iOS requirement. SPM strictly enforces that a package's platform requirements are equal to...

> I know it's moot in this particular instance, but that CocoaPods behavior is something we've benefitted from in `google_maps_flutter` for quite a while. https://github.com/flutter/flutter/issues/169376 is a design document to...

Yes, we're aware of that timeline; we were already planning to have a solution here in advance of 2026Q2, so it shouldn't affect anything.

> * Using less storage (as no Visual Studio is needed) Not telling people to install Visual Studio would require replacement workflows for everything, not just that page. Notably [this](https://docs.flutter.dev/platform-integration/platform-channels#step-5-add-a-windows-platform-specific-implementation)...

Not necessarily; as I said above: > If we can provide a good end-to-end story with VS Code, however, that's definitely something that seems worth considering. I don't know if...

@JaffaKetchup Denigrating other developers' work is not a great way to make your point.