Session verification problems #18386
Labels
A-E2EE
A-E2EE-SAS-Verification
O-Uncommon
Most users are unlikely to come across this or unexpected workflow
S-Major
Severely degrades major functionality or product features, with no satisfactory workaround
T-Defect
X-Needs-Investigation
Description
I have returned to Element after a 3.5 years break (we can say that I left Riot in favour of Element). I had big problems getting started which started with not being able to verify my sessions. (Side comment: "verify login" sounds like an account verification during registration and "Use another login" as an option to cross-verify sessions sounds like I should be using a different account, not perform an operation between two sessions).
Steps to reproduce
First login on phone, then in the web client, emoji verification
First login in the web client, then on phone, emoji verification
First login in the web client, then on phone, qr code verification
I was able to scan the code and the phone showed this:
I confirmed and received this on phone and the app:
I ended up (if I remember correctly I dare not trying to repeat it) going on the phone into settings, security, sessions management and was able to select verification by text which was one-sided and just worked.
If it helps, I have also had problems sending messages in a newly created conversation. I created it on the phone and couldn't send messages, then in the browser I could (and could see them on the phone), but when I logged out and back in in the browser all messages were encrypted. I could only send messages from the phone after I completed the verification.
Describe how what happens differs from what you expected.
I was expecting verification to work at first try.
Logs being sent: yes
Version information
In browser (and phone)
For the web app:
For the phone app:
1.1.15[40101152] (G-b2969) on Android 10 (Huawei BLA-L29)
The text was updated successfully, but these errors were encountered: