Transfers are not retried when they fail
Nobody has claimed this yet.
- Dominant language
- Swift
- Stars
- 2.5k
- Forks
- 1k
- Avg merge
- 2d 18h
- Merged PRs (30d)
- 13
Description
In an area where changing between networks happens often (LTE / Pocket Wi-Fi / other public Wi-Fi, possibly with walled garden login), Nextcloud transfers are unreliable.
I have a bunch of transfers that are stuck (forever?) with 2 different kinds of error:
- The certificate for this server is invalid
- Error code 100
Expected behaviour
Failed transfers are retried again later. If not automatically, then at least manually (by tapping on the transfer).
Actual behaviour
When a transfer fails, it's not retried at all and remains in an error state forever.
Steps to reproduce
Unknown.
iOS version
iOS 12.1
App version
Nextcloud for iOS 2.22.7.4
Server configuration
Operating system: CentOS 7.5
Database: PostgreSQL 11.1
Nextcloud version: 15.0.0 running within the official Nextcloud Apache image.
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 source files, tests, or entry points are identified. Start by reproducing a transfer failure while switching between LTE and Wi-Fi, then trace how certificate and error-code-100 failures enter the permanent error state. Done means failed transfers are retried later or can be restarted by tapping them.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- swift
- Domain
- mobile-dev
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 28/100