Fix: Prevent TypeError in network applet when devices is undefined #13444
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.
This PR fixes a TypeError that appears in logs (and potentially affects UI rendering) when a connection is removed while
devicesis undefined.The issue:
In
_connectionRemoved, the code accessesdevices.lengthwithout checking ifdevicesexists. This can happen during specific wake-from-sleep scenarios or network resets.The fix:
Added a null check (
if (devices)) before iterating over the devices list.Verification:
Tested locally on Linux Mint. The error no longer appears in logs when network state changes.
issue found here : #12721