-
-
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
Verification not possible on newly logged in windows desktop session #27056
Comments
I wouldn't be surprised if this is somehow related to the rust sdk rollout on new logins... |
Please send logs. |
Logs should have just arrived from my colleague. It now somehow shows up as verified, but a different session shows up as unverified which we now removed. |
So any progress on this problem? Still experiencing this.. :( |
Same problem here. I am unable to verify my pc session. I have tried with multiple web browsers and desktop app. Also, I have tried with different security keys, where the verification process ends successfully but my pc session remains unverified :(. I can see messages from my desktop but cannot send a single message 🙃 Any workaround here? Thanks in advance. |
yes i found a solution, just use this client instead https://schildi.chat/desktop/ |
Thanks! That worked |
This is still a problem, any updates. Trying to roll this out to a new org. Using the security key to verify won't display "looks good" until one uploads twice, and even then after pressing "Continue" the "Verify this session" pop-up/dialog remains. |
Forget about it buddy. They were part of a diddy freak off and now in the middle of lawsuit so aint nobody got time for that... use cinny or schildi app |
What does that even mean? |
Steps to reproduce
Outcome
What did you expect?
verification to work
What happened instead?
various error messages resulting in an unverified session
Operating system
Windows
Application version
Element version 1.11.58
How did you install the app?
No response
Homeserver
No response
Will you send logs?
Yes
The text was updated successfully, but these errors were encountered: