Bug Editor/Hub get confused if network connection lost while logged in

Win 10 64-bit, Unity 2020.3.9f1, Hub 2.4.3

If the internet connection goes down then returns while the Hub is running (regardless of whether or not the editor is running), then the editor can't retrieve packages, and doesn't recognize the network connection:




Additionally, every action in the Editor's "account" menu is disabled, so there is no smooth way to recover.

Also, the Hub still thinks you are logged in, even though any network requests fail. The Editor does as well, as evidenced by UI state (e.g. the Package Manager window also throws exceptions without providing a recovery workflow, the Services configuration pane thinks the network itself is down and the Retry button there is a no-op, etc.).

The workaround is to close the Editor and then either restart the Hub or explicitly sign out in the Hub and log back in again, then restart the Editor.

This behavior appears to be consistent and repeatable.

Expected Behavior:

The following is what I expect to happen:

- Unity Hub is aware of connection loss and either prompts to sign back in when you open the Hub window, or at minimum does not act as if you are logged in.
- Unity Editor is aware of connection loss and either prompts to sign back in, or at minimum has "Sign In" enabled in the account menu.

The following is what actually happens:

- Hub and Editor UIs are inconsistent and misbehaved until you explicitly log out and back in.