You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
First of all, before emoji verification, I did manual verification matrix-commander-rs --bootstrap --verify manual -d.
Then try emoji verification again, I could verify between 2 accounts. One account on Element on cell phone who initiates the verification. Second account on the matrix-commander-rs CLI running the --verify option. I started the matrix-commander-rs --verify first to sit waiting, then the cell phone did the "request verification".
I could also do it between the matrix-commander-rs CLI and Element on a web browser. Here I tested two different devices of the same user.
In short, I could get both Element website as well as Element app on cell phone working for me.
In version v0.5.0 I added outgoing requests, i.e. matrix-commander-rs send a request (on invitation) to verify to another client (e.g. Element). This seems to work on Element webpage in browser. But this definitely does not work for me on Element app on Android.
Matrix has changed the spec for verification and also the implementation of verification in Element. So, some things that used to work no longer work. Also some things work in Element webpage, but not in Element phone app. Things are different in different implementations.
Not sure if there is a bug in Element phone app or in matrix-commander-rs. matrix-commander-rs does not receive any event from phone after user accepts the verification in the verification popup.
When I start
matrix-commander-rs --verify
and then click verification in the Elements app, nothing happens.Might this be the result of Elements using in-room-verification instead of device verification?
The text was updated successfully, but these errors were encountered: