When receiving the packet with the guid in the reply, this guid is of type string, since a json string doesn't automatically get parsed back. This was not caught by the tests since they use the JObject directly instead of round-tripping through the json string representation, which causes extra type information to be kept around.
When receiving the packet with the guid in the reply, this guid is of type string, since a json string doesn't automatically get parsed back. This was not caught by the tests since they use the JObject directly instead of round-tripping through the json string representation, which causes extra type information to be kept around.