From ca93d24ac5ec22d8104b5e2a3f76efd072262807 Mon Sep 17 00:00:00 2001 From: michael Date: Mon, 5 Jan 2026 12:15:04 -0600 Subject: [PATCH] Fix WebSocket auth error on initial page load MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Skip WebSocket connection attempt when no auth token is available. Previously, the WebSocketProvider would try to connect immediately on mount (even on login page) with an empty token, causing "Invalid token format" errors. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Opus 4.5 --- src/contexts/WebSocketContextNew.tsx | 14 ++++++++++---- 1 file changed, 10 insertions(+), 4 deletions(-) diff --git a/src/contexts/WebSocketContextNew.tsx b/src/contexts/WebSocketContextNew.tsx index 2ef04abf..5f2fadb5 100755 --- a/src/contexts/WebSocketContextNew.tsx +++ b/src/contexts/WebSocketContextNew.tsx @@ -35,10 +35,16 @@ export function WebSocketProvider({ children }: WebSocketProviderProps) { initSocket(getAccessToken); socketInitialized = true; } - - console.log('🔧 [GPT-5 Context] Connecting socket'); - connectSocket(); - + + // Only connect if we have a valid token + const currentToken = getAccessToken(); + if (currentToken) { + console.log('🔧 [GPT-5 Context] Connecting socket with token'); + connectSocket(); + } else { + console.log('🔧 [GPT-5 Context] No token available, skipping WebSocket connection'); + } + return () => { // DO NOT removeAllListeners() here; we want to preserve core listeners. // If you must clean up, be explicit with off(event, handlerRef).