Open jmagman opened 5 months ago
Are there time constraints here? That is, could we do it today, or should we wait until it's been out N months or there have been M newer releases?
should we wait until it's been out N months or there have been M newer releases?
There's no real value in waiting longer than April 29th, which is the point at which the app store will require Xcode 15 builds. At that point, nobody actually shipping apps can stay on Xcode 14 anyway.
should we wait until it's been out N months or there have been M newer releases?
There's no real value in waiting longer than April 29th, which is the point at which the app store will require Xcode 15 builds. At that point, nobody actually shipping apps can stay on Xcode 14 anyway.
Cool, thanks.
@vashworth https://github.com/flutter/flutter/pull/146256 needs Xcode 15.0, right?
@vashworth #146256 needs Xcode 15.0, right?
It's not a blocker (I wrote in checks that disable Swift Package Manager if not Xcode 15+), but yes it does need Xcode 15.0 to use the Swift Package Manager integration
I bumped the "recommended" version to 15 in https://github.com/flutter/flutter/pull/146367, which emits a doctor warning but doesn't stop from building on lower versions. Let's cp that for the next stable so people can start upgrading now.
Flutter's Swift Package Manager feature requires Xcode 15. CocoaPods will be used on older versions of Xcode.
We should update the Flutter tool's Xcode requirement to ensure Swift Package Manager is usable.
Previous bump at https://github.com/flutter/flutter/pull/93094