Unexpected grey "authenticity cannot be guaranteed" warnings

[ara4n]

Steps to reproduce

1. Receive new e2ee msgs
2. They have unexpected grey (i) warnings on them
3. Tapping on warning gives "authenticity cannot be guaranteed on this device or so"

However, the authenticity should be fine as they shouldn't have been fished out of backup or otherwise gossipped.

This is particularly bad if the grey warning eclipses the fact that the message came from an unverified device, and so should have a red warning.

This is a rust-sdk bug: matrix-org/matrix-rust-sdk#3703 hopefully fixed by matrix-org/matrix-rust-sdk#4040 but filing here at the app-layer for tracking purposes and to confirm that the SDK fix actually works.

Outcome

What did you expect?

App should prioritise the trust of message keys received via Olm from the sender over the trust of keys fished out of backup.

What happened instead?

Presumably it raced, fished them out of backup, and then didn't update the shields later.

Your phone model

No response

Operating system version

No response

Application version

718

Homeserver

matrix.org

Will you send logs?

Yes