After an invite is rejected locally, we don't update the clients about it via /sync
(riot-web bug: https://github.com/vector-im/riot-web/issues/3743)
To confirm if you are suffering from this bug: try telling your client to flush its cache. If the invite goes away, it is this bug.
You're right. The invite does go away.
Is there any chance that this will get added to the holding pen so it is at least in the plan to fix this soon? This is one of the more annoying user facing bugs still present in Synapse.
I can confirm that I experienced this bug recently as well. Clearing the cache in Riot web made the stuck invite go away.
cc @neilisfragile
I just had this with most recent version of riot web app. I had to:
Unfortunately I had to do a similar activity on my mobile app as well but hopefully these steps help someone
I've added a $200 bounty to encourage a community member to work on this important Synapse issue. It expires 2020-01-01. https://freedomsponsors.org/issue/849/locally-rejected-invites-dont-get-passed-on-to-the-client?alert=SPONSOR#description
If a Synapse core team member solves the issue while at work, I will reallocate this bounty to another issue. If a core team member wants to solve this with their community hat on then they can choose to take the bounty.
Hi @aaronraimist, I made a Github bot and a website similar to the https://freedomsponsors.org/ you are using. The Github bot can automatically add a comment to every new issue with a link to a website that encourages people to add reward. (It adds a link to existing open issues when you install). It automatically comments on the issue and tag people when anyone gives a reward, claim the rewards, and approve a reward. Automatically label issues with rewards so you know what is really important for your users.
I wonder if you or the owner of this repo would like to try it. It's in beta now, I'm looking for people to give it a try.
Could this be fixed, please? This causes a very prominent and serious issue in Riot, see https://github.com/vector-im/riot-web/issues/3743#issuecomment-589652386. That bug is literally "front and center", and there is no obvious recourse for a normal end user. In other words, the bug is persistent. (Reading bug reports for workaround and flushing caches does not count.) I ran into this after using Riot only twice. It makes a really immature impression of Riot and Matrix.
I just had this with most recent version of riot web app. I had to:
- clear cache and reload in security/settings
- go to bottom of security/settings and apparently (and thankfully) there are 'Bulk Options' which included 'reject all 213 invites' <--- not sure how that even happened as it was one person inviting me...
- wait a really long time while it cleared
- log out
- Log back in
Unfortunately I had to do a similar activity on my mobile app as well but hopefully these steps help someone
"Clear cache and reload" is now here under Help & About:

That's nice, but it doesn't help affected users, because they cannot possibly know that this button is a workaround for this bug. Googling for bug reports is not a proper user interface.
I can also confirm that, once locally_rejected is set for a room in the database, the invite persists very prominently and annoyingly in all other clients, until "clear cache and reload" is used on every client.
I agree that this needs to be fixed urgently.
As stated on https://github.com/vector-im/riot-web/issues/3743#issuecomment-645911842:
This bug is really annoying and can [make] one's life miserable if you get spammed by room invites (just saying). Any progress or estimates when it would be addressed?
Most helpful comment
I've added a $200 bounty to encourage a community member to work on this important Synapse issue. It expires 2020-01-01. https://freedomsponsors.org/issue/849/locally-rejected-invites-dont-get-passed-on-to-the-client?alert=SPONSOR#description
If a Synapse core team member solves the issue while at work, I will reallocate this bounty to another issue. If a core team member wants to solve this with their community hat on then they can choose to take the bounty.