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
A significant part of the argument for switching the default iOS template to Swift was that with Swift 5, newer iOS devices wouldn't have the size overhead of having all the Swift libraries bundled in an app.
However, our Swift template is currently using Swift version 4, which means that's actually not the case unless developers go in and manually change their project settings. Lots of people are going to have unnecessarily large new apps under the current settings.
We should make the language default for the app and plugin templates 5, not 4. This will require:
Actually changing the value in the Xcode project templates
Updating the Swift code in the templates to use Swift 5
Making Xcode 10.3 the minimum supported version in flutter_tool (currently its 9)
In all templates upping SWIFT_VERSION to 5.0 (at least in a fresh app create and plugin create I don't see any errors or warnings after doing that, which is good!)
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
[-]Swift template is using Swift 4.[/-][+]Swift template is using Swift 4[/+]stuartmorgan-g commentedon Sep 12, 2019
Since we shipped Swift-by-default to stable, should we consider a hotfix for this?
jmagman commentedon Sep 13, 2019
Off the top of my head, this would involve:
stuartmorgan-g commentedon Sep 13, 2019
I thought we didn't use Swift in first-party plugins yet, because it would have caused the size bloat for everyone using them.
jmagman commentedon Sep 13, 2019
You're right. Maybe check the top 50 plugins? I doubt there are more than a handful if any. #25676
github-actions commentedon Aug 27, 2021
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.