Zombie upload jobs/file entries retained after upload if uploading via "Save to Files"
Nobody has claimed this yet.
- Dominant language
- Swift
- Stars
- 2.5k
- Forks
- 1k
- Avg merge
- 2d 18h
- Merged PRs (30d)
- 13
Description
Expected behaviour
When I select a photo or a video and save it in Nextcloud via "Save to Files" it shows up in the "Transfers" view and a dummy entry is added to the respective folder in the Nextcloud file browser. After the upload finishes, the transfer and the dummy entry disappear. The latter is replaced with the actual uploaded file.
Actual behaviour
The file I save shows up in the "Transfers" view and the dummy entry appears in the respective folder in Nextcloud. However, neither the dummy nor the transfer disappear after the upload has finished. The only way to clean things up is to check if the entry for the finished upload is shown next to the dummy and then press the "stop" button on the dummy entry. It will disappear, leaving only the uploaded file visible.
Additionally, the transfer stays listed in the Transfers view as long as the dummy entry exists. A side effect is that the number of dummy transfers is always shown as a red badge.
Steps to reproduce
- Select something (with non-negligible file size) and choose "Save to Files" in the iOS share sheet
- Choose Nextcloud as destination
- Switch to the Nextcloud app and navigate to the upload in progress in the file hierarchy
- Wait for the upload to finish
- The completed file is visible in the folder now, next to the dummy entry
Reasoning or why should it be changed/implemented?
The current behavior makes it very hard to tell if and when an upload succeeded.
iOS version
13.5.1
App version
3.0.1.18
Server configuration
Operating system: Arch Linux
Web server: Nginx
Database: MariaDB
PHP version: 7.4.7
Nextcloud version: 19.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 Save to Files flow from the listed steps and inspect the upload handling for Transfers and the dummy file entry. Confirm the behavior on upload completion, then verify that both the transfer and dummy entry are removed while the completed file remains.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ios, swift
- Domain
- mobile
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100