fix: handle SDK disposal gracefully to prevent crashes on app exit #3345
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.

Fixes unhandled exceptions that occur when the application is closed while widgets and BLoCs are still accessing a disposed KomodoDefiSdk instance. This ensures graceful error handling instead of crashes during app shutdown.
Related Issues
Fixes #3341
Related to #3339
lastKnownUsdBalanceand_listenToAuthStateChangesmentioned in #3341. Due to the app architecture, similar errors can occur elsewhere when exiting the application, where the SDK has already been disposed but some components, widgets, or BLoCs are still trying to access it.p.s. If this PR is considered for merging, we should also consider merging #3339, which fixes another set of errors that occur on exit in Linux: