Server-side label QR fallback builds a scheme-less URL and uses the legacy /s/ route for new 6-char codes #442

Closed
opened 2026-08-21 21:13:26 +00:00 by gambit-admin · 0 comments
Owner

Found while investigating the COTH Dwebble no-QR label (2026-08-21). When a queued label payload has no qr_url, the server backfills one from the rcn (backend/app/routes/external_scan.py:~8886-8900) — but it builds it from prod LABEL_QR_BASE_URL as 'www.rungambit.com/s/...' with NO scheme (some QR scanners won't open it), and it always uses the legacy /s/ short route even for new 6-char codes, which should print as gmbt.app/g/ (PR #89 format). Fix: prepend https://, route 6-char codes to /g/, and prefer the gmbt.app short domain to keep the QR small.


Filed from a Claude Code session

Found while investigating the COTH Dwebble no-QR label (2026-08-21). When a queued label payload has no qr_url, the server backfills one from the rcn (backend/app/routes/external_scan.py:~8886-8900) — but it builds it from prod LABEL_QR_BASE_URL as 'www.rungambit.com/s/...' with NO scheme (some QR scanners won't open it), and it always uses the legacy /s/ short route even for new 6-char codes, which should print as gmbt.app/g/<code> (PR #89 format). Fix: prepend https://, route 6-char codes to /g/, and prefer the gmbt.app short domain to keep the QR small. --- Filed from a Claude Code session
gambit-admin added the bugapi labels 2026-08-21 21:13:26 +00:00
Sign in to join this conversation.