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
Back handling state is lost on activity recreation when using a cached engine #159158
This state is lost when the activity (or activity hosting the fragment) is destroyed and recreated. This is fine when the engine is also destroyed, but if a cached engine is being used then the Flutter routes are not destroyed, so the two get out of sync.
We can fix this by overriding to save this state in onSaveInstanceState (conditionally), and then using the state when recreating the Activity/Fragment, though we will have to be careful to ensure the conditions match exactly when the engine is going to stay around.
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
[Android] Save back handling state in Activity/Fragment bundle (#56715)
github-actions commentedon Dec 18, 2024
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.[Android] Save back handling state in Activity/Fragment bundle (flutt…