macOS/iOS 18 file size limits
- Dominant language
- Python
- Stars
- 5.4k
- Forks
- 850
- Avg merge
- 4d 5h
- Merged PRs (30d)
- 10
Description
## ❓Question
### Expected behavior when processing files exceeding platform size limits (1GB iOS, 2GB macOS)?
I've encountered an issue where files exceeding the platform size limits (1GB on iOS 18, 2GB on macOS) can still be exported and processed, but the resulting output doesn't work properly.
**Current behavior:**
- Files larger than the limits can be exported without errors
- Computation/processing appears to complete successfully
- The resulting output is non-functional
**Question:**
Is this the expected behavior? Should the system:
a) Block these operations entirely when files exceed size limits, or
b) Allow processing but produce invalid results?
**Platform details:**
- iOS 18: 1GB file size limit
- macOS: 2GB file size limit
I'd appreciate clarification on whether this is intentional design or if operations should fail earlier with appropriate error messages.
Contributor guide
Research direction
The issue names no files, tests, or entry points. Start by reproducing the export and processing behavior with files over the stated iOS and macOS limits, then determine the intended failure behavior; done should include a clear decision and appropriate handling or documentation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ios, macos
- Domain
- desktop-dev, machine-learning, mobile-dev
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100