yo exits immediately i think. yo_scheduler had a 5 second timeout before it deletes the watch file. because it's a KeepAlive the yo notifications would post immediately, it would exit, launchd would wait 10 seconds before starting it again, which it did (displaying potentially two updates), but then the watch file would be deleted after five seconds, so it wouldn't start it a third time. avoid the file-exists-KeepAlive problem altogether by maintaining a WatchPaths path instead.
Also start our LaunchAgents in the background if there's a logged in user.
Change from KeepAlive to WatchPaths.
yo exits immediately i think. yo_scheduler had a 5 second timeout before it deletes the watch file. because it's a KeepAlive the yo notifications would post immediately, it would exit, launchd would wait 10 seconds before starting it again, which it did (displaying potentially two updates), but then the watch file would be deleted after five seconds, so it wouldn't start it a third time. avoid the file-exists-KeepAlive problem altogether by maintaining a WatchPaths path instead.
Also start our LaunchAgents in the background if there's a logged in user.