Closed fladd closed 9 months ago
This seems to be a packaging (or processor) issue. I had the same problem after update to 1.11.59 from some earlier version, but building Element locally produces an application that hasn't got the crash upon startup issue.
@vhalkola yeah I have a feeling its related to us having moved to M1 runners to build the Universal application and something about the M1 macOS environment being incapable of building for EOL Big Sur - though it is just a theory
Steps to reproduce
Crash report
Whole crash report is too long to post here apparently.
Outcome
What did you expect?
Element opens
What happened instead?
Element immediately crashes and the MacOS crash report states that there was a segfault 11.
Operating system
MacOS
Application version
Don't know, it crashes before I can check (but I updated today - 20240219)
How did you install the app?
Update from within Element
Homeserver
matrix.org
Will you send logs?
Yes