
When a schedule starts, those prompts suddenly appear, referencing an invisible application called Copy Job. #bigmessĪnd it will be individual developers that will be left to try and work around Apple’s rushed decision making and half-assed implementations. Given Mojave b9 created a whole NEW set of display problems in app (none which existed in any prev beta) does not give me encouragement that Apple will fix #AEpocalypse in time or in a user-friendly manner. Or, alternatively, Apple understood this but development was way behind schedule and, for no discernible reason, it decided to rush ahead rather than take the time to get it right for macOS 10.15.
EVENTSCRIPTS APPLESTORE PRO
That is impossible to square with the idea that it understands and cares about pro users. Apple did not seem to be aware of how disruptive this would be for developers or how much it will degrade the user experience for customers. The general idea of AppleEvent sandboxing is not a bad one, but the rollout was botched.
EVENTSCRIPTS APPLESTORE PROFESSIONAL
But it’s unclear what changes are still in the pipeline - and whether Apple can make enough progress before Mojave’s public release.Īpple has been talking a good game lately about the Mac and professional users, but actions like this either make it seem like mere talk or point to division within the company. The addition of new APIs in beta 7 telegraphed that Apple is still working on it. And there are still no release notes for Foundation, Core Data, and other frameworks besides AppKit.ĪppleEvent sandboxing, as of Mojave beta 9, is not in a good shape.

What’s up with the documentation this year? We’re now on beta 9, but Apple hasn’t mentioned this important stuff anywhere but the headers. Instead AESend() will return errAEEventWouldRequireUserConsent. If the AppleEvent sent that way would require user consent, the user is not prompted for consent. MacOS Mojave beta 7 introduced AEDeterminePermissionToAutomateTarget, a new API that allows apps to determine whether they’re authorized to send an AppleEvent to another app: OSStatus AEDeterminePermissionToAutomateTarget( const AEAddressDesc* target,Īlso new in macOS Mojave beta 7 is kAEDoNotPromptForUserConsent, a flag that can be added to the AESendMode that’s passed to AESend(). AEDeterminePermissionToAutomateTarget Added, But AEpocalyse Still Looms
