Sometimes the app will launch with an infinite spinner
This is something that does not happen all the time, but once it happens it seems to occur every time.
We should investigate when this happens to find the reason.
Theories to test
-
This happens when we don't get a response from the server/when we wait to long for the response. Tested with mitmproxy, it can happen even if we have a quick response. - This happens sometimes when we don't get new info from the server we care about. The last time it occurred to me, with mitmproxy, the first sync only had new ephemeral data. It usually happens after I've already launched the app a few times recently.
- The consequences of this should be minimized with #831, as the user will at least be able to see its old room history.
- The client becomes unresponsive, so it may be an upstream issue. This has been tested with !876 (closed) by checking if we get anything from the client's sync stream. Also, it seems impossible to do anything that requires the client to load data, like we're offline.
To solve this temporarily
A solution that works every time is to force the app to re-login. To do that you need to erase the two passwords under the name Fractal
(with the capitalized f
, without it would be the password for stable fractal) in your secret service provider.
In a regular GNOME install you can find this in the login
keyring in Passwords and Keys (seahorse).
Edited by Kévin Commaille