We have a 1v1 game using Playfab's default matchmaking system. It used to work fine, but something seems to have changed over the last month, breaking the matchmaking for us.
Our timeline of events:
1. Player `EB78A8BF8D304118` tries to start a game using `PlayFabClientAPI.Matchmake`
2. Playfab starts a game with LobbyID `67311E2D67352DD7`
3. Player receives ticket `EB78A8BF8D304118-0-D773B4A9A0727711-7F6A-8D4B4372D6BD160-1E7880FDD862CCB3.BCF62808CBCFB7FE`
4. Player connects to Game Server and sends matchmaking ticket data
5. Game Server attempts to validate the connected player's matchmaking ticket using `PlayFabServerAPI.RedeemMatchmakerTicket`
6. Game Server receives the response `{"HttpCode":400,"HttpStatus":"BadRequest","Error":1024,"ErrorMessage":"Game not found"}`
7. Player is restarted to try the process again, using `PlayFabClientAPI.Matchmake`
8. Player receives ticket `EB78A8BF8D304118-0-D773B4A9A0727711-7F6A-8D4B4373B64C1A2-F04193A7658F343A.D194DAFA6352C456`
9. This ticket is sent to the same Game Server instance, validated successfully, and everything works great
Looking at the Lobby's playstream, we see this:
http://i.imgur.com/MJazhmn.png
And in text form, with all the details:
https://gist.github.com/anonymous/0b94ba478ba972d6888b4a0d86c27c21
This problem happens consistently. We're not sure if it's a problem with our implementation, or the Playfab API.