error with Matchmaker/UserInfo

Question

question

rogerolier asked Nov 22, '17

error with Matchmaker/UserInfo

We are having a strange error with Matchmaker/UserInfo with only specific users.

We suspect is something wrong about how this users are implemented, but we don't understand where is the error, as all other apis work perfectly.

Title id is 661F and a user that makes the error is for example 5E487EA40D24A68E

The response is:

{
"code": 500,
"status": "InternalServerError",
"error": "InternalServerError",
"errorCode": 1110,
"errorMessage": "An unexpected error occured while processing the request.",
"errorHash": "97ea20c543d5a9672098fff695bd65f7",
"errorDetails": {
"RequestID": [
"3c0bb141d2624a26b2eb688df30660c4"
]
}
}

apis Matchmaking

10 |1200

Attachments: Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

Answer 1 · 2017-11-22T02:26:26Z

brendan answered Nov 22, '17

Thanks for the full details of the response - with a 500 error (which tells us something unexpected happened), the Request ID is what allows us to find the details.

In this case, the call to UserInfo was:

{"PlayFabId": "5E487EA40D24A68E", "MinCatalogVersion": 0}

This highlights an essential error in that API call, for which I've opened a bug - CatalogVersion is a string, not an int. When this function was created (very early in our history), CatalogVersion had to be a numeric value - that's no longer the case. What I would recommend is one of two things:

1. Make all your CatalogVersion values be integer values - literally a version number.

2. Use Server/GetPlayerCombinedInfo instead.

And thanks for the catch, by the way - the Matchmaker API is rarely used, which is how this hadn't come up before. We'll likely need to deprecate this API call in favor of putting something like GetPlayerCombinedInfo in the Matchmaker API.

10 |1200

Attachments: Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

question