Re: Mavericks: Long lag making new events in Calendar app
Re: Mavericks: Long lag making new events in Calendar app
- Subject: Re: Mavericks: Long lag making new events in Calendar app
- From: Andrew <email@hidden>
- Date: Wed, 13 Nov 2013 03:34:06 -0500
Thanks for the response!!
> >The more relevant one is Security -> Privacy -> Calendars...
> > Could the prompt be hidden by the script activating some app or other?
I have no idea what might hide it on every Mac running Mavericks in the office.
I haven't been able to get a prompt asking me to authorize the AppleScript Editor or FileMaker pro to access calendars.
Is there a plist to toss to reset it or any way to manually add an app to the list, perhaps from the Terminal?
> > And I would *guess* that the same proviso about access to Accessibility and the need to consider code-signing or at least removing write
> > permissions from the executable applies here.
On one of the Macs I experimented with applets and with scripts executed from the script menu… Didn't mention it because I was trying to avoid a TMI problem…
When executing applets, there *are* prompts to authorize access to calendars and regardless of the fact that an applet has been approved to access calendars, I get sandbox errors in the Console: "Not entitled to send an AppleEvent to this process."
When executing authorized applets ( per: http://support.apple.com/kb/HT5914 ) the sandbox errors persist.
When executing the script from FileMaker Pro or the Script Editor, I'm *not* getting sandbox errors. There are no log entries corresponding to running the scripts from FMP or the Script Editor.
…
One more potentially relevant piece of info:
I've observed the calendaragent process dramatically kicking up its CPU activity -- hitting over 80% CPU in the Activity Monitor -- while the Calendar app beachballs. When the Calendar app settles down and the event has been successfully added, its activity drops back to 0.0%… So it's grinding away at *something* ...
...
I'm not convinced that the beachballing is related to sandboxing. Why would sandboxing affect only the time that it takes to execute the command? It takes no time at all to add an event to a local calendar, but 45 seconds or more to add an event to a CalDAV or Exchange calendar. Does that have the feel of a sandbox issue?
'Anything else you can think of for me to check?
…Thanks again!
-Andrew
On Nov 13, 2013, at 1:22 AM, Shane Stanley <email@hidden> wrote:
> On 13 Nov 2013, at 3:09 PM, Andrew <email@hidden> wrote:
>
>> * Each Mac has the Script Editor, SystemEvents, SystemUIServer and FileMaker Pro added to the list of apps in "Security & Privacy" > Accessibility.
>
> Unless your apps use GUI scripting, that setting is irrelevant. The more relevant one is Security -> Privacy -> Calendars.
>
> (I just tried to view the Calendar dictionary in Script Debugger's Explorer, which is the same as scripting it, and I got a dialog asking for permission; when I said yes, it was added to the Security -> Privacy -> Calendars list.)
>
> Could the prompt be hidden by the script activating some app or other?
>
> And I would *guess* that the same proviso about access to Accessibility and the need to consider code-signing or at least removing write permissions from the executable applies here.
>
> --
> Shane Stanley <email@hidden>
> <www.macosxautomation.com/applescript/apps/>
>
_______________________________________________
Do not post admin requests to the list. They will be ignored.
AppleScript-Users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
Archives: http://lists.apple.com/archives/applescript-users
This email sent to email@hidden