Repository navigation
Define a pattern for runApp when the window may have no size #32871
Description
With add to app, we should propose a best practice for what to do with the widget tree if, by default, users are going to run the engine ahead of time. They would need to put some widget into runApp so something rebuilds eventually but some widget want actual window sizes too so it shouldn’t be the final widget tree.
Do we need a WhenWindowAttached widget? Or just read MediaQuery.of(context).size?
Activity
matthew-carroll commentedon Jun 6, 2019
This issue needs to also account for the fact that lifecycle events are sent across a platform channel and they have an impact on Flutter's running state. The platform developer would have to make a choice to send or not send those events, and that decision would impact what Flutter runs or doesn't run.
xster commentedon Jun 6, 2019
Agreed. Perhaps one exploration might be to consider adding new parallel or enum value lifecycle signals to distinguish app not in foreground vs app in foreground but Flutter isn't
chunhtai commentedon Sep 4, 2019
I wrote up a document to conclude our off line discussion https://docs.google.com/document/d/1FNuq5-3rEB1n1fChdEde6gzZG9QOiw7HtM2jb12Ecv4/
xster commentedon Oct 2, 2019
@chunhtai you had some PRs on this right? Can we attach some links?
chunhtai commentedon Oct 2, 2019
The life cycle pr is tracked in this #39832
blasten commentedon Oct 17, 2019
Hi @chunhtai. Are you still working on this issue?
chunhtai commentedon Oct 18, 2019
@blasten , I am still working on this one #39832
timsneath commentedon Jan 3, 2020
Touching this issue for triage purposes.
xster commentedon Jan 6, 2020
The last bit in the chain is flutter-team-archive/engine#14002
github-actions commentedon Aug 8, 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.