Messages sent after device sleep may stuck in "sending" state in community

[churik]

Bug Report

Problem

I believe the issue exists regardless of the fleet, but in the current release on shards.test version it is more noticeable.
Messages are completely stuck in "sending" state if they are sent after the device is unlocked. Re-login doesn't help, the messages are stuck there forever and they are not being resent.

Expected behavior

Messages are sent

Actual behavior

messages are stuck there forever and they are not being resent even after re-login

Reproduction

Prerequisites: device A joined to community

1. Lock the device and wait ~5 mins (app should be on the background)
2. Unlock the device and try to send a couple of messages to community

Logs (to be added)

Additional Information

• Status version: release 18
• Operating System: Android, iOS

[churik]

Currently can reproduce consistently with android sending from offline state - messages stuck in "Sending" state forever after getting back online

Logs: Status-debug-logs.zip

[pavloburykh]

UPDATE (22.01.24):

So far I am unable to reproduce this issue. Maybe something has been fixed on go-waku side recently, not sure.

But let's keep this issue open for a while. If we face it again we will post an update here.

[pavloburykh]

UPDATE (25.01.24):

I have been able to reproduce the bug on the recovered user. In my case the issue seems nothing to do with sleep mode or offline/online handling.

The issues have been reproduced both in communities and 1-1 chats.

Some of the messages have subsequently changed status from Sending to Sent and have been in fact delivered.
But some of the messages have been stuck in Sending status forever and have not been delivered (or delivered partially, i.e message contained text + 6 images but only text + 3 images have been delivered and 3 images have been lost).

Status-debug-logs (97).zip

[ulisesmac]

I tried to replicate the issue several times but I couldn't. Has it been solved? I tested on two physical Android devices and an emulator.

Tried following the steps in the description and also as specified in the comment #18284 (comment)
CC: @churik

This issue could be closed or maybe we need to specify exact steps to reproducte it 🤔

[churik]

It could be that it was fixed, as we enabled light client and several waku releases happened after that.
Thank you for taking a look.
I'll reopen if relevant