Comment by tclancy
20 days ago
What is going on with this? I tried that and the alias I have built in for this problem, `make_safe() { xattr -d -r com.apple.quarantine $1 }`
The application cannot be opened for an unexpected reason, error=Error Domain=RBSRequestErrorDomain Code=5 "Launch failed." UserInfo={NSLocalizedFailureReason=Launch failed., NSUnderlyingError=0xae1038720 {Error Domain=NSPOSIXErrorDomain Code=163 "Unknown error: 163" UserInfo={NSLocalizedDescription=Launchd job spawn failed}}}
The situation is actually worse than it looks.
This error exists because Apple has effectively made app notarization mandatory, otherwise, users see this warning. In theory, notarization is straightforward: upload your DMG via their API, and within minutes you get a notarized/stamped app back.
…until you hit the infamous "Team is not yet configured for notarization" error.
Once that happens, you can be completely blocked from notarizing your app for months. Apple has confirmed via email that this is a bug on their end. It affects many developers, has been known for years, and Apple still hasn't fixed it. It completely elimiates any chances of you being able to notarize your app, thus, getting rid of this error/warning.
Have a loot at how many people are suffering from this for years with no resolution yet: https://developer.apple.com/forums/thread/118465
Yikes. Why anyone would willingly develop for Apple platforms is beyond me. But then I also don't understand why some some people like using the crap^WmacOS. To each their own I guess. Hardware does look nice though, too bad about their software.
Well, mainly because it's a better unix than Linux for the desktop, and I'd rather pull my eyes out of their sockets with a rusty screwdriver than use Windows.
Other than developing my own (without using any other OS...) which is a ... significant ... task, there's not much other option. YMMV.
10 replies →
The advantage is you can just develop it once and publish, rather than pushing things through multiple different packaging processes, and a MacOS person might be more likely to spend money.
Because they "have" to have the nice display or good battery life I guess. Everyone has different priorities. Personally for me it's Linux or nothing.
Well, gotta sell wherever the customers are, unfortunately.
Because that is where the users with the money are.
> It affects many developers, has been known for years, and Apple still hasn't fixed it.
Not a feature they care about. Same for deleting apps not released yet. Haven't looked in a while but for over a decade it has been impossible to delete ios apps submitted and not released. So either you have to release the app, make it "apple approved" and then immediately kill it or have an app always present (I think you can hide it but I've not checked that in quite a while.
Can't you (as in the user) still just type `sudo spctl --master-disable` to get rid of the nonsense?
Yeah but this command sucks because AFAIK then it doesn’t even verify notarized apps anymore (for example if the certificate is invalid, if it was revoked, etc.)
And it inspired me to buy it for $0.99 and that doesn't work on Mac either. The [your least favorite tribe] really are revolting.