Error: Cannot read properties of undefined (reading 'concat')

[syveriea]

Describe the bug

I was reading an old message from March 3rd 2026, some of the messages weren't able to be decrypted anymore, i started scrolling down and when I had scrolled down far enough where I had replied to a message that Element says was "Unable to load event that was replied to, it either does not exist or you do not have permission to view it." Sable crashes

on Element it shows up just fine and doesn't crash when trying to view this message:

Reproduction

try to load a message that replied to another message that you cant view(?)

Expected behavior

for it to not crash and render it like how Element does it

Platform and versions

- OS: CachyOS GNU/Linux x86_64
- Browser: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/148.0.0.0 Safari/537.36 (I'm using Helium Browser on wayland)
- Sable: v1.16.0 (604661e)
- Matrix homeserver: federated.nexus

Additional context

Automated Bug Report

Error occurred in the application.

Error Message

Cannot read properties of undefined (reading 'concat')

Stacktrace

TypeError: Cannot read properties of undefined (reading 'concat')
    at m.room.pinned_events (https://app.sable.moe/assets/index-2mwvDDQd.js:174611:34)
    at https://app.sable.moe/assets/index-2mwvDDQd.js:153891:16
    at children (https://app.sable.moe/assets/index-2mwvDDQd.js:175323:26)
    at F.useMemo.i (https://app.sable.moe/assets/index-2mwvDDQd.js:173017:14)
    at L (https://app.sable.moe/assets/index-2mwvDDQd.js:173046:17)
    at https://app.sable.moe/assets/index-2mwvDDQd.js:173105:58
    at dA (https://app.sable.moe/assets/index-2mwvDDQd.js:23433:155)
    at nG (https://app.sable.moe/assets/index-2mwvDDQd.js:24064:28)
    at PG (https://app.sable.moe/assets/index-2mwvDDQd.js:25997:90)
    at RG (https://app.sable.moe/assets/index-2mwvDDQd.js:25695:15)

[7w1]

I didn't really test the linked PR that should fix this, so if it continues occurring after the next release let me know and I'll reopen the issue, although I think it should be fixed.