Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Some messages get stuck in "sending" status for sender despite they have been sent/delivered to receiver #15385

Closed
pavloburykh opened this issue Mar 16, 2023 · 3 comments · Fixed by #16260
Assignees

Comments

@pavloburykh
Copy link
Contributor

pavloburykh commented Mar 16, 2023

I faced the issue in all kind of chats but seems like it is easier to reproduce in community channels.

Preconditions: User A - sender, User B - receiver

Steps:

  1. Try sending several messages by User A to User B until some of the messages gets stuck in "sending" status
  2. See if such message has been received by User B

Actual result: Some messages get stuck in "sending" status for sender despite they have been sent/delivered to receiver

User_A_sender_logs.zip
User_B_receiver_logs.zip

message_sending_status.mp4

Additional Information

  • Status version: nightly
  • Operating System: Android, iOS
@pavloburykh pavloburykh added this to the 1.21.0-rc.2 milestone Mar 16, 2023
@vkjr vkjr self-assigned this Mar 24, 2023
@cammellos cammellos modified the milestones: 1.22.0, 1.23.0 Mar 28, 2023
@vkjr vkjr removed their assignment May 9, 2023
@cammellos cammellos self-assigned this Jun 6, 2023
@pavloburykh
Copy link
Contributor Author

Hi @cammellos ! If it is possible, could we prioritise this issue? It became a blocker for our e2e as in many tests we are relying on correct status of the message. And in fact this status remains in sending in many cases regardless message has been already delivered to receiver.

@cammellos
Copy link
Contributor

@pavloburykh I'll be looking at this today, thank you

@cammellos
Copy link
Contributor

I think I know the root cause,
it's most likely due to the fact that waku-1 was asynchronous when sending messages, while waku-2 is more synchronous, so the message is sent before it can be tracked.
I'll be looking at a solution today.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants