Open sandervdwaal opened 3 years ago
Looks like your access token was invalidated, which means either you or your HS admin logged you out. However it should have told you this, but there was another error: I think when trying to remove the search index after the logout. I'll repurpose this bug to track that error.
So this could be a bug where the desktop app errors if its access token is invalidated while it isn't running (or maybe while it is, too)
I'm not sure if this is related, but it seems likely: I am suddenly unable to log into my existing Element Desktop session, and instead a new session is created at launch. This happens even after I've deleted the newly created session and rebooted. I have also updated to the latest version (1.7.32, olm 3.2.3). I have never logged into my account from any other device. Is there any way to regain access to the earlier session?
Looks like your access token was invalidated, which means either you or your HS admin logged you out. However it should have told you this
This is still intuitive because it means that any backup of the virtual machine in which I run Element Desktop will not suffice. I just restored a very recent backup (thinking that a backup of the entire VM would get my chat history back) but it shows the mentioned error message. My security key was not accepted. My security passphrase was accepted but I lost my entire chat history (without Element showing any further error message).
Description
Unable to restore session message
Steps to reproduce
If you have previously used a more recent version of Element, your session may be incompatible with this version. Close this window and return to the more recent version.
Clearing your browser's storage may fix the problem, but will sign you out and cause any encrypted chat history to become unreadable."
I have not knowingly set up a separate session elsewhere
Version information
For the desktop app: