Search Issue Tracker
Third Party Issue
Votes
0
Found in
1.2.1
Issue ID
UUM-134994
Regression
No
SessionException: Unexpected exception processing network metadata when client joins session while host starts Relay
*Client scripts attached to ticket
Steps to reproduce:
- Host creates a Session without {{WithRelayNetwork()}} (solo lobby, no networking)
- A second client joins the session via join code
- Host calls {{StartRelayNetworkAsync()}} when player count >= 2
- Client intermittently fails during network metadata processin
Actual results:
Client throws {{SessionException: Unexpected exception processing network metadata}} (~2/10 attempts). Inner exception shows "Joining network failed." No identifiable timing pattern.
Expected results:
Client successfully processes relay network metadata and connects without error.
Reproducible with versions: Unity 6000.0.58f2 and com.unity.services.multiplayer@1.2.1
Not reproducible with versions:
Can’t test with versions:
Tested on (OS):
Notes:
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Texture generator reference image fails despite valid size
- Agent mode can enter infinite execution loop
- AI Gateway responses contain duplicated sentences
- Texture 2D asset is created when promoting a generated Cubemap to a new asset
- Unable to copy multiple paragraphs from Assistant responses
Resolution Note:
Thank you for reporting a bug to Unity.
Our investigation indicates the issue originates from a third-party asset, plugin, or service, rather than Unity itself. Because the problem lies outside our codebase, we're unable to address it directly.
We will close this case as a third-party issue. We recommend contacting the vendor or maintainer for support. If you have evidence that the issue is within Unity, please share it and we will re-open the investigation.
Resolution Note:
Thank you for reporting a bug to Unity.
Our investigation indicates the issue originates from a third-party asset, plugin, or service, rather than Unity itself. Because the problem lies outside our codebase, we're unable to address it directly.
We will close this case as a third-party issue. We recommend contacting the vendor or maintainer for support. If you have evidence that the issue is within Unity, please share it and we will re-open the investigation.