text messages cut

[bl-kl2]

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

Starting from approx end of 2024 - start of 2025, both sent and received messages started to being cut if length > something like, dont know, dont remember, 512 bytes?

The issue does happen apparently at random, while of course its a bug, so the bug lies somewhere.

This is of course a really, really serious issue.

I am starting to put at end of each message something like ENDD, to make sure the other person knows that the message has been transmitted and received completely and not truncated, and people I am communicating with are starting to do the same.

Often, too much often, we experience truncated messages, so it is greatly annoying, being that we must either split the original message, if on a desktop device connected to the smartphone,
but if on smartphone the cut portion of message would be lost, so we have always to copy the whole message before sending it.

The most important feature of Signal is to send messages, aint it?

If this stops working, Signal then stops being what is supposed to be, or at least at its birth.

Screenshots

No response

Device

No response

Android version

No response

Signal version

7.28.4

Link to debug log

No response

[greyson-signal]

You're on a pretty old signal version. Can you update to latest? Can you also share what language you're writing messages in?

[bl-kl2]

I just updated the Signal app, my previous version was released dec 21 2024, and I am pretty sure that the problem appeared before this date.

Same identical problem with one of my co-workers, meaning he uses Signal too, and he too sometimes with long messages does experience cutting.

He has an updated Signal Desktop on Linux.

Language used is only english, smartphone and laptop language settings are english, both for me and my co-worker.
Also, no unicode multiple bytes chars, accented letters etc.

I will try to have an example of a message constantly truncated, also if I fear that its more a race condition or similar.

The excruciating thing is that this happens apparently at random.

Now I am working on that, i.e. having the cut repeatable (meaning a known cut message that would always or at least by a fair noncut/cut ratio be cut again), but if we will not succeed in that, I will update this thread anyway.

[greyson-signal]

I've tried to reproduce the issue, but unfortunately can't. Can you tell me more about your device? A log would be really helpful, if only to get details about your device.

[bl-kl2]

The issue happens at least with 2 different devices.
Now, as said in previous message, I am trying to reproduce in a reliable way the issue, but until now no luck.

But I have been able to recover 3 original cut messages, and the interesting thing is that the 3 messages are cut at byte 2047-2048, and it seems that, for the cut to happen, the byte 2048-2049 needs to be a space char.

Also, 2047-2048 and 2048-2049 discrepancies maybe are related to a newline yes/no, in the copied original messages.

I will update here when I will have more data, and of course if we will be able to constantly reproduce the issue I will add further details.