mobile-files-media — Canonical Skill

Purpose

Enforce the verified file/media pipeline with platform-safe URI handling.

When to use

Camera capture, photo picking, chunked upload, download/open/share, save to gallery, permissions, scoped-storage/sandbox paths.

Required reading

• skills/mobile/FILES_MEDIA.md

Relevant project locations

• src/composables/useFileSystem.ts (active picker/save path), src/composables/useUpload.ts (active upload path)
• src/composables/useCamera.ts (currently no import callers)
• src/composables/useFileDownload.ts, src/utils/FileUtils.ts
• src/api/FileManagerService.ts

Mandatory rules

1. Camera: getPhoto Uri + webUseInput, pickImages. Web has no gallery: savePicture/saveFile fall back to a browser download.
2. Save pipeline: base64 → Filesystem.writeFile (Directory.Data) → Media.savePhoto into AppAlbumName album.
3. Upload defaults: 1 MB chunks, one attempt unless maxRetries is overridden; FormData uploadChunkApi then merge DTO mergeChunkApi. In-memory chunk tracking is not restart-safe resume.
4. Validate paths, MIME, filenames; respect scoped storage / sandbox; request minimal permissions with isWeb() guards.
5. Blob URLs from fethCdnData must be released: use useBlobUrls() (track + auto-revoke on unmount), as BaseImage/BaseAvatar do. Downloads that must land on the device use useFileDownload.

Implementation workflow

1. Trace the caller's capture/pick → convert → store/upload → cleanup chain; do not assume the unreferenced useCamera.ts is the active path.
2. Handle permission-denied, cancel, retry-exhausted, large-file paths.
3. Clean temp files; confirm user-visible export location.
4. Verify per mobile-testing, incl. SECURITY (untrusted files).

Verification

Mocked picker/upload unit tests; real capture/save/share only on device.