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
The cellular network was overloaded at the Glacier Peak Event -- enough signal bars but very poor data throughput. [In the event survey, I suggested that FIRST ask the cellular providers to set up COWS (Cell sites On Wheels) for all FRC events. Let's suggest this early and often.]
People can understand not getting updates, but the app displayed content regressions such as:
Go back to the event's Teams screen and see an empty list or a short list of teams. When it can't fetch new data, why does it lose earlier data? If a network response gets cut short, doesn't the HTTP library indicate that?
Go back to the event's Rankings screen and see smaller W-L-T counts than earlier. I took this screenshot after Quarter Finals when it claimed the top qual scores as (1-0-0)!
The text was updated successfully, but these errors were encountered:
I saw this issue today as well. I was able to replicate it once on purpose but then the next time around it only was partially replicated.
My process:
Viewed a regionals rankings at some point in the day
Viewed same regionals rankings later to see the updates
Turned off mobile data (to try to save battery) then turned the screen off/put the phone to sleep.
When I turned on the screen the rankings had reverted back to the old data I saw earlier in the day.
When I turned mobile data back on and reloaded I had the correct rankings. Note: Network/UI bug #828 is still present so you must reload from the list of events page instead of the single event/event breakdown page (atleast that was my experience).
I was able to repeat these steps for the full effect one other time. Sadly, on the third time, the error didn't appear the same - I was still able to see the old rankings blip up but then they got replaced with the new ones immediately.
The cellular network was overloaded at the Glacier Peak Event -- enough signal bars but very poor data throughput. [In the event survey, I suggested that FIRST ask the cellular providers to set up COWS (Cell sites On Wheels) for all FRC events. Let's suggest this early and often.]
People can understand not getting updates, but the app displayed content regressions such as:
(1-0-0)
!The text was updated successfully, but these errors were encountered: