Skip to content

Conversation

@NoelStephensUnity
Copy link
Member

@NoelStephensUnity NoelStephensUnity commented Jan 28, 2026

Purpose of this PR

Fixes the issue where NetworkManager would not clean up if an exception was thrown while it was starting. This could result in a host or server not completing the start process yet would still have internal systems (i.e. NetworkConnectionManager, NetworkMessageManager, and UnityTransport) initialized. If a client attempted to connect to a server or host in this state it could result in the server or host logging the following error message:
[Netcode] A ConnectionRequestMessage was received from the server on the client side.

Jira ticket

MTT-13631
fix: #3552

Changelog

  • Fixed: Issue where NetworkManager was not cleaning itself up if an exception was thrown while starting.

Documentation

  • No documentation changes or additions were necessary.

Testing & QA (How your changes can be verified during release Playtest)

Functional Testing

Manual testing :

Automated tests:

  • Covered by existing automated tests
  • Covered by new automated tests

Does the change require QA team to:

  • Review automated tests?
  • Execute manual tests?
  • Provide feedback about the PR?

If any boxes above are checked the QA team will be automatically added as a PR reviewer.

Backports

TBD

Fixes the issue where NetworkManager would not clean up if an exception was thrown while it was starting.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

ConnectionRequestMessage was received from the server on the client side

2 participants