Sorry everyone, been a busy Fall over here (or Spring, for those southern hemispherites).
Looking back at the only set of logs I see (logs >> begging), I see this:
The app will display the Downloads tab only when it thinks it’s offline (which makes sense, right?) However, it looks like it only spent a couple of seconds in this state.
Looking at the home screen, it looks like it reloaded as well in the timeframe:
Sep 30, 2024 12:58:15.984 [Javascript] INFO - Discovery: Are we offline? 0 hubs, network is 0 => offline: true.
Sep 30, 2024 12:59:15.710 [Javascript] INFO - Discovery: Are we offline? 10 hubs, network is 0 => offline: true.
Looking at the car logs shows an issue:
Sep 30, 2024 12:58:15.902 [Javascript] INFO - Car: Going offline for loss of network.
Sep 30, 2024 13:00:33.648 [Javascript] INFO - Car: We have network now, and home screen loaded.
It loses network at the same time as everything else, but doesn’t appear to regain it until a few minutes laster. This part of the app looks at a debounced network state (to avoid glitching), and it appears that this is the root cause of the issue:
Sep 30, 2024 12:58:15.901 [Javascript] INFO - App: Debounced network type changed to, 0
Sep 30, 2024 13:00:33.633 [Javascript] INFO - App: Debounced network type changed to, 1
The issue is that we’re using the normal system timers to do the debounce, and not the special native ones we created. The system timers don’t work with the app in the background.
Thanks for coming to my TED Talk, this will be fixed in the next release.
