"Can't load this message (m.room.message)" on reply in thread

[dinosmm]

Steps to reproduce

I replied to a message in the main chat room, and chose to reply in thread, from Element Android.

In Element Web and Element Desktop, in place of my reply I see this:

Can't load this message (m.room.message)

'View source' shows the message text correctly.

Outcome

What did you expect?

I expected to see my threaded reply correctly in the web and desktop clients.

What happened instead?

I see the error message:
Can't load this message (m.room.message)

Underlying JavaScript error:

2022-05-13T10:31:28.021Z E Cannot read properties of null (reading 'getThreads')
TypeError: Cannot read properties of null (reading 'getThreads')
    at new F (vector://vector/webapp/bundles/0dfc1e1dd51d68d7008e/vendors~init.js:2:636300)
    at k.getThreadsRoomState (vector://vector/webapp/bundles/0dfc1e1dd51d68d7008e/vendors~init.js:2:637831)
    at Xe.setupNotificationListener (vector://vector/webapp/bundles/0dfc1e1dd51d68d7008e/vendors~element-web-app.js:2:1047649)
    at Xe.componentDidMount (vector://vector/webapp/bundles/0dfc1e1dd51d68d7008e/vendors~element-web-app.js:2:1052579)
    at hs (vector://vector/webapp/bundles/0dfc1e1dd51d68d7008e/vendors~init.js:2:3063847)
    at Cl (vector://vector/webapp/bundles/0dfc1e1dd51d68d7008e/vendors~init.js:2:3080905)
    at t.unstable_runWithPriority (vector://vector/webapp/bundles/0dfc1e1dd51d68d7008e/vendors~init.js:2:3106190)
    at zi (vector://vector/webapp/bundles/0dfc1e1dd51d68d7008e/vendors~init.js:2:3022782)
    at Fl (vector://vector/webapp/bundles/0dfc1e1dd51d68d7008e/vendors~init.js:2:3077450)
    at hl (vector://vector/webapp/bundles/0dfc1e1dd51d68d7008e/vendors~init.js:2:3073561)

Operating system

Windows 10

Application version

1.10.12

How did you install the app?

From the official website

Homeserver

Synapse 1.58.0

Will you send logs?

Yes

[markiceman]

I have the same problem. It is last message in thread.

It is really big problem. Threads in 1.10.12 are unusable.

[MadLittleMods]

Looking at rageshake logs reproducing this, the relevant error is:

2022-05-13T10:31:28.021Z E Cannot read properties of null (reading 'getThreads')
TypeError: Cannot read properties of null (reading 'getThreads')
    at new F (vector://vector/webapp/bundles/0dfc1e1dd51d68d7008e/vendors~init.js:2:636300)
    at k.getThreadsRoomState (vector://vector/webapp/bundles/0dfc1e1dd51d68d7008e/vendors~init.js:2:637831)
    at Xe.setupNotificationListener (vector://vector/webapp/bundles/0dfc1e1dd51d68d7008e/vendors~element-web-app.js:2:1047649)
    at Xe.componentDidMount (vector://vector/webapp/bundles/0dfc1e1dd51d68d7008e/vendors~element-web-app.js:2:1052579)
    at hs (vector://vector/webapp/bundles/0dfc1e1dd51d68d7008e/vendors~init.js:2:3063847)
    at Cl (vector://vector/webapp/bundles/0dfc1e1dd51d68d7008e/vendors~init.js:2:3080905)
    at t.unstable_runWithPriority (vector://vector/webapp/bundles/0dfc1e1dd51d68d7008e/vendors~init.js:2:3106190)
    at zi (vector://vector/webapp/bundles/0dfc1e1dd51d68d7008e/vendors~init.js:2:3022782)
    at Fl (vector://vector/webapp/bundles/0dfc1e1dd51d68d7008e/vendors~init.js:2:3077450)
    at hl (vector://vector/webapp/bundles/0dfc1e1dd51d68d7008e/vendors~init.js:2:3073561)

---

My issue is separate #22195 but has the same symptoms showing the tile error boundary.

[turt2live]

stacktrace converted (loosely):

new ThreadsRoomNotificationState()
RoomNotificationStateStore#getThreadsRoomState // from the set call
EventTile#setupNotificationListener

this implies that thread.room is null, which is scary.

[turt2live]

I'm unable to find a way to reproduce this, and can't seem to trick it into happening on my local machine. If people see this, please submit logs with a link to the message so we can attempt investigation that way.

It's quite clear from the log traffic that it's happening often, so upgrading occurrence rating.

[turt2live]

Noting the "should never happen" cases, matrix-org/matrix-js-sdk#2375 attempts to add a more obvious error to locate what is going wrong and matrix-org/matrix-react-sdk#8618 is an extremely long shot at fixing this.

[markiceman]

What changed from 1.10.11 to 1.10.12? Version 1.10.11 don't have this problem.

[turt2live]

Far too many changes to consider, unfortunately. There's a dozen things which were fixed or changed about Threads alone.

[markiceman]

Try "Clear cache and reload".

[t3chguy]

What changed from 1.10.11 to 1.10.12? Version 1.10.11 don't have this problem.

A huge refactoring of how threads got created from being async to sync

[markiceman]

@t3chguy , @turt2live : Still cannot reproduce?

[turt2live]

for now, yes. We're collecting more information until we have a cause determined.

Please continue to submit logs when the bug happens.

[JokerGermany]

On all rooms (element-Android, element-web and so on, will send logs)

[JokerGermany]

Clearing Cache fixed it

[turt2live]

@JokerGermany looks like your issue was something else, awkwardly. Fix/mitigation is up at matrix-org/matrix-react-sdk#8845

[germain-gg]

This will be fixed once we land element-hq/element-meta#196 and #22981

[christro]

I have the same problems with https://app.element.io in Mac OS: Can't load this message (m.room.message)