Signal stops receiving messages during an active conversation

[bme13]

Guidelines

• I have searched searched open and closed issues for duplicates
• I am submitting a bug report for existing functionality that does not work as intended
• This isn't a feature request or a discussion topic

Bug description

While having a conversation all of a sudden I only see one mark indicating my conversation partner doesn't receive my message.
Today I start a conversation with this person while the last conversation was the 25th of January. The first message arrives correctly so it doesn't seem to be an FCM/background issue. Next I receive 2 messages and when sending a new message, this message only get's one mark. These are the timestamps:
11:52, my first message
11:52, 2 reply's
11:54 my next message (containing a photo and text) that does only get one checkmark. (message id: 1738925651377)
Called this person and asked to open Signal. Than the message came through. Asked for a debug log, so the attached log is from the receiving device.

Screenshots

No response

Device

Samsung SM-A546B

Android version

14

Signal version

7.31.1

Link to debug log

https://debuglogs.org/android/7.31.1/1d61b2072b4f72bdb1f79a37599c8f119b807b097a50cdf4e773fb36a3f39106

[x64x2]

could be an ISP issue.

[bme13]

In the original description the situation did not resolve automatically but here's a log that I have more frequently with this contact. It's a bit similar in that the original message goes through fast, but the next message takes a much longer time. Here's the timeline:
18:02 original message (id 1739034167965)
18:04 received response, 2 messages
18:06 next message (id 1739034393637) this one takes a few minutes to arrive.
Here's the log of the receiving device again. Looking at it I see a couple of onStop/onDestroy messsages. Does that mean the user closes the app?

https://debuglogs.org/android/7.32.2/45e8d028f2781704172b2323ef6a02b31c8b268f1cff10d2837ba09d6a0a5b01

[MR-Bagga]

I'm getting duplicate message exception error do you in which signal or libsignal client version did they solve tis issue?