From 28b89b34441f4a3257c4bac8410433894fd47be8 Mon Sep 17 00:00:00 2001 From: Claude Date: Tue, 19 May 2026 21:51:49 +0000 Subject: [PATCH] fix: stop reporting transient WebSocket connect_error to Sentry connect_error fires on every retry attempt (e.g. iOS Safari dropping WebSocket during network transitions). Using logger.error routed each attempt to Sentry.captureException, generating noise for a self-healing failure. Switch to logger.log (no-op in production); the real failure path (reconnect_failed) still uses logger.error and surfaces in Sentry. https://claude.ai/code/session_01TpZ9W111Trkv2g4CkCWFpB --- app/hooks/useDraftSocket.ts | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/app/hooks/useDraftSocket.ts b/app/hooks/useDraftSocket.ts index 2813160..b4564db 100644 --- a/app/hooks/useDraftSocket.ts +++ b/app/hooks/useDraftSocket.ts @@ -64,7 +64,7 @@ export function useDraftSocket(seasonId: string, teamId?: string): UseDraftSocke }); socket.on("connect_error", (error) => { - logger.error("Socket.IO connection error:", error); + logger.log("Socket.IO connection error:", error); // Don't set connectionError here — reconnect_attempt fires immediately after // and would clear it again, causing the error overlay to flicker on every // retry. Only show a hard error once all attempts are exhausted (reconnect_failed).