Text longer than 2048 characters truncated when copied from collapsed message

[DirkPitt1]

• I have searched open and closed issues for duplicates
• I am submitting a bug report for existing functionality that does not work as intended
• I have read https://github.com/signalapp/Signal-Android/wiki/Submitting-useful-bug-reports
• This isn't a feature request or a discussion topic

---

Bug description

On Signal Android when copying collapsed long message (>2048 characters) from message thread, text gets cut to first 2048 characters. It's consistent behavior and works that way every time. I suspect it's restriction from time when max Signal message length was 2000 characters that weren't removed.

When copying expanded long message in Read more view through Select all>Copy, all the message text is copied.

This can potentially occur on Signal iOS too but I can't confirm this since I haven't iPhone.

Steps to reproduce

• Receive/send very long message (about 3000 characters).
• Select collapsed message and copy .
• Paste it somewhere.

Actual result:
Pasted text is only 2048 characters long. The rest of copied message is missing.

Expected result:
Entire message text is copied and pasted.

Device info

Device: LG G4
Android version: 6
Signal version: 4.58.1

[Meteor0id]

This bug is a continuous annoyance, it's easy to fall into the trap of copy pasting a message and deleting it only to discover later that part of the message was never copied.

[AnantTiwari-Naman]

Yep, is a rather bad bug.

[Schweineschwarte]

It is still in version 5.25.7

[stale]

Is this still relevant? If so, what is blocking it? Is there anything you can do to help move it forward?

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.

[Meteor0id]

To my knowledfe this bug still exists but has been ignored by the devs.

[stale]

Is this still relevant? If so, what is blocking it? Is there anything you can do to help move it forward?

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.

[Meteor0id]

This issue still exists and was again mentioned by someone in the beta thread this week. I wonder if it is even being tracked internally because it has been around so long.

[greyson-signal]

We're tracking it

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.