As of 2024-12-09, I am still getting this error but after messing around a bit, I think I may have found a workaround.
Workaround
It seems like you cannot login when you get the error. This time I decided to click on the chat. Nothing loads but now the usual profile icon shows and a banner to login also shows. If the banner doesn't show, the profile options should have the option to sign in.
After signing in, some things may load. For me, it loaded three or four of maybe eighty or hundred of chats I should have. The profile icon doesn't show nor does the status.
As with the prior login issue, reloading the application after signing in with the issues will then finally load properly.
At least, I can use the app in the morning now. I am not sure why waiting several hours will also reach the same state.
Possible Alternate Workaround
May be able to skip a step above by trying to sign in before closing the app if the option is available. Also closing the app before calling it a day seems to also bypass the issue.
Now that I am writing this alternate workaround, I think there is a possibility that the issue may be with the login token not expiring properly. To make a guess, it may be that it is reusing the token that expires in 24 hours. The reason I have to wait for it open again is that I am waiting for the 24 hours to expire. Closing the app probably removes that token properly. Signing in also kind of removes the token but the app still may be continuing to load so therefor only loading parts of the configurations. And for some reason, closing the app after getting the error does not remove the token properly.
No comments:
Post a Comment