Improving background sync (download)
Nobody has claimed this yet.
- Dominant language
- Swift
- Stars
- 2.5k
- Forks
- 1k
- Avg merge
- 2d 18h
- Merged PRs (30d)
- 13
Description
I found similar issues that were closed but are still unsolved AFAIK:
Steps to reproduce
This is just an example. Different usage scenarios are possible.
- Mark a large file (e.g. >2GB) as available offline.
- Wait for transfer to be e.g. at 50%.
- Switch to another app.
- Switch back to nextcloud.
- Download restart from 0%.
- Profit!
Expected behaviour
Two possible outcomes:
- Download should resume from 50%.
- Download should be run in the background.
Actual behaviour
- Download is restarted from scratch.
Screenshots
If applicable, add a screenshot showing the issue.
Logs
If applicable, you can post the iOS app or server logs (removing any sensitive information).
Reasoning or why should it be changed/implemented?
Environment data
iOS version: e.g. iOS 14.4.1
16.5.1
Nextcloud iOS app version: see More > Settings
4.8.3.1
Server operating system:
Web server: Apache, nginx
Database:
PHP version:
Nextcloud version: see Nextcloud admin page
27.0.0
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
Start by reproducing the download interruption on iOS 16.5.1 with Nextcloud iOS 4.8.3.1, then trace the app's offline-download and background-transfer entry points. Done means a large offline download either resumes from its previous progress or continues in the background without restarting from zero.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ios, swift
- Domain
- mobile-dev
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100