-
-
Notifications
You must be signed in to change notification settings - Fork 2.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Encryption upgrade prompt doesn't lead anywhere #22893
Comments
I didn't event get this notification when the event occured!
|
Still happening to me on the latest version of Element. Element version: 1.11.43 |
Experiencing this on the current develop.element.io (since a few months ago) Element version: 9091c07-react-2e7668752fa5-js-9f1d0c389634 |
Same issue on latest element desktop |
Same issue on element desktop
|
If anyone can reproduce this, please do so and then send debug logs from within the application referencing this issue. |
Actually, this toast was removed in #28299, so I guess it's fixed. |
Steps to reproduce
Logging into desktop Element with new element.io identity
Some very limited usage, mostly DMs
Encryption upgrade available prompt pops up
![image](https://user-images.githubusercontent.com/640121/179771524-9feb77b3-3de8-48be-85cc-ae3d73f556d7.png)
Clicking on upgrade, it asks for my security key
![image](https://user-images.githubusercontent.com/640121/179771747-48bd33aa-f594-4569-ae1e-33dc1e079512.png)
Clicking on continue just brings me back to the original screen
![image](https://user-images.githubusercontent.com/640121/179771853-dafa871a-9ee8-4475-8541-ab7473383431.png)
Outcome
What did you expect?
I would have expected the client to do whatever it has to do and the initial prompt to disappear, potentially showing a brief confirmation message that all is good.
What happened instead?
I feel like in a loop and I cannot resolve this.
Operating system
Windows
Application version
Element version: 1.11.0, Olm version: 3.2.8
How did you install the app?
from element.io
Homeserver
element.io
Will you send logs?
Yes
The text was updated successfully, but these errors were encountered: