Utility.Networking.WebSocketException: Exception of type 'Utility.Networking.WebSocketException' was thrown.

[sentry]

Sentry Issue: UNITY-EXPLORER-QB3

Utility.Networking.WebSocketException: Exception of type 'Utility.Networking.WebSocketException' was thrown.
  File "C:/workspace/workspace/p/Explorer/Assets/DCL/Infrastructure/Utility/Networking/DCLWebSocket.cs", line 123, in ConnectAsync
  File "C:/workspace/workspace/p/Explorer/Assets/DCL/Infrastructure/CrdtEcsBridge/JsModulesImplementation/ClientWebSocketApiImplementation.cs", line 59, in ConnectAsync
  File "C:/workspace/workspace/p/Explorer/Assets/DCL/Infrastructure/Utility/Networking/DCLWebSocket.cs", line 123, in ConnectAsync
  File "SceneRunner.Scene.cpp", line 10250, in ReportAndRethrowExceptionAsync
  File "SceneRuntime__1.cpp", line 7126, in ConnectAsync
...
(74 additional frame(s) were not displayed)

This issue was automatically created by Sentry via Explorer Alpha Github Issue Creation

[github-actions]

This is a duplicate of #10103 - Scene websocket connect failures reach Sentry as anonymous WebSocketException (UNITY-EXPLORER-Q0A).

The root cause and proposed fix are documented in #10103. All WebSocketException issues with the generic title are duplicates of this root issue and should be consolidated there for tracking.

Please follow #10103 for updates on this issue.

[github-actions]

Automated Triage

Issue type	bug
Affected area	Networking / WebSocket connectivity
Feature category	Primary
Severity	SEV-2 → 1-high

Reasoning: WebSocketException during ConnectAsync is a crash in core networking infrastructure (Primary category: Stability & Crashes). The stack trace shows repeated connection failures in DCLWebSocket.cs, which affects users' ability to connect to the platform. Multiple Sentry instances indicate this affects some users while the platform remains partially functional for others, meeting SEV-2 criteria.

Labels applied: bug, 1-high, web-requests

---

Auto-triaged. If labels are incorrect, update issue triage categories or severity policy and re-run triage.

[github-actions]

Automated Triage

Issue type	bug
Affected area	WebSocket networking / CRDT bridge
Feature category	Primary — Stability & Crashes
Severity	SEV-2 → 1-high

Reasoning: This is a WebSocketException in the core DCLWebSocket connection path (DCLWebSocket.cs:123), which is part of the CRDT/ECS bridge infrastructure. WebSocket failures prevent entity state synchronization and scene interaction, making this a Primary category crash affecting some users. The issue is marked as a duplicate, so this should be consolidated with the original report for resolution tracking.

Labels applied: bug, 1-high, web-requests, duplicate, sentry (already present — no changes needed)

---

Auto-triaged. If labels are incorrect, update issue triage categories or severity policy and re-run triage.