Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Device list not updated on sending device, leading to UTDs #2594

Open
Tracked by #2411
richvdh opened this issue Oct 23, 2024 · 0 comments
Open
Tracked by #2411

Device list not updated on sending device, leading to UTDs #2594

richvdh opened this issue Oct 23, 2024 · 0 comments
Labels
A-E2EE Z-UISI Unable to decrypt errors

Comments

@richvdh
Copy link
Member

richvdh commented Oct 23, 2024

I now have seen twofour separate reports of UTDs where the logs show:

  • Recipient logs in on a new device
  • Sender does not perform a /keys/query request for the recipient
  • Some time later, sender sends an encrypted message, but omits the new device
  • Recipient (obviously) receives a UTD.

It is unclear if the cause is that Synapse does not tell the sender about the new device, or that the sender ignores the notification.

Something that is in common between the reports I have seen is that the sender and recipient are on different servers, so one potential cause is that the federated device-list-update-notification is getting lost. I've now seen a similar report between users on the same server.

The senders in the two cases are on different clients (EWR vs EX).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-E2EE Z-UISI Unable to decrypt errors
Projects
None yet
Development

No branches or pull requests

1 participant