Closed 0oM4R closed 1 year ago
I really think this is just a problem with the implementation of the client. The error response in the envelope might have a code, but will always have an error message explaining what happened.
I really think this is just a problem with the implementation of the client. The error response in the envelope might have a code, but will always have an error message explaining what happened.
the error we got in the client is just code: 102
i tried to log the envelop.error and got the same message:
That is so weird, I will take another look.
@0oM4R
Can you explain to me where the Error
object in the screenshot above is coming from ? because that's not what rmb sends back. this has been constructed somewhere else in the code from the original response
we have faced this error recently and the error message wasn't clear
https://github.com/threefoldtech/rmb-rs/blob/3a2166459eeeb4782648c7f79ba80fe4da22d68f/src/types/mod.rs#L35
we can make the error more descriptive and mention that the ttl or massage expired