Skip to content

[UIScene] Migration plan for FlutterSceneLifeCycleEngineRegistration #185702

New issue
New issue
Closed
#192457
Closed
[UIScene] Migration plan for FlutterSceneLifeCycleEngineRegistration#185702
#192457
Labels
P2Important issues not at the top of the work listplatform-iosiOS applications specificallyteam-iosOwned by iOS platform teamtriaged-iosTriaged by iOS platform team

Description

@hellohuanlin
hellohuanlin
opened on Apr 28, 2026

Use case

As discussed in #185689, FlutterSceneLifeCycleEngineRegistration's API can be error-prone.

If we adopt the proposal discussed in #185690, developers won't have to manually register/unregister the engines. However, it's already a public API, so we can't just remove it. We should come up with ways to phase it out without breaking existing client.

Proposal

We should be able to just make both register/unregister APIs no-op (to be confirmed), or just print out a warning.

Creating a separate issue here as a reminder that it's public API and we should carefully handle the transition and not to break existing client.

Activity

  1. hellohuanlin
    added
    platform-iosiOS applications specifically
    team-iosOwned by iOS platform team
    on Apr 28, 2026
  2. hellohuanlin
    added a parent issue on Apr 28, 2026
  3. hellohuanlin
    added
    P2Important issues not at the top of the work list
    triaged-iosTriaged by iOS platform team
    on Apr 30, 2026
  4. auto-submit
    closed this as completedin #192457on Oct 16, 2026
  5. richyo-codes
    added a commit that references this issue on Oct 16, 2026

    [ios] Use DFS traversal to find engines of a scene automatically (rat…

    4ba130c
  6. suryaKommana2662
    added a commit that references this issue on Oct 29, 2026

    [ios] Use DFS traversal to find engines of a scene automatically (rat…

    952b8d6

  7. github-actions commented on Oct 30, 2026

    @github-actions
    github-actionsBot
    on Oct 30, 2026 – with GitHub Actions

    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.

  8. github-actions
    locked as resolved and limited conversation to collaborators on Oct 30, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    P2Important issues not at the top of the work listplatform-iosiOS applications specificallyteam-iosOwned by iOS platform teamtriaged-iosTriaged by iOS platform team

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions