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
Would like instructions on how to implement onSaveInstanceState #16799
changed the title [-]Would like instructions on how to handle landscape transitions with Flutter[/-][+]Would like instructions on how to implement onSaveInstanceState[/+]on May 31, 2018
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
eseidelGoogle commentedon Apr 20, 2018
I'm aware of at least one bug reported with Flutter's rotation code: #16322 there may be others.
championswimmer commentedon Apr 20, 2018
There needs to be documentation regarding how
onSaveInstanceStateis to be implented in Flutter as well.championswimmer commentedon Apr 20, 2018
Also pertinent : #6827
And dupe: #3427
Sfshaza commentedon May 18, 2018
Yes, added to doc content plan.
Sfshaza commentedon May 31, 2018
OK, PR flutter/website#1037 handles documenting how to configure landscape view, and also that android should not restart a Flutter app.
The onSaveInstanceState doc is not yet written.
[-]Would like instructions on how to handle landscape transitions with Flutter[/-][+]Would like instructions on how to implement onSaveInstanceState[/+]mzgreen commentedon Jun 27, 2018
Please note that
onSaveInstanceStateis not only about persisting state during config changes. More important part is that it's used it to persist transient app state when OS kills the app.https://developer.android.com/topic/libraries/architecture/saving-states#system_initiated_ui_state_dismissal
zoechi commentedon Dec 11, 2018
Issue moved to flutter/website #2004 via ZenHub
github-actions commentedon Sep 1, 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.