ScriptingBridge with Swift - Communicating with Apps using AppleScript and Swift

AppleScript is a great technology on macOS for both developers and power users. It allows users to create automated processes which work other apps. As a developer though, sometimes you want a build an app in Xcode with the power of AppleScriptwithout the need to have separate script files. To work with AppleScript in any app, there are two options to do this:

  1. Write a separate AppleScript file and use the NSAppleScript API to execute and run the script.
  2. Use ScriptingBridge to work with AppleScript in Swift or Objective-C.

We are going to look at the second option: ScriptBridging. In particular, how to use ScriptBridge in Swift wihout the need for AppleScript files or event Objective-C bridging.

The Drawbacks of ScriptBridging

It should be noted if you intend to write an App for the Mac App Store there are restrictions as noted by Apple. You can also look at this article by Craig Hockenberry which shows how you can use the AppleScript API in a Mac Store app. The bottom line is: You can not use ScriptingBridge with an app in the Mac App Store.

Objective-C ScriptBridging to Swift ScriptBridging

When it comes to Objective-C ScriptBridging, Apple already provides tools to prepare the code. Luckily, Tony Ingraldi of Majesty Software, has a great set of python scripts for creating the same code in Swift. For more details on this specifically take a look his repo on GitHub or his blog post here.

ScriptBridging with Safari

Now let's try doing this by writing an app which pulls the tab urls out of a Safari window. The repo for this app can be found here.

Building the Swift Code from AppleScript Definition

Download the python scripting tools from the SwiftScripting repo on GitHub. From the repo's directory, run the following commands:

pip install clang sdef /Applications/ > Safari.sdef sdp -fh --basename Safari Safari.sdef ./ Safari.h ./ Safari.sdef

Let's break this down:

  1. pip install clang - ensures clang is installed for python
  2. sdef /Applications/ > Safari.sdef - gets the scripting definition from the specified script- able application
  3. sdp -fh --basename Safari Safari.sdef - transforms a scripting definition to an Objective-C header file
  4. ./ Safari.h - transforms the Objective-C header file to Swift
  5. ./ Safari.sdef - extracts the enums from the standard definition to Swift

Now you should have 4 new files:

Since we are using only Swift code, we will only need the two Swift files (Safari.swift and SafariScripting.swift) in our application. Add the two files to your project in Xcode and now in our application we can talk to Safari.

Using the ScriptBridging API for Safari

To pull the all Safari windows currently open:

if let application = SBApplication(bundleIdentifier: "") { let safariApplication = application as SafariApplication let safariWindows ={ $0 as? SafariWindow }) ... }

We call the SBApplication constructor using the bundle identifier. If an object is returned, we cast as the SafariApplication protocol and get all the windows. The

windows property only returns a SBElementArray, so we need to cast those elements to a SafariWindow. From there we can get the window's set of tabs:

let safariWindow = safariWindows?.first let safariTab = safariWindow?.tabs?().firstObject as? SafariTab let url = safariTab?.URL

Let's break this down:

  1. let safariWindow = safariWindows?.first - get the first Safari window
  2. let safariTab = safariWindow?.tabs?().firstObject as? SafariTab - get the first tab of the Safari window and cast it to SafariTab
  3. let url = safariTab?.URL - get the url of that particular tab

If you need more details checkout the repo for the sample app called jURLnal which copies the URLs to the clipboard.


So as you can see -

  1. We have used the standard ScriptBridging tools to build the standard definition and Objective-C header file of Safari’s AppleScript API.
  2. We used a set of python scripts from Tony Ingraldi of Majesty Software to convert the Objective-C header file and standard definition to Swift code.
  3. Added the two Swift files to our project and used the API to extract the windows and tabs of the currently open Safari application.

If you have any questions, comments, or thoughts, be sure to post a comment below in the disqus forum. If you are looking for a speaker on an Apple development topic or need help with your current macOS app project, feel free to contact me at our form here.