signalapp / signalapp/Signal-Android
Messages sent out of order on slow network connections.
Nobody has claimed this yet.
- Dominant language
- Kotlin
- Stars
- 29.4k
- Forks
- 6.9k
- PR merge metrics
- No merged PRs in 30d
Description
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
On slow connections, especially when sending media, messages get sent out of order cause context issues for the recipient of the messages.
Subsequent messages should queue and wait for prior messages to complete sending, before sending, or messages should be time-stamped with the time sent by the sender, as opposed to transmitted to signals servers, thus retaining temporal accuracy.
Screenshots
No response
Device
Samsung Z Fold4
Android version
Android 16
Signal version
7.70.2
Link to debug log
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No file or test is named. First reproduce the issue on a slow connection while sending media and inspect how subsequent messages are queued and ordered; done means recipients see messages in the sender's intended temporal order, with a regression test covering the case.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kotlin
- Domain
- mobile-dev
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 38/100