Response closed without grpc-status (headers only)

[carsonfarmer]

This is a common error that we see coming from various Threads Clients. It is essentially the default error coming back from a Client that doesn't receive a valid response from the Proxy gRPC service. There are a number of common reasons for this error:

• The Service the Client is attempting to connect to isn't running.
  • This can happen if your local threadsd isn't running, or was shut down.
  • Check that your threadsd is still running.
  • Alternatively, if you are connecting to a remote service, make sure the host url you are using is correct.
• The request being sent to the service is malformed.
  • This can happen if there are issues with some input to the Client (perhaps the ThreadID is invalid, etc), or the Client isn't correctly marshaling the data into a protobuf.
  • Check that your inputs are correct/the right types.
  • If you are running in React Native or some environment other than Go or Typescript/Javascript, it is possible there are issues with Bytes handling.
  • You might want to ask in the Slack channel if this might be the case.

We will add to the above list of possible issues and fixes as we discover them, and attempt to close some of those potential gotchas along the way.