Fractal sent a huge amount of verification cancel to device messages.
My account was clogged and no to-device encryption messages were received because all clients were downloading m.key.verification.cancel
.
I get a lot of those logs on element web:
Crypto: could not find VerificationRequest for m.key.verification.cancel, and could not create one, so ignoring. rageshake.ts:77:16
received to-device m.key.verification.cancel from: @toger5:matrix.org id: undefined rageshake.ts:77:16
And this message on element webR:
DEBUG matrix_sdk_crypto::machine: Received a to-device event
at /home/runner/.cargo/git/checkouts/matrix-rust-sdk-1f4927f82a3d27bb/3e17fc2/crates/matrix-sdk-crypto/src/machine.rs:1117
in matrix_sdk_crypto::machine::receive_to_device_event with sender="@toger5:matrix.org" event_type="m.key.verification.cancel"
in matrix_sdk_crypto::machine::receive_sync_changes 100 bundle.js:262326:19
Steps to reproduce
- Logging into Fractal nightly
- Starting a verification request with element X android.
- It failed to verify but its hard to describe where exactly (It was chaotic and pressing "start" (the verification) yielded the verification got canceled screen.
- Waiting for a couple of days.
- A huge amount of
m.key.verification.cancel
to device events accumulated. - Logging out the fractal device from another client and waiting for the to-device messages to be downloaded. My clients are working on them for multiple days now.
Information
(I will try to gether more information. Currently I dont have it at hand but dont want to forget about reporting this.)
Edited by Timo