Description
When iOS device storage is full (or too low), Ente can fail during backup while fetching/caching originals from iCloud Photos or writing temporary encrypted upload files.
Today this appears to fail as generic upload/file errors and retries, but without a clear user-facing reason like “Device storage is full”.
This makes backup look stuck/indefinitely retrying and users don’t know they must free local space.
Steps to reproduce
- Use Ente Photos on iOS with iCloud Photos enabled.
- Keep device local storage nearly full.
- Start/continue backup of iCloud-backed assets.
- Observe backup progress (looping through assets fast) and no error surfacing other than retry / contact support button.
Actual behavior
- Individual uploads fail and are retried.
- Backup may remain in retry/error-ish state without clear diagnosis.
- No explicit notification/banner indicating local device storage is full.
Expected behavior
When backup fails due to local storage exhaustion (e.g. inability to materialize source file/cache or write temp encrypted files), Ente should:
- Detect and classify this as a local-disk-space error.
- Surface a clear message in backup status (and optionally push/local notification), e.g.:
- “Backup paused: device storage is full. Free up space and retry.”
- Avoid noisy blind retries until storage recovers (or retry with backoff + clear UX state).
- Optionally provide quick action/link to storage guidance.
Why this matters
For iOS + iCloud Photos flows, temporary local storage is required for backup. Without explicit handling, users cannot distinguish:
- network issues,
- cloud quota issues,
- local device storage exhaustion.
This increases support load and causes confusion about backup reliability.
Platform / product
- Product: Ente Photos
- Platform: iOS
- Area: Backup / Sync
Description
When iOS device storage is full (or too low), Ente can fail during backup while fetching/caching originals from iCloud Photos or writing temporary encrypted upload files.
Today this appears to fail as generic upload/file errors and retries, but without a clear user-facing reason like “Device storage is full”.
This makes backup look stuck/indefinitely retrying and users don’t know they must free local space.
Steps to reproduce
Actual behavior
Expected behavior
When backup fails due to local storage exhaustion (e.g. inability to materialize source file/cache or write temp encrypted files), Ente should:
Why this matters
For iOS + iCloud Photos flows, temporary local storage is required for backup. Without explicit handling, users cannot distinguish:
This increases support load and causes confusion about backup reliability.
Platform / product