element-hq / element-hq/element-ios

Robust automatic retry on choppy network conditions

Open
#4,711 1 comment 0 reactions 0 assignees View on GitHub
feature T-Enhancement
Dominant language
Swift
Stars
1.8k
Forks
544
PR merge metrics
PR metrics pending

Description

Clone of https://github.com/vector-im/element-android/issues/3837

---

Related to https://github.com/vector-im/element-android/issues/2803

Couldn't automatic retry be a thing for when all delivery failures are only network-related?

Telegram and WhatsApp have the ability to send messages whenever you want, after which a clock icon will appear that'll wait until it is either delivered or sent.

With Element I often get the feeling that delivery failures are *also* given in turbulent network conditions, which make retrying extremely cumbersome.

I'd really like to have such a robust delivery system such as Telegram and WhatsApp be in place in Element, where firing off a message on a good server (though a bad network), will have its delivery time not be an if, but a when. (Whenever the network allows it, keep retrying until it does.)

Contributor guide

Open the contributing guide

Research direction

Start by reading the linked Element Android issues 3837 and 2803 to understand the related discussion; this issue names no iOS files, tests, or entry points. The work would need a defined scope for retrying network-only delivery failures, with completion measured by reliable eventual delivery when connectivity returns.

Written by the indexing model from the issue text.

Assessment

Tech stack
swift
Domain
mobile
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.