"Downloader.app" will damage your computer. You should move it to the Bin.

[TonnyCS]

I got this error today, unfortunatelly I have no idea what to do. When I try to reinstall it via curl install.sh, the start fails with the error code 153.

The application cannot be opened for an unexpected reason, error=Error Domain=RBSRequestErrorDomain Code=5 "Launch failed." UserInfo={NSLocalizedFailureReason=Launch failed., NSUnderlyingError=0x600000d0a700 {Error Domain=NSPOSIXErrorDomain Code=153 "Unknown error: 153" UserInfo={NSLocalizedDescription=Launchd job spawn failed}}}

[vineetchoudhary]

Hi,

As per this thread, This issue is intermittent and happens 20% of time even if app codesigning and notarisation is clean.

Can you please confirm if you face this issue when you launch the app manually from Applications directory? If you are able to launch manually then I'll remove open command from install script.

[Moulick]

@vineetchoudhary did you make the release? I think I got a notification a couple of hours ago for the tag but an associated release does not exist, nor does a compiled app. Aria2c seems to have been added as an asset to the 2.2 release though https://github.com/vineetchoudhary/Downloader-for-Apple-Developers/releases/tag/2.2.0

[vineetchoudhary]

@Moulick, yes I released and removed 2.3.0 because I was still facing the same issue on another machine. I added aria2c to the asset because I'm planning to install aria2c separately. Because when aria2c is available in Downloader.app then macOS block the launch.

[kg-currenxie]

Same issue for me :/ Both with curl on downloading a release

[toineenzo]

Certificate seems expired?? I once saw a video where somebody said a work around is to move the file around some directories and only after that, open it. But that doesn't seem to do the trick here. I think its just the expired certificate.

[Moulick]

Would love to know if there was any workaround to this problem. Even trying to self-sign via codesign --force --deep -s - /Applications/Downloader.app and codesign --force --deep --sign - /Applications/Downloader.app does not work :(

[davidebeatrici]

Right click on the binary -> Get Info -> Check Override Malware Protection.

The application now crashes with EXC_CRASH (SIGKILL (Code Signature Invalid)) though.

[Moulick]

Whoooo! I was actually able to make it work!

1. Download from https://github.com/vineetchoudhary/Downloader-for-Apple-Developers/releases/download/2.2.0/Downloader.app.zip, unzip Downloader.app.zip and move Downloader.app into /Applications directory. The link in readme has an expired certificate so will not work anymore
2. Try to launch once, MacOS will not allow it and give warnings about malware etc. Dismiss the warnings. This is an important step else the below Override Malware Protection will not appear.
3. Right-click the application, Go to Get Info, and Check Override Malware Protection
4. Run codesign --force --deep --sign - /Applications/Downloader.app. This will sign the application with your own signature.
5. run codesign --force --deep --sign - /Applications/Downloader.app/Contents/Resources/aria2c. This will sign the included aria2c binary.
6. Success!! Now you'll be able to launch and use the application without MacOs complaining.

[cbowns]

This is a lot of work to run an application that Apple revoked the certificate for. c.f. #34

% codesign -v Downloader.app           
Downloader.app: CSSMERR_TP_CERT_REVOKED

[Moulick]

@cbowns true but till @vineetchoudhary is able to get a new cert and make a release signing both aria2c and his application, this is the only workaround.

[Moulick]

Btw @vineetchoudhary, you don't have to release aria2c separately. I think as long as you sign it with your certificate and then include it in the Downloader.app, it should work. No need to even build the binary yourself, I think you can just get it from the official source during build time and sign it.