Search Issue Tracker
Fixed
Fixed in 1.2.1
Votes
0
Found in [Package]
1.2.0
Issue ID
MTTB-1724
Regression
Yes
Joining a session created with RelayProtocol.WSS throws Mismatched Relay configuration ArgumentException
Steps to reproduce:
- Open the attached project
- Open the MainMenu Scene
- Open the Multiplayer Play Mode Window and start a Virtual Player
- Enter Play mode
- In the Game view, enter a Player name and press Enter (This will enable the "Play Now!" button)
- Press the "Play Now!" button (This will transition the menu to the lobby screen)
- Repeat steps 5 and 6 in the Virtual Player window
Actual results: Virtual Player is connected to the session without issues
Expected results: Virtual Player is not connected to the same session, and errors related to Mismatched Relay configuration ArgumentException are thrown
Reproducible with versions: 1.2.0 (6000.2.11f1, 6000.3.0b9, 6000.4.0a4)
Not reproducible with versions: 1.2.0-pre.1 (6000.2.11f1, 6000.3.0b9, 6000.4.0a4)
Can’t test with versions: 1.1.8 (RelayProtocol.WSS was not yet available)
Tested on (OS): macOS 26.0.1
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
- [WebGPU] clearing 2d array texture only clears first slice
- Particle System Renderer icon is missing in Animation window > Add Property context menu
- [Android] Legacy, TMP and UI Toolkit Input Field language toggle to some non-latin alphabet languages does not work with external keyboard
- Crash on keywords::LocalKeywordState::operator when calling ShaderUtil.GetPasskeywords with ShaderType.RayTracing set as the third parameter
- Inconsistent “Remove property” behavior when removing child properties in Animator window
Resolution Note (fix version 1.2.1):
The RelayProtocol set in joining clients through the SessionOptions is properly used when joining a session instead of the default platform value.
Known issue:
The RelayProtocol option is not available when using MultiplayerServices APIs with the JoinSessionOptions or ReconnectSessionOptions (i.e: JoinSessionByIdAsync, ReconnectToSessionAsync, ...) preventing using these APIs with a custom RelayProtocol. Work is being planned to allow this behaviour in a future version.