Autostart MacOS and aw-watcher-window

starting aw-qt from the terminal works fine for me, but when I try to create an automator app to launch aw on boot, I run into an issue with the aw-watcher-window.

In this image, you can see my attempts to launch aw from the automator application and terminal.

I have the automator app set up to run this:

/usr/bin/nohup /usr/local/bin/aw-qt >/dev/null 2>&1 &

When I start it with the Automator app, aw-watcher-window isn’t able to request access to control “System Events.app“. Even if I run the same in Terminal and grant it access, launching from the Automator app still won’t let aw-watcher-window get the access it needs.

The first time I run the app, osascript requests and is granted access to control “System Events.app“. Terminal and iTerm have also been granted such access.

Has anybody got aw running at boot on MacOS?

[ErikBjare]

This should be a lot easier with the upcoming .app bundle that will be available in v0.9, which should just be possible to add to the normal autostart applications in settings.

[xylix]

Fixed in v0.9.0