-
-
Notifications
You must be signed in to change notification settings - Fork 463
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
PaneItemEpander Widget crashes the app when the Pane is collapsed🐛 #670
Comments
It's be very helpful if you could run the app with |
══╡ EXCEPTION CAUGHT BY SCHEDULER LIBRARY ╞═════════════════════════════════════════════════════════ When the exception was thrown, this was the stack: Another exception was thrown: setState() called after dispose(): _StickyNavigationIndicatorState#0405b(lifecycle state: defunct, not mounted, tickers: tracking 0 tickers) Another exception was thrown: This widget has been unmounted, so the State no longer has a context (and should be considered defunct). Another exception was thrown: setState() called after dispose(): _StickyNavigationIndicatorState#80327(lifecycle state: defunct, not mounted, tickers: tracking 0 tickers) Another exception was thrown: This widget has been unmounted, so the State no longer has a context (and should be considered defunct). Another exception was thrown: setState() called after dispose(): _StickyNavigationIndicatorState#85c9b(lifecycle state: defunct, not mounted, tickers: tracking 0 tickers) |
I have same problem but different error message. Please reopen this issue. Also I see same problem on example website(https://bdlukaa.github.io/fluent_ui/). My code:
My Error:
|
Describe the bug
PaneItemEpander Widget crashes the app when the Pane is collapsed.
To Reproduce
Steps to reproduce the behavior:
'Consider canceling any active work during "dispose" or using the "mounted" getter to determine if the State is still active.', thrown
Expected behavior
I expected the Navigation to not crash the entire application and throw an error.
Screenshots
The text was updated successfully, but these errors were encountered: