Skip to content

Reactivate should guarantee rebuild #2901

Closed

Description

@Hixie

We've been assuming that if you're ever reactivated, you will be rebuilt, but actually if you're reprojected that might not be true.

This leads to things like Inherited not properly notifying descendants when they move around and get a new Inherited ancestor.

Activity

  1. added
    frameworkflutter/packages/flutter repository. See also f: labels.
    on Mar 25, 2016
  2. added this to the milestone on Mar 25, 2016
  3. Hixie commented on Mar 25, 2016

    @Hixie
    ContributorAuthor

    also means that if you disconnect from an ancestor when you deactivate (e.g. disconnecting from a Material that's doing your splashes), you won't reconnect.

  4. self-assigned this
    on Mar 29, 2016
  5. added a commit that references this issue on Mar 29, 2016
    b841e86
  6. github-actions commented on Aug 16, 2021

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

  7. locked as resolved and limited conversation to collaborators on Aug 16, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

frameworkflutter/packages/flutter repository. See also f: labels.

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions