Uploading of iCloud corrupted photo causes photo auto-upload to halt.
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
- Somehow get an icloud corrupted photo in your photos app
- Setup nextcloud auto-upload
- Once Nextcloud tries to sync corrupted photo, all uploads halt and no error is shown or no way to continue
Expected behaviour
Ideally the user should be told that a file cannot be synced and the auto-upload should continue.
Actual behaviour
The auto-upload stops and no additional photos are uploaded. Trying to restart the auto upload results in the same error once the upload reaches the corrupted icloud photo.
Workaround
- Check last uploaded file via Nextcloud web interface.
- Find next file in ios Photos and delete (probably is corrupted).
- Return to Nextcloud app and download will continue after “file not found” error is displayed:
Screenshots
Corrupted photo in Photos app looks like:
Reasoning or why should it be changed/implemented?
This issue prevented me from switching to Nextcloud for months. Once I discovered the workaround, I'm really loving the app!
I would suspect that I'm not the only one out there that has these 'corrupted' icloud phots in my Photos app.
Environment data
** iOS Version ** iOS 15.1
Nextcloud iOS app version: 4.0.6.0
Server operating system: Ubuntu
Web server: Apache
Database: MySQL
Nextcloud version: 22.2.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 tracing the iOS app's photo auto-upload flow and reproduce the failure with an iCloud-corrupted photo. The fix should report that the file cannot be synced and continue uploading subsequent photos instead of halting; verify that restarting does not repeatedly stop at the same file.
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