0

macOS Mojave 10.14.6

I would like to be able to programmatically create repeating calendar events that open a given file when run. I'm using AppleScript within Automator. Creating the repeating events is not hard, but I cannot seem to add an Open File Alert. Is this possible?

I found this old post which was having the same problem and the nearest conclusion was that it's not possible for some inexplicable reason. Does anyone know how to accomplish this?

5
  • I see both a class and an element named "open file alarm" so... are you certain about this?
    – JVC
    Commented Jul 19, 2020 at 18:08
  • "This class represents an 'open file' alarm. Starting with OS X 10.14, it is not possible to create new open file alarms or view URLs for existing open file alarms. Trying to save or modify an open file alarm will result in a save error. Editing other aspects of events or reminders that have existing open file alarms is allowed as long as the alarm isn't modified."
    – CJK
    Commented Jul 19, 2020 at 18:11
  • Well damn... my Calendar dictionary doesn't say any of that. Just the very first sentence. How odd. Also I get no error of any kind.
    – JVC
    Commented Jul 19, 2020 at 18:12
  • No problem, thanks for helping me get to the apparent bottom of this, disappointing as it is. So close, and yet so far!
    – JVC
    Commented Jul 19, 2020 at 18:13
  • BTW, make this an answer if you want and I'll accept it.
    – JVC
    Commented Jul 19, 2020 at 18:42

1 Answer 1

1

Quoting Calendar's AppleScript dictionary in macOS Catalina (but applicable since Mojave) :

"This class represents an 'open file' alarm. Starting with OS X 10.14, it is not possible to create new open file alarms or view URLs for existing open file alarms. Trying to save or modify an open file alarm will result in a save error. Editing other aspects of events or reminders that have existing open file alarms is allowed as long as the alarm isn't modified."

Additionally, having tested other types of calendar alarms in Catalina that do not have similar warnings against them, they too failed to be created. Whilst the restriction in place for file alarms is most likely motivated by security concerns, the others feel more like a bug.

1
  • In case anyone sees this and wonders why they don't see the above message in their Dictionary, my Mojave dictionary does not contain this message, it contains only the first sentence. Maybe an artifact of having upgraded from High Sierra? I don't know... but it caused me to not understand why this wouldn't work until @CJK pointed it out.
    – JVC
    Commented Jul 24, 2020 at 13:27

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .