fix: proactively refresh Supabase JWT before API calls #84

TheFurya · 2026-03-22T11:33:45+01:00

TheFurya commented

2026-03-22 11:33:45 +01:00

Summary

Proactively refresh the Supabase JWT token before making API calls to prevent intermittent 401 errors caused by expired tokens
Update the API client to check token freshness and refresh when nearing expiry
Close out several false-positive crash/bug beans related to MFA and admin page ownership

Test plan

Verify API calls no longer produce intermittent 401 errors during long sessions
Confirm token refresh happens transparently without user interaction
Check that save/load operations work reliably without requiring re-login

🤖 Generated with Claude Code

## Summary - Proactively refresh the Supabase JWT token before making API calls to prevent intermittent 401 errors caused by expired tokens - Update the API client to check token freshness and refresh when nearing expiry - Close out several false-positive crash/bug beans related to MFA and admin page ownership ## Test plan - [ ] Verify API calls no longer produce intermittent 401 errors during long sessions - [ ] Confirm token refresh happens transparently without user interaction - [ ] Check that save/load operations work reliably without requiring re-login 🤖 Generated with [Claude Code](https://claude.com/claude-code)

TheFurya added 7 commits 2026-03-22 11:33:46 +01:00

fix: proactively refresh Supabase JWT before API calls 22dd569b75

Adds token expiry checking and automatic refresh to prevent intermittent
401 errors when the cached session token expires between interactions.

- Check token expiry (60s buffer) before each API call
- Add 401 interceptor that retries once with refreshed token
- Explicitly enable autoRefreshToken in Supabase client

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

chore: mark bean nuzlocke-tracker-tatg as completed c21d33ad65

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

chore: mark bean nuzlocke-tracker-i2va as completed 118dbcafd9

Work was already committed (3bd24fc) and merged to develop.
Crash recovery bean nuzlocke-tracker-ks9c also resolved.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

chore: mark MFA beans as completed 891c1f6757

Crash recovery for nuzlocke-tracker-f2hs: MFA feature was already
implemented and merged via PR #76. Verified code, tests pass.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

chore: mark owner info in admin pages beans as completed 4ca5f9263c

The implementation was already complete and merged - just needed
the beans marked as done after agent crash.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

chore: close false-positive crash bean nuzlocke-tracker-26my fd2020ce50

Original bean (nuzlocke-tracker-2fp1) was already completed.
Commit a3f332f merged via PR #74.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

chore: scrap false-positive crash bean nuzlocke-tracker-9rm8

CI / backend-tests (pull_request) Successful in 30s

Details

CI / frontend-tests (pull_request) Successful in 28s

Details

80d5d01993

MFA feature was already completed and merged via PR #76.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

TheFurya merged commit d1ede63256 into develop

2026-03-22 11:35:34 +01:00

TheFurya deleted branch feature/fix-intermittent-401-errors

2026-03-22 11:35:35 +01:00

TheFurya referenced this issue from a commit

2026-03-22 11:35:38 +01:00

Merge pull request 'fix: proactively refresh Supabase JWT before API calls' (#84) from feature/fix-intermittent-401-errors into develop

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: pokemon/nuzlocke-tracker#84