Unable to leave (or otherwise interact with) room

[hutchisr]

Description

A room I'm in (was in?) lost it's title at some point and is now simply named <name of last account in the chat log> and 6763 others If I try to leave the room I get the error message @<my account> not in room !yhqiEdqNjyPbxtUjzm:matrix.org. If I try to send a message to the room I get the following error

User @<my account> not in room !yhqiEdqNjyPbxtUjzm:matrix.org (<FrozenEvent event_id='$157079196715146GBEDr:matrix.org', type='m.room.member', state_key='@<my account>'>)
Resend message or cancel message now.

I am also unable to perform any other actions such as mark the room as low priority or favorite (these actions do not give any error message, they simply don't work)

I am also unable to rejoin the room from the "explore rooms" dialog since Element thinks I'm still in it.

Steps to reproduce

Unfortunately, this happened out of the blue without any interaction on my part and I'm not even sure exactly when it did so I have no idea.

Logs being sent: yes

Version information

• Platform: desktop

For the desktop app:

• OS: macOS, Windows, and Linux, though I first noticed it while using macOS.
• Version: 1.7.18

[jryans]

@hutchisr If you clear Element's cache (User menu -> Settings -> Help -> Scroll down -> Clear cache), does that fix Element's view of the situation?

[linuxmail]

hi,

thanks for the hint: I had also a problem with a deleted room. I wasn't able to remove it out of Element, "Not a known room" was the message, but after clear the cache, the room disappears.

[hutchisr]

Clearing cache seems to have solved the issue, thanks!

[jryans]

I'm glad to hear clear cache was able to workaround this... Obviously it would be better if that were not needed at all, so let's keep this issue open, but at a lower priority.

[osresearch]

Due to a federation configuration mistake I ended up with quite a few Empty Room's that I couldn't leave due to the same "Not a known room" issue. Clearing the cache made them go away for me, too.

[nemobis]

Clearing the cache works also for a similar case of non-removable room: a room in the favorites which gets deleted and purged on the server. You cannot leave the room and trying to unfavorite does nothing.

[rgpublic]

Wow. So cool. Took me ages to find this issue. I always logged out and logged back in to get rid of old rooms, but that caused the usual dreaded flood of warning icons and undecipherable messages. As a simple workaround, I guess it would be quite nice to give at least a hint in the error message: "Not a known room. Try clearing the cache under Settings => Help if this issue persists".

[strypey]

I'm having the same issue, on Android (OxygenOS 11.1.2.2 on a Samsung OnePlus), with a copy of Element 1.5.3.2 installed using F-Droid. The room remains in my room list, and every attempt to leave the room results in a "Not a known room" error message. Clear cache isn't working. I tried closing the app and doing clear cache, same result.

[nycterent]

404 "Not a known room" - solved by clearing cache. Version 1.11.66 (1.11.66), MacOS 14.4.1, arm