Bug: Stream of new messages does not emit all new messages

[bselwe]

Describe the bug

When the stream of messages streamBatchMessages is idle for 5-15 minutes (there is no new message received within that time), it sometimes fails to emit all new messages by skipping the first few messages.

Expected behavior

The stream of messages streamBatchMessages delivers all new messages in the given conversations.

Steps to reproduce the bug

listenToMessages(List<xmtp.Conversation> conversations) {
  recovery.cancel("messages");
  messagesSubscription?.cancel();
  messagesSubscription = client.streamBatchMessages(conversations).listen(
    (newMessage) async {
      debugPrint(
        '${DateTime.now()} [Conversations]: New message from ${newMessage.sender}: ${newMessage.content}',
      );

      send(NewMessageResponse(newMessage));
    },
    onError: (_) {
      recovery.cancel("messages");
      messagesSubscription?.cancel();
      recovery.attempt("messages", () => listenToMessages(conversations));
    },
  );
}

For recovery, see this.

[bselwe]

I've noticed that streamBatchMessages quite often emits a GRPC error, which might be related:

gRPC Error (code: 4, codeName: DEADLINE_EXCEEDED, message: Deadline exceeded, details: null, rawResponse: null, trailers: {})

[giovasdistillery]

@bselwe the whole day I tried to reproduce the error but I was not able to do it, the worst case scenario I can see is a lack of 3-4 minutes to get messages, but I received all messages, Could you please add more descriptive way to reproduce the error?