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

Cannot leave old rooms which no longer exist #399

Closed
krille-chan opened this issue Jul 15, 2023 · 2 comments
Closed

Cannot leave old rooms which no longer exist #399

krille-chan opened this issue Jul 15, 2023 · 2 comments
Labels
stale The item is going to be closed soon because of inactivity

Comments

@krille-chan
Copy link
Owner

Description

Trying to leave an old room -- in this case, the old #conduit:fachschaften.org room -- produces an error message:

M_BAD_STATE: Cannot leave a roo*

*Modal dialog/alert cuts off here, but based on Conduit's source code (https://gitlab.com/famedly/conduit/-/blob/next/src/database/rooms.rs#L2636), presumably says "...Cannot leave a room you are not a member of."

Ultimately, this error probably applies to any deleted room, whether or not it was replaced.

To Reproduce

Connect fluffychat to a Conduit server; join a federated room elsewhere. Then, migrate that room with same name and server, but presumably new id (may need to ask Timo Koesters of Conduit the specifics). Join the new room.

Fluffychat continues to show the old room (with old id) and new room (new id), both having same name.

Trying to leave the room -- which is again presumably done via API call using a room id, not name, produces the above error message.

Ultimately, this error probably applies to any deleted room, whether or not it was replaced.

Additional information:

Note that Element mobile does NOT show the old instance of the room; only the current, updated one.

  • Device: iphone 11 pro max
  • OS and OS version: ios 15.5
  • Installed version of FluffyChat: 1.5.0
Copy link

This issue is stale because it has been open for 120 days with no activity.

@github-actions github-actions bot added the stale The item is going to be closed soon because of inactivity label Dec 27, 2023
Copy link

This issue was closed because it has been inactive for 14 days since being marked as stale.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Jan 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
stale The item is going to be closed soon because of inactivity
Projects
None yet
Development

No branches or pull requests

1 participant