Skip to content
This repository has been archived by the owner on Apr 12, 2022. It is now read-only.

some rooms are shown as Empty room with lazy loading #2671

Open
532910 opened this issue Oct 20, 2018 · 12 comments
Open

some rooms are shown as Empty room with lazy loading #2671

532910 opened this issue Oct 20, 2018 · 12 comments

Comments

@532910
Copy link
Contributor

532910 commented Oct 20, 2018

but room details shows two active members

@dva-re
Copy link
Contributor

dva-re commented Nov 7, 2018

it also appears on the latest dev-build = (

@non-Jedi
Copy link

For what it's worth, this is causing significant usability problems for my non-technical family members. It seems to happen only on 1-to-1 rooms with 2 different homeservers, but it isn't every room. Please chat with me @adam:thebeckmeyers.xyz if more details are needed or let me know if a rageshake would be helpful for this one.

@dkasak
Copy link
Member

dkasak commented Dec 17, 2018

FWIW, it's happening to me in a 1-on-1 room between me and another person on the same homeserver too.

@r4dh4l
Copy link

r4dh4l commented Jan 5, 2019

I have this problem since the last and the current version of Riot-Android installed via F-Droid (currently 0.8.21 (82100) - added on 2019-01-03, don't remember the version before, maybe Version 0.8.20 (82000) - added on 2018-12-27 ).
On Riot-Web/Desktop all Rooms are listed correctly.

It seems to happen only on 1-to-1 rooms with 2 different homeservers

In my case the affected 1on1-rooms contain only users from the same homeserver (which is not matrix.org).

@mvgorcum
Copy link
Contributor

In my case the affected 1on1-rooms contain only users from the same homeserver (which is not matrix.org).

I have the same issue. It's a single room that is affected.

Most notably it's a room that at some point was renamed, and the name was subsequently removed, causing the 1:1 room to revert back to the normal behavior (displaying the name of the other user in the room) without lazyloading.

@esackbauer
Copy link

Most notably it's a room that at some point was renamed, and the name was subsequently removed, causing the 1:1 room to revert back to the normal behavior (displaying the name of the other user in the room) without lazyloading.

Exactly the same with me.

@r4dh4l
Copy link

r4dh4l commented Jan 15, 2019

Most notably it's a room that at some point was renamed, and the name was subsequently removed, causing the 1:1 room to revert back to the normal behavior (displaying the name of the other user in the room) without lazyloading.

So providing a room name and removing it again solved the problem for you? Not working in my case, just tested. :/

@mvgorcum
Copy link
Contributor

No, I'm saying that adding a name and removing it happened in the past. Which worked fine without LL.

@r4dh4l
Copy link

r4dh4l commented Jan 15, 2019

Okay, sry and thx for confirming. I don't remember if I renamed the affected rooms in the past. I doubt that I did because all of them were created as 1:1 rooms and there is no need to give a special name to such rooms.

@mehturt
Copy link

mehturt commented May 5, 2019

For me it happens when I change display name or even profile image

@croulibri
Copy link

I have this problem since the last and the current version of Riot-Android installed via F-Droid (currently 0.8.21 (82100) - added on 2019-01-03, don't remember the version before, maybe Version 0.8.20 (82000) - added on 2018-12-27 ).
On Riot-Web/Desktop all Rooms are listed correctly.

It seems to happen only on 1-to-1 rooms with 2 different homeservers

In my case the affected 1on1-rooms contain only users from the same homeserver (which is not matrix.org).

I face exactly the same situation.
Removing the lazy loading correct the problem as the room name take again the name of the correspondent.

@schildbach
Copy link

I had the "Empty room" problem too after I set my avatar. I just disabled "lazy loading" and this fixed this issue for me.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests