-
-
Notifications
You must be signed in to change notification settings - Fork 2k
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
client gets stuck with invites even after they get rejected #3743
Comments
this is a synapse bug really |
I have an instance of what I presume is this. Stuck invite, can't join or reject it. Its just sitting in my room list and making Riot display a notification bubble constantly. I run my own homeserver. Any way to kill it? |
@rschulman after you reject it (and fail), clear client cache |
While we wait for this to be fixed in Synapse, Riot should just remove that room from its own database when I click reject. This is what Quaternion does and it means that at least you don't have to clear cache on all of your devices, you just have to click reject on all of your devices. |
I'll look into this shortly |
Any progress? |
As for the workaround at this level, its too ambiguous in the case of what happens when a real re-invite comes through. This issue is blocked on Synapse fixing their issue. |
@benbucksch the upstream issue you want to track is matrix-org/synapse#2181 |
@aviau clear client cache in settings after hitting Reject. This is a Synapse bug. |
@t3chguy where do you clear this cache from the web client at riot.im/app? |
Settings > Help & About |
This bug is really annoying and can one's life miserable if you get spammed by room invites (just saying). Any progress or estimates when it would be addressed? |
As per above, the issue is upstream: matrix-org/synapse#2181 |
fixed by matrix-org/synapse#7804 |
Was still seeing this in Element/android... here's my workaround to get rid of it. In my case, I had both the invite message that wouldn't go away and a working DM window with the same person. In Riot/web (or desktop):
Make sure you keep valid JSON syntax when editing it (beware of commas, etc). |
if we can't reach a remote server when rejecting an invite, we just flag it as rejected locally. But it looks like we forget to update the client (via /sync).
Workaround is to flush the cache in the client.
The text was updated successfully, but these errors were encountered: