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

Can't view threads in a particular room "RealmList does not accept null values" #8529

Open
Standard8 opened this issue Jun 13, 2023 · 1 comment
Labels
O-Uncommon Most users are unlikely to come across this or unexpected workflow S-Major Severely degrades major functionality or product features, with no satisfactory workaround T-Defect Something isn't working: bugs, crashes, hangs and other reported problems

Comments

@Standard8
Copy link

Steps to reproduce

  1. On my desktop client, I have a room that appears to be fully read (including threads), but the desktop client thinks that it is unread. This is Room stuck as unread despite all messages/threads marked as read (to my knowledge) element-web#25481
  2. Out of interest I tried looking at it on my Element app on Android and the room shows as unread.
  3. Try and open the thread view of the room.

Outcome

What did you expect?

To see all the threads.

What happened instead?

An error message was displayed: "RealmList does not accept null values".

The only options were to retry or ok. Retry just gave the same error message. Ok would allow the error to be closed, but no threads would be displayed.

Your phone model

Fairphone 4

Operating system version

Android 12

Application version and app store

1.5.32 [40105322]

Homeserver

mozilla.org

Will you send logs?

Yes

Are you willing to provide a PR?

No

@Standard8 Standard8 added the T-Defect Something isn't working: bugs, crashes, hangs and other reported problems label Jun 13, 2023
@jmartinesp jmartinesp added O-Uncommon Most users are unlikely to come across this or unexpected workflow S-Major Severely degrades major functionality or product features, with no satisfactory workaround labels Jun 15, 2023
@xpac1985
Copy link

xpac1985 commented Jan 9, 2024

I see the same issue, and could now filter down the reason (at least for my case):

If you have someone set to Ignore/Blocked, and that person has written a message in a Thread, the Thread list for that channel will throw the error mentioned above. Unblocking (and reloading the client) will make it work again, but it also means you have to endure $person again. :D

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
O-Uncommon Most users are unlikely to come across this or unexpected workflow S-Major Severely degrades major functionality or product features, with no satisfactory workaround T-Defect Something isn't working: bugs, crashes, hangs and other reported problems
Projects
None yet
Development

No branches or pull requests

3 participants