Fix Garmin token connection not persisting after save
All checks were successful
Deploy / deploy (push) Successful in 1m38s
All checks were successful
Deploy / deploy (push) Successful in 1m38s
Root cause: The setup-db script was missing user field definitions (garminConnected, tokens, etc.). Production PocketBase had no such fields, so updates silently failed to persist. Changes: - Add user custom fields to setup-db.ts (matches e2e harness) - Fix status route to use strict boolean check (=== true) - Add verification in tokens route with helpful error message - Add ENCRYPTION_KEY to playwright config for e2e tests - Add comprehensive e2e tests for Garmin connection flow Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
This commit is contained in:
@@ -54,6 +54,8 @@ export default defineConfig({
|
||||
// Use the test PocketBase instance (port 8091)
|
||||
NEXT_PUBLIC_POCKETBASE_URL: "http://127.0.0.1:8091",
|
||||
POCKETBASE_URL: "http://127.0.0.1:8091",
|
||||
// Required for Garmin token encryption
|
||||
ENCRYPTION_KEY: "e2e-test-encryption-key-32chars",
|
||||
},
|
||||
},
|
||||
});
|
||||
|
||||
Reference in New Issue
Block a user