Deprecate build ios-framework --universal#69720
Deprecate build ios-framework --universal#69720fluttergithubbot merged 2 commits intoflutter:masterfrom
Conversation
jmagman
added
platform-ios
flutter-dashboard
bot
added
c: contributor-productivity
| ..addFlag('universal', | ||
| help: 'Produce universal frameworks that include all valid architectures. ' | ||
| 'This is true by default.', | ||
| defaultsTo: true, |
There was a problem hiding this comment.
This should have a https://flutter.dev/docs/release/breaking-changes page if we're changing the default perhaps? Is there any user actions possibly needed for the integrator?
There was a problem hiding this comment.
We don't usually do that for tool changes, though the integrator would need to pass in --universal --no-xcframework now to get the old default behavior.
@zanderso what do you think?
There was a problem hiding this comment.
As long as the guidance from the tool itself is clear about what is going on, then that is usually sufficient.
| help: 'Produce a Flutter.podspec instead of an engine Flutter.xcframework (recommended if host app uses CocoaPods).', | ||
| ) | ||
| ..addOption('output', | ||
| abbr: 'o', |
There was a problem hiding this comment.
it seems like we never built in flag options to let users choose the target-platforms (like Android). Do you think we should?
There was a problem hiding this comment.
It's flutter build ios-framework it doesn't support other platforms.
|
Samples updated at flutter/samples#582 |
5 participants
Description
Universal (fat) frameworks that support physical devices and simulators aren't possible in an ARM simulator world since the arm64
iphoneosandiphonesimulatorslices can't belipod together. Deprecate and hide--universaland make--xcframeworkthe default.--universalwill need to be hard deprecated (removed) when the ARM simulator Flutter.framework ships.Related Issues
Fixes #69718
Tests
Updated
build_ios_framework_module_test.