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

My messages are not visible to receiver, the receiver sees "waiting for this message" #28396

Closed
naccaccio opened this issue Nov 6, 2024 · 3 comments
Labels
A-E2EE 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-Info This issue is blocked awaiting information from the reporter

Comments

@naccaccio
Copy link

Steps to reproduce

  1. Send message on macOS app to another matrix.org user using web app

Outcome

What did you expect?

The receiver sees the message.

What happened instead?

The receiver sees "waiting for this message".

Operating system

No response

Application version

No response

How did you install the app?

No response

Homeserver

No response

Will you send logs?

Yes

@dosubot dosubot bot added A-E2EE 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 labels Nov 6, 2024
@t3chguy
Copy link
Member

t3chguy commented Nov 6, 2024

waiting for this message is not a string in Element Web or Desktop, more details would be necessary. Please fill the issue template where you left it blank with No response.

@t3chguy t3chguy added the X-Needs-Info This issue is blocked awaiting information from the reporter label Nov 6, 2024
@t3chguy
Copy link
Member

t3chguy commented Nov 18, 2024

Closing due to lack of required information

@t3chguy t3chguy closed this as not planned Won't fix, can't repro, duplicate, stale Nov 18, 2024
@andybalaam
Copy link
Member

After investigating the debug logs you sent (thanks!) we think this was caused by matrix-org/matrix-rust-sdk#1415 . (This bug is fixed, but it leaves things on the receiver side in an incorrect state.)

If the receiver logs out and logs in again, the problem should go away. Do get back to us here if that doesn't work.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-E2EE 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-Info This issue is blocked awaiting information from the reporter
Projects
None yet
Development

No branches or pull requests

3 participants