Breaking News: Grepper is joining You.com. Read the official announcement!

Looking up a deactivated widget's ancestor is unsafe. dispose AnimationController

nidal bakir answered on January 10, 2024 Popularity 5/10 Helpfulness 1/10

answer Looking up a deactivated widget's ancestor is unsafe. dispose AnimationController

Looking up a deactivated widget's ancestor is unsafe. dispose AnimationController

Comment

The bug could be a late `AnimationController`:
Since _controller is marked late and the first time
_controller is accessed is in the dispose method,
the AnimationController is actually created during dispose
(and then of course disposed right away). 
Instantiating an AnimationController with a disposed
TickerProvider is not allowed (and also doesn't make much sense).
That's why you see the crash.
Either use the _controller variable before dispose so it is initialized
when dispose is called.
Or mark the variable as nullable and instantiate
the controller in initState.

Popularity 5/10 Helpfulness 1/10 Language dart

Source: Grepper

Tags: ancestor animationcontroller dart dispose

Link to this answer
Share Copy Link

Contributed on Jan 10 2024

nidal bakir

0 Answers Avg Quality 2/10

Continue with Google

By continuing, I agree that I have read and agree to Greppers's Terms of Service and Privacy Policy.

Looking up a deactivated widget's ancestor is unsafe. dispose AnimationController

Contents

More Related Answers

Looking up a deactivated widget's ancestor is unsafe. dispose AnimationController

Grepper

Documentation

Social

Legal

Contact

Oops, You will need to install Grepper and log-in to perform this action.