You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The invite QR encodes the invite link (so a plain camera app lands on the web join page), but the scanner was dropping those raw contents straight into the join field. POST /households/join matches join_code exactly, so the app was sending:
which 404s — the "could not be found" error in your screenshot. parseJoinCode (c5d66a4) now lifts the bare code out of a scan, a pasted link or a typed code before it reaches the API, and the same flow reaches "Joined successfully!". A regression test covering the request body is in #37.
⚠️This is not on your phone yet. The fix is on main, but you're on v0.1.6 and the next build hasn't gone out — sharing a household by QR will still fail until it does. I'll ping you when there's a build to install.
Activity
fix(join): lift the join code out of a scanned invite link
spdotdev commentedon Jul 12, 2026
Fixed — verified on a Pixel 7 Pro.
The invite QR encodes the invite link (so a plain camera app lands on the web join page), but the scanner was dropping those raw contents straight into the join field.
POST /households/joinmatchesjoin_codeexactly, so the app was sending:{"code":"https://inventory.scuttle.dev/join/ABCD-2345"}which 404s — the "could not be found" error in your screenshot.
parseJoinCode(c5d66a4) now lifts the bare code out of a scan, a pasted link or a typed code before it reaches the API, and the same flow reaches "Joined successfully!". A regression test covering the request body is in #37.main, but you're on v0.1.6 and the next build hasn't gone out — sharing a household by QR will still fail until it does. I'll ping you when there's a build to install.Cover the invite-link join path at the network boundary (#30)