When calling Matchmake from UE4 blueprint, PlayFab does not return the correct error code for "GameNotFound", instead returns 200
LogPlayFab: Request: {
"BuildVersion": null,
"CharacterId": null,
"GameMode": null,
"LobbyId": "11810456334627489889",
"Region": "EUWest",
"StartNewIfNoneFound": false,
"StatisticName": null
}
LogPlayFab: Response : {"code":200,"status":"OK","data":{"Status":"GameNotFound"}}
Sorry for the delay getting back to you on this. Long story short, that's the correct result. It's not an error, because the call to Matchmake itself didn't fail. The call specified a Lobby ID which doesn't exist. The code checks for that lobby, sees that it isn't in the available set, and says "well, your call was fine, but that lobby isn't available, so I'm returning you an empty set".
Since this API call has worked this way since it was introduced, it's not something we'd be able to change, since that would break every existing title that uses it (we have a firm policy against breaking changes).
Hi Brendan. Thanks for the reply. I understand, but when can I expect the error code: 1025 to be returned then as is described in the API docs ?
2 People are following this question.
