Unhandled file size limit when syncing camera roll
Nobody has claimed this yet.
- Dominant language
- Swift
- Stars
- 2.5k
- Forks
- 1k
- Avg merge
- 2d 18h
- Merged PRs (30d)
- 13
Description
How to use GitHub
- Please use the 👍 reaction to show that you are affected by the same issue.
- Please don't comment if you have no relevant information to add. It's just extra noise for everyone subscribed to this issue.
- Subscribe to receive notifications on status change and new comments.
Steps to reproduce
- Start sync of camera roll via iOS
- As soon as =>50MB (or 60MB, not sure) is attempted to upload the iOS app terminates.
- Upon restart of app, it terminates again after couple of seconds when upload is retried.
Expected behaviour
It shouldn‘t crash, handle error by reporting error or just skipping the file and report later.
Actual behaviour
When synching camera roll via iOS app: as soon as =>50MB (or 60, not sure) is attempted to upload the iOS app terminates.
Logs
no logs, sorry
Reasoning or why should it be changed/implemented?
Unhandled error, crash prevents people from synching there entire camera roll.
Environment data
iOS version: 26.1
Nextcloud iOS app version: 7.2.2.4?
Server operating system: not sure, managed instance from Hetzner
Web server: not sure
Database: not sure
PHP version: not sure
Nextcloud version: 31.0.10?
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 camera roll sync on iOS with a file around the reported 50–60 MB limit, then trace the upload error handling. Done means the app no longer terminates when the limit is encountered and instead reports the error or skips the file so syncing can continue.
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