You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm trying to perform matchmaking and running into a DeJson failure due to missing keys:
ERROR nakama_rs::web_socket: handle_message: Failed to parse json: Json Deserialize error: Key not found party_id, line:1 col:404
The call to add_matchmaker is as follows:
let match_maker = Matchmaker {
min_count: 2,
max_count: 2,
string_properties: Default::default(),
numeric_properties: Default::default(),
query: "*".to_string(),
};
let ticket = web_socket.add_matchmaker(&match_maker).await;
If I modify socket.rs to add the #[nserde(default)] attribute to the appropriate field in MatchmakerUser the failure mode moves on to the same issue with string_properties and numeric_properties.
Adding the attribute to all three as follows enables the matchmaking to proceed:
After the above, similar errors occur for the authoritative and label fields in Match. Adding default attributes to these allow the matchmaking and match joining to proceed. Not sure if the applied default values are appropriate.
I'm trying to perform matchmaking and running into a DeJson failure due to missing keys:
The call to
add_matchmaker
is as follows:If I modify
socket.rs
to add the#[nserde(default)]
attribute to the appropriate field inMatchmakerUser
the failure mode moves on to the same issue withstring_properties
andnumeric_properties
.Adding the attribute to all three as follows enables the matchmaking to proceed:
After the above, similar errors occur for the
authoritative
andlabel
fields inMatch
. Adding default attributes to these allow the matchmaking and match joining to proceed. Not sure if the applied default values are appropriate.The full exchange of messages is as follows:
The text was updated successfully, but these errors were encountered: