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

Locally-rejected invites don't get passed on to the client #2181

Open
richvdh opened this issue May 2, 2017 · 8 comments

Comments

Projects
None yet
8 participants
@richvdh
Copy link
Member

commented May 2, 2017

After an invite is rejected locally, we don't update the clients about it via /sync

(riot-web bug: vector-im/riot-web#3743)

@richvdh

This comment has been minimized.

Copy link
Member Author

commented Apr 27, 2018

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.

@AdrienMatricon

This comment has been minimized.

Copy link

commented Apr 27, 2018

You're right. The invite does go away.

@aaronraimist

This comment has been minimized.

Copy link
Contributor

commented Feb 17, 2019

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.

@redsky17

This comment has been minimized.

Copy link

commented Feb 17, 2019

I can confirm that I experienced this bug recently as well. Clearing the cache in Riot web made the stuck invite go away.

@ara4n

This comment has been minimized.

Copy link
Member

commented Feb 17, 2019

@wayneoutthere

This comment has been minimized.

Copy link

commented Mar 22, 2019

I just had this with most recent version of riot web app. I had to:

  1. clear cache and reload in security/settings
  2. 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...
  3. wait a really long time while it cleared
  4. log out
  5. Log back in

Unfortunately I had to do a similar activity on my mobile app as well but hopefully these steps help someone

@aaronraimist

This comment has been minimized.

Copy link
Contributor

commented Apr 3, 2019

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.

@sunshineo

This comment has been minimized.

Copy link

commented Apr 26, 2019

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.