This repository has been archived by the owner on Mar 1, 2024. It is now read-only.
Make the Websocket disconnect: 1006 error more informative for end users #184
Labels
Comments
|
Issues go stale after 30 days of inactivity. Please comment or re-open the issue if you are still interested in getting this issue fixed. |
alien299
added a commit
to alien299/PixelStreamingInfrastructure
that referenced
this issue
Nov 28, 2023
Fixed an Issue regarding the Websocket disconnect error messages. I made them more informative so they can assist with debugging. [Issue EpicGames#184](EpicGames#184)
6 tasks
alien299
added a commit
to alien299/PixelStreamingInfrastructure
that referenced
this issue
Nov 30, 2023
Fixed an Issue regarding the Websocket disconnect error messages. I made them more informative so they can assist with debugging. [Issue EpicGames#184](EpicGames#184)
wizard0918
pushed a commit
to wizard0918/Epic-Games-PixelStreamingInfrastructure
that referenced
this issue
Apr 23, 2024
Update cirrus.js - More informative error messages - Fixes EpicGames/PixelStreamingInfrastructure#184
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Component your feature request relates to
Problem your feature solves? Please describe.
Currently, all websocket disconnects are presented with the same "Websocket disconnected: 1006" error (see screenshot). This is a generic error, but not overly useful to assist with debugging whether UE disconnected or the browser disconnected.
Describe the solution you'd like
Ideally, rather than a catch all disconnect message, a user would be able to see which component has disconnected: e.g. UE disconnected, Signalling Server disconnected, Browser disconnected etc.
Additional context
The text was updated successfully, but these errors were encountered: