Ask a Question

Ask a Question
Back to All

Matchmaking Error on Room ID

Hello,

Sometime around last week, based on feedback from internal testers, we started running into a critical crash during the matchmaking process to find a room for players. We attempted to replicate the bug, and the first match went perfectly fine and put two players into a lobby. However, the next four attempts crashed about 15 seconds into the matchmaking process (MaxWait is set to 240 seconds). Below is the attached error message log from Beamable's Platform Requester Exception:

Beamable Error:
PlatformRequesterException: HTTP Error. method=[GET] uri=[https://api.beamable.com/matchmaking/matches/3dd87440-4d4f-49a1-848a-25a65ac1bbb7] code=[404] payload=[{ "status": 404, "error": "LobbyNotFound", "description": "Unable to find lobby with id: 3dd87440-4d4f-49a1-848a-25a65ac1bbb7" }]
Beamable.Common.Promise`1[T].GetResult () (at Library/PackageCache/[email protected]/Common/Runtime/Promise.cs:427)
Beamable.Experimental.Api.Matchmaking.MatchmakingHandle+d40.MoveNext () (at Library/PackageCache/[email protected]/Runtime/Core/Platform/SDK/Matchmaking/MatchmakingService.cs:324)
--- End of stack trace from previous location where exception was thrown ---
System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw () (at :0)
System.Runtime.CompilerServices.AsyncMethodBuilderCore+<>c.b
6_0 (System.Object state) (at :0)
UnityEngine.UnitySynchronizationContext+WorkRequest.Invoke () (at <028e4d71153d4ed5ac6bee0dfc08aa3b>:0)
UnityEngine.UnitySynchronizationContext:ExecuteTasks()

Prior to last week, we had not received this error message, and nothing has been changed in the matchmaking code or process. Unsure what the error could be or why it is unable to find the lobby id created. If you have any insight or feedback on what could be causing it, let me know as soon as you can. Thanks.