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 |
||
|---|---|---|
| .. | ||
| __tests__ | ||
| useDraftAuthRecovery.ts | ||
| useDraftNotifications.ts | ||
| useDraftRoomState.ts | ||
| useDraftSocket.ts | ||
| useDraftSocketEvents.ts | ||
| useFocusTrap.ts | ||
| useLocalTimezone.ts | ||
| useMediaQuery.ts | ||
| useRoundTransition.ts | ||
| useSortableData.ts | ||