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
{{ message }}
Repository navigation
Commit df71942
Browse filesBrowse the repository at this point in the historyBrowse files
To use this, your root widget must support unbounded constraints. Avoid using widgets that require bounded constraints (like `ListView` or `LayoutBuilder`) at the top of your tree, as they can conflict with the dynamic sizing logic.
795
+
796
+
In practice, this means that quite a few common widgets are not supported,
797
+
such as `ScaffoldBuilder`, `CupertinoTimerPicker`,
798
+
or any widget that internally relies on a `LayoutBuilder`.
799
+
When in doubt, you can use an `UnconstrainedBox` to test the usability of
800
+
a widget for a content-sized view, as in the following example:
The value of `appFlavor` matches the name of the Xcode scheme you defined (for example, `staging` or `production`). If no flavor is specified during the build, `appFlavor` returns `null`.
270
+
:::
271
+
242
272
### Use the run command (Xcode)
243
273
244
274
You can launch a specific scheme in Xcode using the
0 commit comments