Added null check in NetworkLatencyWarning #516
Merged
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 simply adds a check to prevent NullReferenceExceptions from happening when NetworkManager's singleton instance is destroyed.
Related Pull Requests
Issue Number(s) (*)
Fixes issue(s): Those NREs are observed in the log attached to MTT-2656 but I'm not sure if it's actually linked to the bug described there.
Manual testing scenarios
Questions or comments
Contribution checklist