-
Notifications
You must be signed in to change notification settings - Fork 3.8k
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鈥檒l occasionally send you account related emails.
Already on GitHub? Sign in to your account
馃悰 Bug Report: Unable to delete team membership from user profile if the team doesn't exist #5914
Comments
Never tried doing this and I can see why this happens. I was going to suggest a custom function that triggers when Interesting to say the least. Gonna take a small look into the code. |
Alright so looking at the calls being made, it's pretty clear why this happens. Deleting a membership makes a I think the best way to fix this would be to implement deletion of all memberships in a team, when a team is deleted. But it seems like this is already being done. Now I'm even more intrigued lol Edit: It does look like the membership isn't "unlinked" from the user though. So that would explain the issue you're facing. Gonna dive deeper |
Yes, You're right! Without it, the membership will be forever present in the user details with the name n/a and no thumbnail. It is a dead end. |
@vlohar08 thank you for raising this. We'll investigate this and share some more details :) |
Hi Appwrite team. Can I be assigned to make a PR for this issue? I have fixed it on a local dev environment by adding the |
@safwanyp sure go ahead 馃槃 I'll assign it to you |
Actually, I'm going to close this as a duplicate of #5517 |
Appreciate it Christy! Making a PR now 馃榿 |
馃憻 Reproduction steps
You will get this error - The Requested Team Invitation Could not be found.
馃憤 Expected behavior
馃憥 Actual Behavior
馃幉 Appwrite version
Version 1.3.x
馃捇 Operating system
Linux
馃П Your Environment
Appwrite Version - 1.3.8
Self-hosted on Digital Ocean using Marketplace Image
馃憖 Have you spent some time to check if this issue has been raised before?
馃彚 Have you read the Code of Conduct?
The text was updated successfully, but these errors were encountered: