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

'Waiting for this message' #2263

Closed
wrjlewis opened this issue Dec 18, 2023 · 5 comments
Closed

'Waiting for this message' #2263

wrjlewis opened this issue Dec 18, 2023 · 5 comments
Labels
A-E2EE Encryption A-Timeline O-Occasional Affects or can be seen by some users regularly or most users rarely S-Major Severely degrades major functionality or product features, with no satisfactory workaround T-Defect X-Needs-Rust This issue needs a Rust SDK change. It must have a link to a Rust SDK issue

Comments

@wrjlewis
Copy link

Steps to reproduce

Messages with the text 'Waiting for this message' appear instead of the actual message.

When it happens it affects all subsequent messages until you sign out and sign in again.

Occurring maybe once or twice a week to me (will rageshake when I next see it and attach to this issue).

Other chat clients are unaffected, for example the same message appears ok in Element or Fluffychat.

There have been a couple of similar reports in #element-x-ios:matrix.org, eg here.

Outcome

What did you expect?

Messages to appear successfully

What happened instead?

All messages from an individual appear as 'Waiting for this message', from the point of the bug showing up.

Your phone model

iPhone 12 pro

Operating system version

17.1.2

Application version

1.4.3

Homeserver

Synapse 1.98 @ wi11.co.uk

Will you send logs?

Yes

@wrjlewis
Copy link
Author

@stefanceriu
Copy link
Member

There's thousands of errors in those logs, ranging from Socket is not connected to IncompleteMessage, Operation timed out and 404 Event not found.
I would say it's not surprising that something broke but what is really surprising is that it needs a full logout for it to start working again. We'll need someone from the crypto team to have a look at this I guess.

@wrjlewis
Copy link
Author

wrjlewis commented Dec 19, 2023

There's thousands of errors in those logs, ranging from Socket is not connected to IncompleteMessage, Operation timed out and 404 Event not found. I would say it's not surprising that something broke but what is really surprising is that it needs a full logout for it to start working again. We'll need someone from the crypto team to have a look at this I guess.

Oh dear..
Despite my best efforts I do have a lot of issues with federation spikes on my homeserver, causing freezes/instability across my network. Perhaps that explains all the network related errors you've mentioned

@Velin92 Velin92 added X-Needs-Rust This issue needs a Rust SDK change. It must have a link to a Rust SDK issue S-Major Severely degrades major functionality or product features, with no satisfactory workaround O-Occasional Affects or can be seen by some users regularly or most users rarely labels Dec 19, 2023
@pr0ton11
Copy link

pr0ton11 commented Jan 12, 2024

I have the same issues, but no error messages from logs both the server and sliding sync proxy. Are the logs part of the element client and should I rage-shake whenever it happens?

@wrjlewis
Copy link
Author

wrjlewis commented Jan 24, 2024

I haven't seen this problem for the last couple of weeks now. Update: still happening occasionally

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-E2EE Encryption A-Timeline O-Occasional Affects or can be seen by some users regularly or most users rarely S-Major Severely degrades major functionality or product features, with no satisfactory workaround T-Defect X-Needs-Rust This issue needs a Rust SDK change. It must have a link to a Rust SDK issue
Projects
None yet
Development

No branches or pull requests

5 participants