-
-
Notifications
You must be signed in to change notification settings - Fork 155
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
3.1 crashes with code signing error #18
Comments
The latest version of Sloth is not code-signed because ... Apple sucks and macOS Big Sur is so locked down that it reports non-notarized Developer ID-signed apps as "damaged". You should be able to download the app, Ctrl-click the bundle and select "Open". https://sveinbjorn.org/files/software/sloth/sloth-3.1.zip |
I should have been clearer. That doesn't work -- the app crashes when I ctrl-click and select "open", unlike for Sloth 3.0.1. |
I am unable to reproduce. Could you try running the Sloth binary from the command line? e.g.
And send me the message you get in the terminal? |
./Sloth gives: zsh: no such file or directory: ./Sloth I don't have Xcode installed or other developer tools, by the way |
This is strange. Could you Ctrl-clicking Sloth.app, selecting Show Package Contents, navigating through Contents, then MacOS, and then double-clicking the Sloth binary? |
Crashed Thread: 0 Exception Type: EXC_BAD_ACCESS (Code Signature Invalid) Termination Reason: Namespace CODESIGNING, Code 0x2 kernel messages: VM Regions Near 0x1044b8000: |
I've updated the 3.1 binary, think I discovered what was wrong. Could you try re-downloading it and see if the problem persists? |
Same problem (using https://sveinbjorn.org/files/software/sloth/sloth-3.1.zip) |
How about now? If this didn't work, I swear I'm giving up on releasing further updates for broken macOS. |
That worked! What did you change, and why didn't you experience the problem on your end? |
This seems to be related to macOS quarantine flags and a bug in Apple's codesign command line tool, which is used during the build process for Sloth. Not entirely sure why I was unable to reproduce, the way macOS handles binaries with signing issues is not well documented and seems to change with every version of the OS. |
macupdate.com has made version 3.1 available, but launching it produces a code signing error.
The text was updated successfully, but these errors were encountered: