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
didChangeDependencies docs don't specify where to call super #28925
didChangeDependencies annotation says we must call super.didChangeDependencies() if we override this method in a State class, but the docs don't specify if we should do it at the beginning or at the end, like initState and many others do specify.
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
pushpendraKh commentedon Aug 20, 2019
any update on this?
jhon2520 commentedon Aug 11, 2024
Any update ?
navaronbracke commentedon Mar 24, 2026
When looking at the framework itself, it looks like it is also not consistent: https://github.com/search?q=repo%3Aflutter%2Fflutter%20didChangeDependencies()&type=code
However, considering it is a "constructive" lifecycle method, I would expect implementers to have to call the super method first in the override.
Document super call order for State.didChangeDependencies
Document super call order for State.didChangeDependencies
Document super call order for State.didChangeDependencies (flutter#18…
github-actions commentedon Aug 19, 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.