Open jordaniac89 opened 5 months ago
I've also given full disk access to the executable, launchctl, sh, bash, and zsh. Looking at it closer, it's probably an issue with MacOS itself and not navidrome, but let me know if anything stands out.
I found this https://stackoverflow.com/questions/58442951/how-to-fix-operation-not-permitted-when-i-use-launchctl-in-macos-catalina But it sounds like you've already taken that into account. How about the Terminal? You didn't say that the Terminal has full disk access...
I confirm that:
Version
v0.50.2
Current Behavior
When trying to run navidrome as a launchctl service, I receive a status code of 78. I get a launch log of
2024-01-17 21:56:29.449940 <Error> Service could not initialize: posix_spawn(/Users/jordanmiles/Documents/navidrome/navidrome), error 0x1 - Operation not permitted 2024-01-17 21:56:29.449950 <Error> initialization failure: 22G120: xpcproxy + 22544 [1097][D177A08D-D99B-3FFD-94E9-90882559A169]: 0x1
When I run the command outside of launchctl, it runs fine.
Expected Behavior
navidrome starts up correctly when running as a service
Steps To Reproduce
I'm using the standard plist file from the documentation. I've confirmed that the executable and the log files have wide open permissions for rwx. As mentioned, when I run the navidrome command from the command line, it works fine.
plist file below:
Environment
How Navidrome is installed?
Binary (from downloads page)
Configuration
Relevant log output
Anything else?
No response
Code of Conduct