Indicates that the call to increment achievement failed since the achievement is not an incremental achievement.

Could not find the achievement, so the operation to update the achievement failed.

An incremental achievement cannot be unlocked directly, so the call to unlock achievement failed.

Indicates that the incremental achievement was also unlocked when the call was made to increment the achievement.

The developer has misconfigured their application in some way. The logs will contain more data about the error and the appropriate resolution.

The specified game ID was not recognized by the server.

The real-time room ID provided to the operation was not valid, or does not correspond to the currently active real-time room.

The game is not licensed to the user. Further calls will return the same code.

The specified match has already had a rematch created. Only one rematch may be created for any initial match.

The match is not currently active. This action cannot be performed on an inactive match.

The match results provided in this API call are invalid. This covers cases of duplicate results, results for players who are not in the match, etc.

The match is not in the correct state to perform the specified action.

One or more participants in this match are not in valid states. This could occur if a specified participant is not actually a participant of the match, or is invalid, or is in an incorrect state to make the API call. Check the logs for more detailed information.

The specified match has already been modified locally. This operation cannot be performed until the match has been sent to the server.

The match data is out of date. Someone else has modified the data on the server, so the request could not be completed safely.

The specified match cannot be found. The provided match ID does not correspond to any known match.

This game does not support multiplayer. This could occur if the linked app is not configured appropriately in the developer console.

The user is not allowed to create a new multiplayer game at this time. This could occur if the user has too many outstanding invitations already.

The match is not the right type to perform this action on. For example, this error will be returned when trying to take a turn in a real-time match.

This multiplayer operation is not valid, and the server rejected it. Check the logs for more information.

The user attempted to invite another user who was not authorized to see the game. This can occur if a trusted tester invites a user who is not a trusted tester while the game is unpublished. In this case, the invitations will not be sent.

A network error occurred while attempting to retrieve fresh data, and no data was available locally.

A network error occurred while attempting to perform an operation that requires network access. The operation may be retried later.

Trying to start a join/create operation while another is already in flight.

The ID of the participant provided by the user is not currently connected to the client in the real-time room.

Failed to initialize the network connection for a real-time room.

The room is not currently active. This action cannot be performed on an inactive room.

Failed to send message to the peer participant for a real-time room.

Failed to send message to the peer participant for a real-time room, since the user has not joined the room.

The attempt to commit the snapshot change failed. See the device logs for more details.

The conflict that was being resolved doesn't exist. This could occur if another device resolved this conflict first, or if an inappropriate conflict ID was provided to resolveConflict().

An error occurred while attempting to open the contents of the snapshot. See the device logs for more details.

The attempt to create a snapshot failed. See the device logs for more details.

The root folder for snapshots could not be found or created. See the device logs for more details on the failure.

The specified snapshot does not exist on the server.

Request could not complete because we were already capturing.

Request could not complete because there is no active screencast capture session.

Request could not complete because the device is out of disk space.

Request could not complete due to permission problems.

Request could not complete due to a storage I/O error.

Request could not complete because something unrecoverable happened in the capture service.

Request could not complete because the request or its options are not supported.