I can run sudo /usr/local/sbin/acrossd from the terminal and it works perfectly, but if it's instead launched from launchd, it runs for a second and then exits with a return code of 255. I tried reinstalling. I've tried granting acrossd various System Preferences>Security & Privacy permissions, like Full Disk Access, Input Monitoring, Developer Tools. I've tried adding PATH environmental variables to com.clixon.acrossd.plist, or even have reattach-to-user-namespace execute acrossd. I've tried having launchd execute /usr/sh -c /usr/local/sbin/acrossd. Unfortunately, I only first installed across center after having already upgraded to 10.15.2, so I have no idea if the issue is actually related to this new version of macOS, or not. Oh, just in case it's relevant, instead of using homebrew to install firstname.lastname@example.org, I actually already had it installed via macports, so I just created a symbolic link from /email@example.com to /opt/local, which seems to work fine. (Homebrew and macports don't play well together.) I just want acrossd to launch automatically, without having to launch it manually from the terminal. Any advice would be appreciated!