Question: How to verify matrix-commander: other client is waiting for "accept request"

[HoboDev]

OS: Linux
Matrix Commander Version: 3.5.0
Server: dendrite 0.9.8
Other Clients: Element 1.11.3 and nheko 0.10.0

Problem:
After matrix-commander is logged in successfully I can not complete the verification process.
Verification is started by matrix-commander and on either Element or nheko when I press verify
matrix-commander does not react. The process also seems to slightly deviate from the description in help
since I can not start emoji verification directly from the client.
Element and nheko can verify each other just fine.
Also I can not send any messages with matrix-commander but I guess this is because it's not verified.
(I can send messages after I joined a room)

Debug output (ids, user and domain redacted):

>matrix-commander --verify "emoji" --debug

2022-09-15 13:11:28,339:    DEBUG: matrix-commander: Debug is turned on. debug count=1
2022-09-15 13:11:28,340:    DEBUG: matrix-commander: Separator is set to "    " of length 4. E.g. Col1    Col2.
2022-09-15 13:11:28,340:    DEBUG: matrix-commander: Encryption is always enabled. It cannot be turned off.
2022-09-15 13:11:28,340:    DEBUG: matrix-commander: All arguments are valid. All checks passed.
2022-09-15 13:11:28,340:    DEBUG: matrix-commander: Trying to create a PID file to store process id 12345.
2022-09-15 13:11:28,340:    DEBUG: matrix-commander: Successfully created PID file "/home/username/.run/matrix-commander.00000000-0000-0000-0000-000000000000.pid" to store process id 12345.
2022-09-15 13:11:28,340:    DEBUG: matrix-commander: Stdin pipe is assigned to "none".
2022-09-15 13:11:28,340:    DEBUG: matrix-commander: SSL will be used. Default SSL certificate validation will be done for this connection.
2022-09-15 13:11:28,340:    DEBUG: matrix-commander: Credentials file existed. So this is the one we suggest to use. file: credentials.json
2022-09-15 13:11:28,340:    DEBUG: matrix-commander: Found an existing store in directory "store" (local or arguments). It will be used.
2022-09-15 13:11:28,350:    DEBUG: matrix-commander: Logged in using stored credentials from credentials file "credentials.json".
2022-09-15 13:11:28,361:    DEBUG: matrix-commander: restore_login successful. Successfully logged in as user @username:example.com via restore_login. Response is: WhoamiResponse(uuid='', start_time=None, end_time=None, timeout=0, transport_response=<ClientResponse(https://example.com/_matrix/client/r0/account/whoami?access_token=00-00000000-0000000000000000000000000000000) [200 OK]>
<CIMultiDictProxy('Server': 'nginx', 'Date': 'Thu, 15 Sep 2022 06:11:07 GMT', 'Content-Type': 'application/json', 'Content-Length': '87', 'Connection': 'keep-alive', 'Access-Control-Allow-Headers': 'Origin, X-Requested-With, Content-Type, Accept, Authorization', 'Access-Control-Allow-Methods': 'GET, POST, PUT, DELETE, OPTIONS', 'Access-Control-Allow-Origin': '*')>
, user_id='@username:example.com')
matrix-commander is ready and waiting for the other party to initiate an emoji verification with us by selecting 'Verify by Emoji' in their Matrix client. Read --verify instructions in --help carefully to assist you in how to do this quickly.

After this I don't get any further reply except when the client declines because of "timeout" or client user interaction

[HoboDev]

It might be due to a missing KeyVerificationAccept which I found in matrix-nio and is the reply after the initial KeyVerificationStart

[8go]

@HoboDev

I have re-tested that about 1 month ago multiple times with Element Android and Element Webapp in Firefox.
It is working. I cannot say anything about nheko, since I do not test that.

... since I can not start emoji verification directly from the client.

You can and you must start the emoji verification on the Element client (e.g. Element Webapp in Firefox).

Find the emoji verification initiation in Element.

There is another old issue here about the same subject. Search for "emoji" or "verification" in the issues and read those too, they might be helpful. But the key issue is that you must find and learn how to initiation the emoji verification in Element.

[ahcheing]

This may or may not be relevent to the OP, but for me the issue was (I think) my slow internet connection. after waiting ~10 minutes (approx, since I was not activly watching terminal or the browser, but I know it took longer then five minutes) the emoji's popped up in the terminal and in the browser. After which point everything seems to work fine.

I don't know if this is an issue with matrix-commander, my server instance, or with my slow internet, but I will say that verifying via element desktop or verifying in a new firefox profile does not take more then 5 minutes. so idk.

[8go]

My personal experience: I have done dozens of verification, maybe close to 100. It never took more than 1 min, in most cases I would say it had taken 1-5 seconds. Just my experience, your mileage may vary. I am very doubtful that the time it takes has to do with the matrix-commander app.

Thanks @ahcheing for sharing your experience.

[8go]

As a tiny tiny side note, it works slightly "better" if you accept the verification first on Element, then then secondly on matrix-commander. But this is not crucial, it works either way, but event order is different and logging is "nicer" that way.

[lesar]

I'm new to matrix and matrix-commander.
I have do verify matrix account for :

• element on android and
• Fractal on fedora.

I have installed by pip matrix-commander 7.6.0 2023-10-16
and then do
matrix-commander --login password ... all well.
but
matrix-commander --verify

only result in:

matrix-commander is ready and waiting for the other party to initiate an emoji verification with us by selecting 'Verify by Emoji' in their Matrix client. Read --verify instructions in --manual carefully to assist you in how to do this quickly.
2023-11-13 17:28:49,032: WARNING: nio.responses: Error validating response: 'next_batch' is a required property

this warnig repeat forever.

I use firefox 119 on fedora 38 and Web Element to verify. Notification is enabled. (all other app notification are poped up)
using matrix-commander no notification are poped up on web Element.

There is a problem or am I doing some thing wrong?

best regards,
Leonardo