I've been debugging why one Element X user cannot decrypt a message. Logs suggest that the to-device message containing the new room key was never received. This could be because:
The sender never sent it
The server never delivered it
Unfortunately, I cannot verify either of these. The sender was on FluffyChat. Is there any way I can rule out FluffyChat as a cause? Element clients tag to-device messages with an extra key under content called org.matrix.msgid which can then be logged server-side, enabling the message to be traced across multiple services. If FluffyChat did the same, and also provided some way to expose the logs client-side for debugging, then it would be possible to see if the client did send the room key and if the server got it / delivered it.
Bug Description
I've been debugging why one Element X user cannot decrypt a message. Logs suggest that the to-device message containing the new room key was never received. This could be because:
Unfortunately, I cannot verify either of these. The sender was on FluffyChat. Is there any way I can rule out FluffyChat as a cause? Element clients tag to-device messages with an extra key under
contentcalledorg.matrix.msgidwhich can then be logged server-side, enabling the message to be traced across multiple services. If FluffyChat did the same, and also provided some way to expose the logs client-side for debugging, then it would be possible to see if the client did send the room key and if the server got it / delivered it.Steps to Reproduce
Send a message in an encrypted room.
Expected Behavior
Messages should be decryptable by the receiver.
App Version
1.20.0
Additional Platform Information
Unknown
Additional Context
No response