Cathy J. Fitzpatrick

The changing filename of the binary is not what is causing the permissions to need to be re-granted with each new build. See my other comment: https://github.com/LizardByte/Sunshine/pull/3348#issuecomment-2450859080.

Re: @00Dchapellebot, I can't determine what your problem is from what you're saying. However, unlike most permissions, there's no way that I know of to reset the state of the...

To help figure out if the local network permission is actually the culprit, try directly running the binary in the foreground of your shell in Terminal.app (rather than using a...

I'm now noticing a problem on my machine where sunshine **_can_** access the local network, regardless of whether it is granted local network permission! What this suggests to me is...

If running in the foreground makes no difference, it theoretically shouldn't be related to the local network permission, but as I said, my own tests establish that that permission is...

> It doesn't look like an issue regarding Local Network permissions, because with that the client was able to see the server but not connect and there was an error...

Just from reading what you wrote, it appears that you are attempting to use a different version of `libicuuc` than the version that Sunshine was linked against. The `ucnv_getMaxCharSize` symbol...

If you want to the the libraries already on your system, you should build Sunshine from source. That has a much higher chance of compatibility than randomly modifying the binaries.

You need to grant the responsible code, as determined by macOS, the microphone permission. This is probably the Sunshine binary, although it can vary, because we don't properly distribute Sunshine...

Loseless Scaling isn't free of cost, so I don't know if too many people are going to be willing to buy it to debug this issue, particularly when the open...