Installation type: dmg
I have tested with the latest version
Manually installing 2.17.0 from dmg file results in the app crashing 100% of attempts to open it.
crash, see log, 1 year
app should open without crash
Same for "auto upgrading" to 2.17.0 :(
Edit:
macOS 10.15.1
Installation Type: brew cask
Can confirm.
MacOS Catalina 10.15
App Version: 2.17.0
Installation type: dmg
I have tested with the latest version
I can simulate the issue easily
Logs: PasteBin
after upgrade (or manual install) does crash on start on Mac OS 10.14.6
Can confirm.
MacOS High Sierra 10.13.6
App Version: 2.17.0
Installation type: manually, dmg
After the update I specifically deleted all the files: ~/Library/Application Support/Rocket.Chat, ~/Library/Application Support/chat.rocket*. and still it didn鈥檛 help.
Same here.
macOS High Sierra 10.13.6
App Version: 2.16.0
Installation Type: App Store
Does not show crash report. Reinstallation does not help.
Workaround:
Install 2.16.2 from .dmg and skip the immediate update prompt presented by the application.
seems like the signature is incorrect so it wont launch the app
Exception Type: EXC_BAD_ACCESS (Code Signature Invalid)
Here's a full crash report.
crash.txt
Crash confirmed on 10.15.2 Beta (19C46a).
By signing the PKG using my Developer Certificate it installed and is working ok.
Any plans to fix this? It's a daily annoyance.
Questions for developers:
2.17.0 still has this issue
Same Issue :/
When will the problem be fixed?
Still not fixed...
this is a kludge because the package should really be signed with a valid apple developer cert, but you should be able to make 2.17.0 run on your mac by doing this (in the terminal):
xattr -r -d com.apple.quarantine /Applications/Rocket.Chat.app
sudo chown -R $(whoami) /Applications/Rocket.Chat.app
sudo codesign --force --deep --sign - /Applications/Rocket.Chat.app
Hey @tassoevan, it seems you did the 2.17.0 release on Github. Can you please take a look at this? Perhaps just withdraw the 2.17.0 release so it doesn't break people's chat program on auto update?
this is a kludge because the package should really be signed with a valid apple developer cert, but you should be able to make 2.17.0 run on your mac by doing this (in the terminal):
xattr -r -d com.apple.quarantine /Applications/Rocket.Chat.app
sudo chown -R $(whoami) /Applications/Rocket.Chat.app
sudo codesign --force --deep --sign - /Applications/Rocket.Chat.app
this worked perfectly. thanks internet stranger.
Be aware this doesn't work for everyone. Mine still crashes upon boot even after running the commands that @pjv suggests.
rocketchat217_crash_catalina.txt
Edit: Seems related to missing developer tools - guessing that is a prerequisite?
% sudo codesign --force --deep --sign - /Applications/Rocket.Chat.app
/Applications/Rocket.Chat.app: replacing existing signature
xcrun: error: invalid active developer path (/Library/Developer/CommandLineTools), missing xcrun at: /Library/Developer/CommandLineTools/usr/bin/xcrun
/Applications/Rocket.Chat.app: the codesign_allocate helper tool cannot be found or used
In subcomponent: /Applications/Rocket.Chat.app/Contents/Frameworks/Electron Framework.framework
this is a kludge because the package should really be signed with a valid apple developer cert, but you should be able to make 2.17.0 run on your mac by doing this (in the terminal):
xattr -r -d com.apple.quarantine /Applications/Rocket.Chat.app
sudo chown -R $(whoami) /Applications/Rocket.Chat.app
sudo codesign --force --deep --sign - /Applications/Rocket.Chat.app
Only works if you have a codesigning certificate in your Keychain.
May I ask why this bug is still unassigned?
I'd like think a program being unable to start because it's seems it's not signed probably should be a fix, that doesn't take 7+ days.
Still under investigation, related to https://github.com/electron-userland/electron-builder/issues/4297
@tassoevan Thanks for the update, appreciate it. Do you have an ETA for a fix?
Same issue here:

Logical CPU: 6
Error Code: 0x00000015 (invalid protections for user instruction write)
Trap Number: 14
@tassoevan, is there an ETA on getting this patched? I know it has been asked before, but a compile with the right certificate is all that is required (or it appears as such) shouldn't take over a week to resolve...
the latest release 1.17.1 fixes the issue
Confirmed fixed.
I can also confirm that it is fixed
2.17.1 fixes the problem.
Commit is here: https://github.com/RocketChat/Rocket.Chat.Electron/pull/1436
Seems update mechanism is gone from app, but that's another story for another issue.
Closing as this specific problem is resolved.
Most helpful comment
May I ask why this bug is still unassigned?
I'd like think a program being unable to start because it's seems it's not signed probably should be a fix, that doesn't take 7+ days.