upgrading to v1.11.0 invalidates session
See original GitHub issueSteps to reproduce
- Have existing installation and signed in profile of electron-desktop v1.10.15.
- Install v1.11.0
- Start element-desktop
Outcome
What did you expect?
element-desktop starts and shows a signed-in view with rooms just as on v1.10.15.
What happened instead?
The following modal is displayed with a “Sign out” button being the only actionable:
Missing session data
Some session data, including encrypted message keys, is missing. Sign out and sign in to fix this, restoring keys from backup.
Your browser likely removed this data when running low on disk space. To help us prevent this in future, please send us logs.
Operating system
Linux (NixOS)
Application version
1.11.0
How did you install the app?
No response
Homeserver
No response
Will you send logs?
No
Issue Analytics
- State:
- Created a year ago
- Comments:5 (5 by maintainers)
Top Results From Across the Web
Invalid session problems & login link not available · Issue #7050
Running 1.11.0 on MongoDB with a 14 day session. It's hard to reproduce this but every since the upgrade to 1.11.0 I've noticed...
Read more >Upgrading Specific Versions | Consul - HashiCorp Developer
Consul 1.7.0 introduced a backwards incompatible change to the Session API. Queries to view or renew sessions from agents on earlier versions will...
Read more >VMware vCenter Server 7.0 Update 3f Release Notes
The upgrade considers the STS certificate invalid and the pre-checks prevent the upgrade process from continuing.
Read more >1.11.0+ Upgrade Notice :: Gloo Edge Docs
Review the changes in Gloo Edge 1.11.x and Gloo Edge Enterprise 1.11.x, and apply the version-specific changes before upgrading your Gloo Edge installation....
Read more >API upgrades | Stripe Documentation
A PaymentIntent is no longer created during Checkout Session creation in payment mode. Instead, a PaymentIntent will be created when the Session is...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
this isn’t a regression.
If your disk was nearly full then browsers, including desktop, tend to purge data we ask it to store, unhelpfully.
Considering a duplicate of one of these issues:
Potentially related issue: #18625
No flatpak here - running unsandboxed.
This happened simultaneously on two simultaneously running instances from the same installation of Element (separate profiles so should not be a cause of conflict there) but a third one on the same host, which was not running at the time that this got triggered, was unaffected.
I have no reason to believe that this occurred due do concurrently running processes attempted to modify the same file for both of these at the same time.