-
Notifications
You must be signed in to change notification settings - Fork 9.8k
[google_maps_flutter] Pin GoogleMaps cocoapod dep to last good known version #2924
Conversation
This is what I saw locally! Why is it ever resolving to 3.10... |
This comment has been minimized.
This comment has been minimized.
Turns out the The minimum version of ios for new flutter apps was bumped from 8.0 to 9.0 recently. The plugin specifies a minimum version of ios to run (8.0). Resolving that in an 8.0 app (old), will yield GoogleMaps 2.7 (as seen above), however new apps that use 9.0 can resolve 3.x versions. 3.9 was good, as seen in the full-green pass linked in the comment above. 3.10 is bad, probably because it exposes new APIs that require a newer version of XCode. The change is undocumented as of now:
|
Cleanup ticket created: flutter/flutter#63530 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
packages/google_maps_flutter/google_maps_flutter/ios/google_maps_flutter.podspec
Outdated
Show resolved
Hide resolved
Pub handles that for us
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Merged on red; this should make the tree green again. |
The tree is squeaky green now |
Description
GoogleMaps 3.10 seems to have increased the minimum requirement for XCode beyond what our test infra can handle (undocumented?).
This change pins the GoogleMaps podspec to <3.10 until the situation clears, to unblock the build trees of both flutter/plugins and flutter/flutter.
Why are our apps resolving to 3.10, when our Podspec states that ios 8.0 needs to be supported?
Apps were resolving to 3.10 because
flutter create
now creates apps that have a minimum iOS version of 9.0 (instead of 8.0).Why did 3.10 break us?
3.10 breaks us because they're using some APIs only available in XCode 11.4 and our infra is in 11.3.1. (However, as @jmagman pointed out, they should check for the availability of these APIs or a runtime error will happen in devices running iOS < 13.4.)
Related Issues
Checklist
Before you create this PR confirm that it meets all requirements listed below by checking the relevant checkboxes (
[x]
). This will ensure a smooth and quick review process.///
).flutter analyze
) does not report any problems on my PR.Breaking Change
Does your PR require plugin users to manually update their apps to accommodate your change?