Search Issue Tracker
Active
Votes
0
Found in [Package]
1.1.6
Issue ID
MTTB-1525
Regression
No
Matchmaking fails on WebGL with Unity Multiplayer Services due to QoS issue
Unity Discussion post with context: [https://discussions.unity.com/t/matchmaking-fails-on-webgl-with-unity-multiplayer-services-due-to-qos-issue/1679817]
*Steps to reproduce:*
# Create project with Multiplayer package
# Set up Matchmaking, and call {{MatchmakeSessionAsync}} and {{{}QosService.Instance.GetQosResultsAsync(){}}}.
# Build and run for Web
*Actual results:* Hangs indefinitely during the QoS measurement phase
*Expected results:* Function returns
*Reproducible with versions:*
* *Unity Version:* 6000.0.53f
* *Unity Multiplayer Services:* 1.1.6
*Not reproducible with versions:*
*Can’t test with versions:*
*Notes:*
* Question from user: "Are there any plans to add logic to the matchmaking part of the SDK to automatically skip QoS on WebGL, similar to how other services handle it?"
* From the user: "It appears that the matchmaking component lacks this specific check for WebGL. As a result, it attempts to perform a QoS measurement, which is not supported on the WebGL platform, causing it to freeze... By adding a preprocessor directive ({{{}#if UNITY_WEBGL{}}}) [in PreparePlayerAsync], we can bypass the QoS check specifically for WebGL builds."
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Asset creation in the Project Browser is not always undone/inconsistent when the undo shortcut is pressed right after creating an asset
- JobTempAlloc memory leak warning is thrown when the Player is shut down
- Graphics State Collection warm-up does not work when using with Addressables Shaders
- "Baked Shadow Radius" field is visible but inactive when when the Shadow Type is set to "Hard Shadows" under the Light Component
- Crash on OnDemandScheduler::HandleImportWorkerLogs when performing various Unity operations
Add comment