Programmatically passing files to Final Cut via Apple Events

Is your app sandboxed?

If you move MyEvents.fcpxml to the home directory and then use /Users/JohnDoe/MyEvents.fcpxml, does that fix things?

Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"

Hey Eskimo. Good to see you in this thread! :-)

Moving the file to /Users/JohnDoe/MyEvents.fcpxml does not help. Same error still occurs.

Application is sandboxed (the default configuration when you create a new XCode project). The app in its current test form does not interact with the file at all. It just tries to tell Final Cut Pro to open it.

Here is the most simple version of the code we are trying to make function:

struct ContentView: View {
    var body: some View {
        VStack {
            Button {
                callScript()
            } label: {
                Text("Open file in Final Cut")
            }
        }
        .padding()
    }
}

func callScript(){
    let scriptSourceToSend = """
tell application "Final Cut Pro Trial"
    activate
    open POSIX file "/Users/user/somefile.fcpxml"
end tell
"""
    let script = NSAppleScript(source: scriptSourceToSend)
    var error: NSDictionary? = nil
    let result = script?.executeAndReturnError(&error)
    if let error = error {
        print("Error executing AppleScript:", error)
    } else {
        print("XML file imported successfully.")
    }
    if result == nil { }
}

The app in its current test form does not interact with the file at all.

Ah, interesting.

Normally when you pass a file reference via an Apple event the system adds a sandbox extension so that the destination app can access it. It won’t be able to do that if your app doesn’t have access to the file in the first place.

If you temporarily disable App Sandbox on your app, does that help?

Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"

If you temporarily disable App Sandbox on your app, does that help?

Yes, when I disable app Sandbox completely, there is no privilege validation error

Normally when you pass a file reference via an Apple event

I would assume so for the native file object. I did not know this was the case for POSIX file as well.

I also tried to put the file into ~/Movies and in Targets -> Signing & Capabilities -> App Sandbox -> File Access -> Set Movies folder to Read/Write. This still produces the privilege violation error.

when I disable app Sandbox completely, there is no privilege validation error

OK. Do you need sandboxing to be enabled? If not, disabling it is clearly the easiest path forward (-:

Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"

Do you need sandboxing to be enabled? If not, disabling it is clearly the easiest path forward

Well.. I don't but Apple does. At least for the Mac App Store :-)

Say we want to distribute Workflow plugin for FInal Cut Pro in Mac App Store. WeI need to comply with requirements (sandboxing) or get some sort of exception. I hear exceptions can be very hard to get.

I don't but Apple does.

*chuckle*

Say we want to distribute Workflow plugin for FInal Cut Pro in Mac App Store. WeI need to comply with requirements (sandboxing) or get some sort of exception.

I’m not super familiar with these plug-ins. Are they loaded within the Final Cut Pro app process? Or are they built as an app extension?

I hear exceptions can be very to get.

That’s my understanding as well.

Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"

I’m not super familiar with these plug-ins. Are they loaded within the Final Cut Pro app process? Or are they built as an app extension?

You can read more about them here https://developer.apple.com/documentation/professional_video_applications/workflow_extensions

However the problem with sending Apple Events and Sandboxing is not directly related to Final Cut extensions. Right now we are just trying out the basic process with a generic macOS app created via Xcode template where we (try) to follow the instructions from Apple and make it work.

What would you recommend we do next? Should we open a new DTS ticket about this specific usage of AppleEvents Vs. App Sandboxing?

I don’t think there’s a way to do this from a sandboxed app. In a non-sandboxed app you can send kAEOpenDocuments ('odoc') Apple events as you wish. However, the App Sandbox restricts that path, on the assumption that apps will use the facilities provided by NSWorkspace.

This isn’t an AppleScript-specific thing; if you use Apple events to send the 'odoc' event directly, you bump into the same restriction. For example, the code snippet below works in a non-sandboxed app but fails in a sandboxed one.

I recommend that you file a bug against that doc, requesting that it call out that NSWorkspace is required for a sandboxed app. Please post your bug number, just for the record.

Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"

func openInTextEditAE(_ urls: [URL]) {
    do {
        print("will open")
        let target = NSAppleEventDescriptor(bundleIdentifier: "com.apple.TextEdit")
        let ae = NSAppleEventDescriptor(
            eventClass: AEEventClass(kCoreEventClass),
            eventID: AEEventID(kAEOpenDocuments),
            targetDescriptor: target,
            returnID: AEReturnID(kAutoGenerateReturnID),
            transactionID: AETransactionID(kAnyTransactionID)
        )
        let directObject = NSAppleEventDescriptor.list()
        for url in urls {
            directObject.insert(NSAppleEventDescriptor(fileURL: url), at: 0)
        }
        ae.setParam(directObject, forKeyword: keyDirectObject)
        _ = try ae.sendEvent(options: [.waitForReply], timeout: 5.0)
        print("did open")
    } catch {
        print("did not open, error: \(error)")
    }
}