Why does this AppleScript cause a big delay in Mavericks?

Question

Level 1

0 points

Why does this AppleScript cause a big delay in Mavericks?

Hello,

I use FileMaker for my database needs. I have been using an AppleScript to create a calendar event from FM to my Calendar using Apple Calendar. This has worked flawlewssly in Mac oSX 10.7 and 10.8. Every since Mavericks, the script still works (creating no error) but takes about 1 minute to complete. The funny thing is that if I run the script from the AS editor, it works just fine. The FileMaker does have access to my calendar in the security area.

Any thoughts?

Here is the script that is invoked:

launchapplication "Calendar"

repeat until application "Calendar" exists

"delay 1"

end repeat

tell application "Calendar"

set my_event to make new event at end of events of calendar "Test Calendar" with properties {description:"Test description here", summary:"Summary Text here", location:"location information here", start date:date "Sunday, December 8, 2013 at 10:00:00 AM", end date:date "Sunday, December 8, 2013 at 12:00:00 PM", allday event:false}

end tell

Thanks!

Stephen

MacBook Pro, OS X Mavericks (10.9)

Posted on Dec 13, 2013 9:52 AM

Reply

Answer 1

El Gaucho Author

Level 1

0 points

Dec 16, 2013 3:17 PM in response to El Gaucho

Just tried this in 10.9.1 and it still causes a delay. Can't figure out why this is happening.

Reply

Answer 2

twtwtw

Level 5

4,936 points

Dec 16, 2013 3:24 PM in response to El Gaucho

try rewriting the first line like so:

tell application "Calendar"

launch

end tell

As it stands you're asing FileMaker to launch the calendar app, and that's not something that FileMaker really knows how to do. Elplicitly directing that command at the correct app may clear things up.

Reply

Answer 3

El Gaucho Author

Level 1

0 points

Dec 16, 2013 4:47 PM in response to twtwtw

Thanks but the issue still persists. I have found that when I run the file from within FileMaker Pro, it works just fine with no delay. When I run the same script in a FileMaker Runtime, I get the delay and the "tccd" file in the Mac OS processes spikes through the roof.

Reply

Answer 4

Hiroto

Level 5

7,461 points

Dec 17, 2013 1:50 AM in response to El Gaucho

Hello

I don't think you need the first four lines of code at all:

launch application "Calendar"
repeat until application "Calendar" exists
    "delay 1"
end repeat

Or, if they are really necessary for some reason I don't know, they should have been at least as follows:

launch application "Calendar"
repeat until application "Calendar" is running
    delay 1
end repeat

Note that it uses no quotes around delay statement and uses application's running property in lieu of exists command. The exists command with an application object as its direct parameter will implicitly launch the application in order to send the "exists" message to the application, which I don't think is what you intend here.

Regards,

H

Reply

Answer 5

El Gaucho Author

Level 1

0 points

Dec 17, 2013 5:57 AM in response to Hiroto

Thanks, I did modify this and the aplescript works as planned. However, the issue that I am facing is that when I run this AppleScript from within my FileMaker application, it works perfectly and quickly. No issues. FileMaker allows me to create a Runtime version of the software. When I use the Runtime version with the same database and AppleSCript, I get this long delay and spike in the "tccd" process in Activity Monitor. This is where I can't find an answer. The Runtime does have permission to access the Calendar application so I am completely stuck. This leads me to believe that it is more of a FileMaker Runtime issue in Mavericks than with AppleScript since this worked just fine under 10.8.x.

Any other thoughts or considerations?

Reply

Answer 6

twtwtw

Level 5

4,936 points

Dec 17, 2013 6:18 AM in response to El Gaucho

From what I gather, tccd is a daemon associated with account security. Maybe the Runtime applets (or whatever they are) are having a sandboxing problem? You might want to check with FM support.

Reply

Answer 7

Hiroto

Level 5

7,461 points

Dec 17, 2013 7:38 AM in response to El Gaucho

Hello

It seems tccd daemon is doing something about tccd.db which keeps track of applications allowed to access contacts database.

See these links for some information:

What the **** is TCCD?

https://discussions.apple.com/thread/4165543

Mac Operations

http://macops.ca/modifying-the-tcc-db/

I don't use 10.7 or later systems and so cannot be of any help here.

Regards,

H

Reply

Answer 8

El Gaucho Author

Level 1

0 points

Dec 17, 2013 7:51 AM in response to Hiroto

I foudn the same info regarding tccd and the contacts database. it seemed weird that this databse would be accessed since I was using the AppleScript to access calendar. (Calendar did request permission to allow access). I have deleted the tccd database and still the issue persists.

Reply

Answer 9

moonrise

Level 1

0 points

Dec 30, 2013 6:53 PM in response to El Gaucho

I'm seeing the same thing. FileMaker Pro 10.0v3, OS X 10.9.1. My FM script generates and runs AppleScript to add a Calendar entry. Takes around a minute under Mavericks, took a second or two in previous OS versions. Process tccd eats CPU.

Reply

Answer 10

_Ÿ_

Level 1

0 points

Jan 7, 2014 9:13 AM in response to El Gaucho

I'm facing the same issue. I noticed that it works fine for local calendars… iCloud calendars seems to have a different behaviour. Is this the same for you ?

Reply

Answer 11

El Gaucho Author

Level 1

0 points

Jan 7, 2014 9:32 AM in response to _Ÿ_

Hello.

I am using iCloud calendars and my results have been mixed. I am now calling the calling script via a shell script terminal command to see if that would help. So far it has been working better but not ideally. Before the applescript would run instantly, now it's dropped from the 1 minute time frame to about 10 seconds to almost 5 seconds. But again my results have been mixed.

Not sure if that hehlps. I wish I had more info from FileMaker on this.

Reply

Answer 12

moonrise

Level 1

0 points

Jan 7, 2014 4:00 PM in response to El Gaucho

The same script, when run from the AppleScript Editor rather than FM, takes a few seconds rather than minutes. This has been very consistent for me.

I don't have any non-iCloud calendars, and the option to create one seems to have vanished in Mavericks :-(

Reply

Answer 13

_Ÿ_

Level 1

0 points

Jan 8, 2014 12:45 AM in response to moonrise

set myCal to "MyLocalendar"

tell application "Calendar"

set l to the title of every calendar

if myCal is not in l then

set n to uid of (makenewcalendarwith properties {name:myCal})

end if

end tell

🙂

Reply

Answer 14

moonrise

Level 1

0 points

Jan 8, 2014 4:49 PM in response to El Gaucho

Thanks!, so I made a local calendar as above, and changed my FM script to use it. But alas, it still takes minutes to run, just as with iCloud calendars.

Reply