status-go: bug: message stuck in sending status for a long time

Problem

Have noticed this multiple times and even during dogfooding session, a message that is sent whose status is still shown as sending. Eventhough the message is received by other side in 1:1 chat, group chat and in this case community.

Attaching the logs for reference. MessageID of the message is 0xf37863ffcb2fcc6d7d05653a25db2ef4d808fa4e1a6cf584b5ddc4587ff82648

Even after 5 minutes, message is still shown as sending status.

Acceptance Criteria

Message should not be showing sending status for soo long especially if it is already delivered.

Notes

image

geth.log.gz

About this issue

  • Original URL
  • State: open
  • Created 2 years ago
  • Comments: 15 (14 by maintainers)

Most upvoted comments

Will we still depend on store-query to change sending status to sent at UserA’s side? If so, then we need to fix it.

No, the ack message will also change the state from outging (or sending) to sent.

Ideally status can be changed by any sort of ack either by mvds, store-query or e2e protocol that is being built at a later point in time.

This is a good idea, we need to encapsulate the interface for better usage in different reliability solutions.

I am also wondering what is the behaviour for the following scenario? The reason for this query is we have observed this behaviour even in case of 1:1 chat during our dogfooding session.

What if userA sends a message to UserB in 1:1 chat and mvds also acks receipt of message by UserB. Will we still depend on store-query to change sending status to sent at UserA’s side? If so, then we need to fix it.

Ideally status can be changed by any sort of ack either by mvds, store-query or e2e protocol that is being built at a later point in time.