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
[UIScene] SceneLifeCycle API to register/unregister the engine can be error prone #185689
If you manually register a FlutterEngine with a scene, you must also unregister it if the view created by the FlutterEngine changes scenes.
// If using FlutterSceneDelegate:
self.unregisterSceneLifeCycle(with: flutterEngine)
// If using FlutterSceneLifeCycleProvider:
sceneLifeCycleDelegate.unregisterSceneLifeCycle(with: flutterEngine)
Issues:
It's unclear where to call unregister in the doc (so we should polish the doc)
This API can be error prone - developers could easily forget to call register/unregister (especially unregister).
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
hellohuanlin commentedon Sep 9, 2026
It turns out that we still have to have register/unregister APIs, but we only need it for edge cases when Flutter VC is not added on the screen.
Also we should add a
sceneparameter, since oneUISceneDelegatecould power multipleUIScenes.[ios] Use DFS traversal to find engines of a scene automatically (rat…
[ios] Use DFS traversal to find engines of a scene automatically (rat…
github-actions commentedon Oct 30, 2026
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.