AppleScript changes in CoreTunnel 4?

Core Tunnel Ask for Support
1

My existing AppleScript from 3.x doesn't work in 4.0.1. Expected class name but found identifier on the word tunnel (after first) in:
set tun to a reference to (first tunnel where name = (item 1 of argv))

This is breaking my workflow, so I plan to downgrade back to 3.x until I can get a working AppleScript setup with 4.x.

2

Starting with version 4.0, Core Shell/Tunnel integration has migrated to Shortcuts and no longer supports AppleScript.

Fortunately, it’s still possible to invoke Shortcuts from AppleScript, for example:

set resultText to do shell script "shortcuts run 'My Shortcut'"
display dialog resultText

You can send me a private message and attach your desensitized AppleScript script, and I can try to help you convert it to Shortcuts actions.

3

So will it still be possible to run things from command-line with parameters (specifically, the tunnel name) passed in? Because that's how my current stuff functions.

Also, I have 3 scripts: check connection status, connect, and disconnect. Will all of those be convertable?

4

I received your private message along with the three AppleScript scripts. Since these scripts don’t contain any sensitive information, I’m replying in this post so we can openly discuss how to migrate from AppleScript to Shortcuts.

The three AppleScript scripts are used for:

  1. Connecting a tunnel
  2. Disconnecting a tunnel
  3. Checking the tunnel connection status

I created three corresponding Shortcuts and shared them here:

  1. Connect Tunnels

    image
    image1284×692 65.9 KB

  2. Disconnect Tunnels

    image
    image1270×684 66.5 KB

  3. Check Tunnel Status

    image
    image1270×1092 98.8 KB

Calling them from the command line is quite simple:

shortcuts run 'Connect Tunnels' -i '<tunnel-name>'
shortcuts run 'Disconnect Tunnels' -i '<tunnel-name>'
shortcuts run 'Check Tunnel Status' -i '<tunnel-name>' | cat
5

Seems to work, but a couple pieces of feedback:

  • Running the shortcut brings the app to the front, which disrupts the focus. I have it in menubar-only mode, so it also ends up adding the icon to my dock. Ideally it would be able to run the shortuct without focusing the core tunnel app
  • When connecting/disconnecting, it doesn't wait for the tunnel to connect/disconnect before returning from the shortcut, which means if my script immediately tries to do something with the tunnel after connecting, it fails because the tunnel isn't ready yet. I've worked around this for now with a 1-second pause at the end of the connecting shortcut, but ideally it would wait for the connection to be established before returning.
6

Will change to allow run in background in next update.

7

Version 4.0.2 now executing connect and disconnect operations triggered from the Shortcuts app in the background.

You can use a timed loop to check the tunnel connection status, determine if it is successful, and return. Refer to the 3rd script for checking the tunnel status. Let me know if you need a complete boilerplate script.