element-web: "Can't load this message (m.room.message)" on reply in thread
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
About this issue
- Original URL
- State: closed
- Created 2 years ago
- Reactions: 1
- Comments: 17 (9 by maintainers)
Commits related to this issue
- Convert `setupNotificationListener` to an unbound function This isn't called by an event handler directly, so shouldn't need to be bound. Equally, this shouldn't cause any problems. This is a long-s... — committed to matrix-org/matrix-react-sdk by turt2live 2 years ago
- Add a catastrophic throw to thread constructor This is an attempt to narrow down https://github.com/vector-im/element-web/issues/22141 — committed to matrix-org/matrix-js-sdk by turt2live 2 years ago
- Add a catastrophic throw to thread constructor (#2375) This is an attempt to narrow down https://github.com/vector-im/element-web/issues/22141 — committed to matrix-org/matrix-js-sdk by turt2live 2 years ago
- Convert `setupNotificationListener` to an unbound function (#8618) This isn't called by an event handler directly, so shouldn't need to be bound. Equally, this shouldn't cause any problems. This is ... — committed to matrix-org/matrix-react-sdk by turt2live 2 years ago
- Merge tag 'v3.60.0' into sc * Loading threads with server-side assistance ([\#9356](https://github.com/matrix-org/matrix-react-sdk/pull/9356)). Fixes vector-im/element-web#21807, vector-im/element-we... — committed to SchildiChat/matrix-react-sdk by su-ex 2 years ago
- Merge tag 'v1.11.14' into sc * Switch to notarytool ([\#440](https://github.com/vector-im/element-desktop/pull/440)). * Loading threads with server-side assistance ([\#9356](https://github.com/matrix... — committed to SchildiChat/element-desktop by su-ex 2 years ago
- Merge tag 'v1.11.14' into sc * Loading threads with server-side assistance ([\#9356](https://github.com/matrix-org/matrix-react-sdk/pull/9356)). Fixes #21807, #21799, #21911, #22141, #22157, #22641, ... — committed to SchildiChat/element-web by su-ex 2 years ago
@JokerGermany looks like your issue was something else, awkwardly. Fix/mitigation is up at https://github.com/matrix-org/matrix-react-sdk/pull/8845