Active Bug
Springs vs Springs Pro Issue
Gallery Creator shows all photos under Springs and zero under Springs Pro. Root cause, three contributing factors, and two solution options with pros/cons.
Covers
- Location name collision (
resolveAppDisplayLocation) - Why the existing override wasn't triggered
- The
LIKE '%/Springs%'query bug - Option A: shared pool · Option B: own folder (recommended)
- Secondary LIKE pattern fix
Read the bug doc
Architecture
Gallery Photo Pipeline
End-to-end flow from DSLR upload through Lambda processing, gallery album assignment, manifest generation, and CampLife app delivery.
Covers
- S3 inbox bucket structure and SQS triggering
- Rekognition face detection & camper matching
- Gallery album status lifecycle
- camplife-bridge-api delivery endpoints
- Springs vs Springs Pro stage-by-stage comparison
Read the pipeline doc
Current Status
As of 2026-05-14, Jesse reported the Springs Pro gallery issue. Here's where things stand:
-
✓Code override already written
gallery-folder-generator.ts:169correctly setslocationName = 'Springs Pro'— no code change needed for the fix. -
!Springs Pro Final Destination folder never provisionedThe folder-creation endpoint was never called for Springs Pro sessions. Photos are landing in the Springs S3 folder.
-
~LIKE query over-matches
LIKE '%/Springs%'matches Springs Pro paths too. Tighten toLIKE '%/Springs/%'after provisioning.