Fix: Remove unused setState causing error after widget disposal #24
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This PR removes unnecessary
setState
call from InfoPopupWidget that can trigger runtime errors after the widget has been disposed.Problem
When navigating back while a popup is still visible, the following assertion error is thrown:
This occurs because
setState
is being called after the widget has been disposed.Steps to Reproduce
Proposed Solution
Removed the
setState
call that is invoked after the widget may have already been disposed. Based on testing, this change does not impact the functionality of the widget.