From c8658d0c50e101c0886910f72590711331b30f9a Mon Sep 17 00:00:00 2001 From: Andy Balaam Date: Wed, 11 Dec 2024 15:36:14 +0000 Subject: [PATCH] Add a comment clarifying why we conclude Unknown for an historical message. Co-authored-by: Richard van der Hoff <1389908+richvdh@users.noreply.github.com> Signed-off-by: Andy Balaam --- crates/matrix-sdk-crypto/src/types/events/utd_cause.rs | 2 ++ 1 file changed, 2 insertions(+) diff --git a/crates/matrix-sdk-crypto/src/types/events/utd_cause.rs b/crates/matrix-sdk-crypto/src/types/events/utd_cause.rs index a85e3fd88a0..c75b75e3b7a 100644 --- a/crates/matrix-sdk-crypto/src/types/events/utd_cause.rs +++ b/crates/matrix-sdk-crypto/src/types/events/utd_cause.rs @@ -220,6 +220,8 @@ impl UtdCause { if crypto_context_info.is_backup_configured || crypto_context_info.this_device_is_verified { + // Either backup download is working but we still don't have the key, or backup download + // *isn't* working despite being verified. In either case, we shrug and give an `Unknown` cause. UtdCause::Unknown } else { UtdCause::HistoricalMessageAndDeviceIsUnverified