You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
I keep having a disconnected error pop up on my
To Reproduce
Steps to reproduce the behavior:
Start up FTCLive Scorekeeping Software
Open up either the localhost that opens automatically or use the ip address connection provided
Attempt to open any of the display pages or the match control page and see a Disconnected! error
Expected behavior
The Disconnected banners should not be showing up on these pages, this is preventing the intended behavior of the pages updating live with the most current event statuses, I currently need to manually reload the pages for them to update for certain events such as a match starting, a match being aborted, entering or leaving test mode, or triggering some of the different audience screens
Screenshots
Device (please complete the following information):
OS: MacOS 15.3 Beta
Browser : Arc(which is Chromium based) and Google Chrome
Version : Scoring System v6.4.5
Additional context
One thing that I noticed that might be helpful in trying to figure out the source of this bug is an error that has popped up in my console multiple times regarding a WebSocket error
The text was updated successfully, but these errors were encountered:
Describe the bug
I keep having a disconnected error pop up on my
To Reproduce
Steps to reproduce the behavior:
Expected behavior
The Disconnected banners should not be showing up on these pages, this is preventing the intended behavior of the pages updating live with the most current event statuses, I currently need to manually reload the pages for them to update for certain events such as a match starting, a match being aborted, entering or leaving test mode, or triggering some of the different audience screens
Screenshots
Device (please complete the following information):
Additional context
One thing that I noticed that might be helpful in trying to figure out the source of this bug is an error that has popped up in my console multiple times regarding a WebSocket error
The text was updated successfully, but these errors were encountered: