Skip to content
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

Closed
odysseus90210 opened this issue Mar 19, 2021 · 11 comments
Closed

3.1 crashes with code signing error #18

odysseus90210 opened this issue Mar 19, 2021 · 11 comments

Comments

@odysseus90210
Copy link

macupdate.com has made version 3.1 available, but launching it produces a code signing error.

@sveinbjornt
Copy link
Owner

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

@odysseus90210
Copy link
Author

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.

@sveinbjornt
Copy link
Owner

I am unable to reproduce. Could you try running the Sloth binary from the command line? e.g.

cd Sloth.app/Contents/MacOS
./Sloth

And send me the message you get in the terminal?

@odysseus90210
Copy link
Author

odysseus90210 commented Mar 19, 2021

./Sloth gives:

zsh: no such file or directory: ./Sloth

I don't have Xcode installed or other developer tools, by the way

@sveinbjornt
Copy link
Owner

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?

@odysseus90210
Copy link
Author

Crashed Thread: 0

Exception Type: EXC_BAD_ACCESS (Code Signature Invalid)
Exception Codes: 0x0000000000000032, 0x00000001044b8000
Exception Note: EXC_CORPSE_NOTIFY

Termination Reason: Namespace CODESIGNING, Code 0x2

kernel messages:

VM Regions Near 0x1044b8000:
__LINKEDIT 1044b4000-1044b8000 [ 16K] r--/r-- SM=COW /Applications/Sloth.app/Contents/MacOS/Sloth
--> mapped file 1044b8000-1044bc000 [ 16K] r--/r-x SM=PRV Object_id=1e69afdd
__TEXT 1045c0000-10463c000 [ 496K] r-x/r-x SM=COW /usr/lib/dyld

@sveinbjornt
Copy link
Owner

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?

@odysseus90210
Copy link
Author

Same problem (using https://sveinbjorn.org/files/software/sloth/sloth-3.1.zip)

@sveinbjornt
Copy link
Owner

How about now? If this didn't work, I swear I'm giving up on releasing further updates for broken macOS.

@odysseus90210
Copy link
Author

That worked! What did you change, and why didn't you experience the problem on your end?

@sveinbjornt
Copy link
Owner

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.

@x13a x13a mentioned this issue Apr 23, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants