ElementR: Unable to verify a user

[florianduros]

Steps to reproduce

Two rust crypto users

1. In a room, open the information panel of a user
2. Click on verify

Enregistrement.de.l.ecran.2023-09-27.a.11.54.56.mov

Outcome

What did you expect?

I'm expecting the verification process to be launched between the two users

What happened instead?

Nothing happen on the receiver side

Operating system

No response

Browser information

No response

URL for webapp

No response

Application version

No response

Homeserver

No response

Will you send logs?

Yes

[richvdh]

There is something wrong with the display of the verification events, which isn't helping:

[nao9797]

I have been having a problem perhaps similar or of the same type with verification functions for more than 2 years of using Element. I thought it was my android phone version, then later I noticed the problem was on my desktop element. I decided to wait at least a year since it seemed like an issue that would severely affect Element and what it's supposed to offer. I have been very idle about this issue, but I feel like now it has been way too long of an ongoing problem. I searched this in the issues and haven't seen a lot of relevant information (at least not in the open issues) and I have been wanting to make a new issue but I feel like it will take a long time to point out something that should have been pointed out long ago by many others. I will eventually do this but I can't help but wonder now if the devs are doing ok, maybe they've bumped into a major obstacle? iduno

[richvdh]

@nao9797 your issue sounds unrelated. We are replacing the crypto code in Element-Web (#21972), so it's possible your problem will be solved anyway, but feel free to open a separate issue explaining your symptoms.

[richvdh]

There is something wrong with the display of the verification events, which isn't helping:

Whilst this is true (it's due to the fact that we're not populating MatrixEvent.verificationRequest), it's not the root of the problem here, and is probably less of a blocker. Filed separately as part of #26258 for now.

The real problem is the absence of a CryptoEvent.VerificationRequestReceived when the event is received.