InstantUpload uploads removed pictures
Nobody has claimed this yet.
- Dominant language
- Swift
- Stars
- 2.5k
- Forks
- 1k
- Avg merge
- 2d 18h
- Merged PRs (30d)
- 13
Description
Steps to reproduce
- Configure InstantUpload to automatically send pictures on WiFi network.
- Take a picture, Nextcloud app notices it and add a pending transfer.
- Remove the picture from the photo app, transfer is still pending and Nextcloud app will upload the picture when WiFi becomes available.
Expected behaviour
I expect Nextcloud app InstantUpload feature with WiFi-only to have a behavior of "batch upload" whenever a WiFi becomes available. Therefore, if I remove a picture on the device before transfer happends, I expect the pending transfer to be removed from the queue.
Actual behaviour
The photo is transferred even though it was deleted on device before transfer could occur.
Note that when a picture is deleted after transfer happens, it seems it is not removed from the Nextcloud server either.
Screenshots
Available upon request.
Logs
Available upon request.
Reasoning or why should it be changed/implemented?
Environment data
iOS 17.1.2
Nextcloud iOS app version: Nextcloud Liquid for iOS 4.9.2.20
Server operating system: Debian
Web server: nginx
Database: sqlite
PHP version: 7.4
Nextcloud version: 25.0.13
Thanks!
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 InstantUpload flow with WiFi-only transfers: queue a picture, delete it from the photo app before WiFi is available, and observe the pending transfer. Trace how pending transfers react to local deletion and how completed uploads relate to later deletion. Done means deleted local pictures are not uploaded from the queue, with the reported behavior verified for the Nextcloud iOS app.
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
- 38/100