Implement ReceiptStorageRepository for Supabase Storage
epic-receipt-capture-and-attachment-core-logic-task-002 — Build the ReceiptStorageRepository to handle binary image upload and retrieval against Supabase Storage buckets. Implement uploadReceiptImage(), getSignedUrl(), and deleteReceiptImage() with streaming progress callbacks, retry logic on network failure, and bucket-level RLS configuration for secure access.
Acceptance Criteria
Technical Requirements
Execution Context
Tier 1 - 540 tasks
Can start after Tier 0 completes
Implementation Notes
The Supabase Dart client's storage upload does not natively stream progress — implement progress by splitting large files into chunks using Uint8List.sublist() and uploading via multipart, or use the uploadBinary method with a custom HttpClient wrapper that intercepts sent bytes. A simpler approach for the initial implementation: use the standard upload call and emit progress as 0.0 (start) and 1.0 (complete) only, with a TODO comment for streaming progress in a future iteration. For MIME type magic byte detection: JPEG starts with bytes [0xFF, 0xD8, 0xFF]; PNG starts with [0x89, 0x50, 0x4E, 0x47]. Implement a private _detectMimeType(Uint8List bytes) method checking the first 4 bytes.
For retry logic, implement a generic _withRetry
Testing Requirements
Write unit tests with a MockSupabaseStorageClient using mocktail: (1) uploadReceiptImage triggers onProgress callbacks at expected intervals and returns the storage path, (2) uploadReceiptImage throws ValidationException for files > 10MB without making a network call, (3) uploadReceiptImage throws ValidationException for non-image MIME types, (4) getSignedUrl returns a URL string on success and throws ReceiptStorageException on storage 404, (5) deleteReceiptImage does not throw when the file is absent (idempotent), (6) retry logic: mock the upload to throw SocketException twice then succeed on third attempt; assert the method returns successfully and the progress callback was called. Write one integration test against a local Supabase storage instance verifying end-to-end upload + signed URL retrieval.
Non-blocking upload creates a race condition: if the claim record is submitted and saved before the upload completes, the storage path may never be written to the claim_receipts table, leaving the claim with a missing receipt that was nonetheless required.
Mitigation & Contingency
Mitigation: Design the attachment service to queue a completion callback that writes the storage path to the claim record upon upload completion, even after the claim form has submitted. Use a local task queue with persistence to survive app backgrounding. Test the race condition explicitly with simulated slow uploads.
Contingency: If the async path association proves unreliable, fall back to blocking upload before claim submission with a clear progress indicator, accepting the UX trade-off in exchange for data integrity.
The offline capture requirement (cache locally, sync when connected) significantly increases state management complexity. If the offline queue is not durable, receipts captured without connectivity may be lost when the app is killed, causing claim submission failures users are not aware of.
Mitigation & Contingency
Mitigation: Persist the offline upload queue to local storage (e.g., Hive or SQLite) on every state transition. Implement background sync using WorkManager (Android) and BGTaskScheduler (iOS). Scope the initial delivery to online-only flow if offline sync cannot be adequately tested before release.
Contingency: Ship without offline support in the first release, displaying a clear 'Upload requires connection' message. Add offline sync as a follow-on task once the core online flow is validated in production.
The inline bottom sheet presentation within a multi-step wizard can conflict with existing modal navigation and back-button handling, particularly if the expense wizard itself uses nested navigation or custom route management.
Mitigation & Contingency
Mitigation: Review the expense wizard navigation architecture before implementation. Use showModalBottomSheet with barrier dismissal disabled to prevent accidental dismissal. Coordinate with the expense wizard team on modal stacking behavior and ensure the camera sheet does not interfere with wizard step transitions.
Contingency: If modal stacking causes navigation issues, present the camera sheet as a full-screen dialog using PageRouteBuilder with a transparent barrier, preserving wizard state via the existing Bloc while still appearing inline.