Skip to content

SchedulerBinding.scheduleForcedFrame currently behaves differently than it was originally designed #97473

Closed

Description

@ColdPaleLight

SchedulerBinding.scheduleForcedFrame currently behaves differently than it was originally designed. By design, the Application lifecycle does not affect SchedulerBinding.scheduleForcedFrame.

The issue (#45131) it depends on has now been fixed, so we can work on getting SchedulerBinding.scheduleForcedFrame to behave as design.

Activity

  1. added
    frameworkflutter/packages/flutter repository. See also f: labels.
    c: tech-debtTechnical debt, code quality, testing, etc.
    P2Important issues not at the top of the work list
    on Jan 29, 2022
  2. added
    r: fixedIssue is closed as already fixed in a newer version
    on Feb 5, 2022
  3. github-actions commented on Feb 19, 2022

    @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.

  4. locked as resolved and limited conversation to collaborators on Feb 19, 2022
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 listc: tech-debtTechnical debt, code quality, testing, etc.frameworkflutter/packages/flutter repository. See also f: labels.r: fixedIssue is closed as already fixed in a newer versionwaiting for PR to land (fixed)A fix is in flight

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions