3 ms·
Built my first Mac app in a while this month, electron based because it does the job. Really unsettling to me that something running fine all working good I up
by whywhywhywhy 3y ago
Built my first Mac app in a while this month, electron based because it does the job.
Really unsettling to me that something running fine all working good I upload it to my web space and download it again and now launching the app says “this app is damaged, contact the developer” and the only option is “move to bin” or cancel.
Now I understand the gatekeeper system well enough at least I thought I did that I was expecting to have to right click open which is pretty standard in Mac land now. But it took me some digging that this “broken” message is just about signing nothing else, the app isn’t broken at all it’s just not been signed.
I understand the reasons gatekeeper exists and I agree with them mostly but changing this messaging from “unidentified developer” to “broken” feels like an aggression against being able to build software without paying the $99 toll gate.
I eventually found a way around it after 3 hours to get the old style “unidentified developer” message without paying Apple. But there was so little info around in half considering making a tutorial explaining it.
But yeah my point mostly is Apple trying to force the hands of developers by escalating warning messages is very worrying to me. None of this was needed from OS X 10.0 to 10.10 not sure why the aggression is needed now, because the Mac App Store is a failure you need to force the hands?