Sequoia's "Local Network Privacy" is far and away one of the most half-baked "features" Apple has ever added to macOS.

When updating to a major new version of Sparkle (in this case, v2.7.x), I typically like to test my new app update locally on my LAN before deploying the app to our Server. I have a light Apache web server (complete with Sparkle AppCast and new app build) running on a Linux box on my LAN for just this purpose. I manually change the app's SUFeedURL to grab the Sparkle AppCast from http://192.168.1.10/whatever, do an Xcode build, and run my test. This has worked perfectly fine for years, up until Sequoia.

With Sequoia, the stupid "Local Network Privacy" blocks my app from accessing my Linux box on my LAN. So the AppCast can't be downloaded, and Sparkle fails out. It's not possible to manually add apps (in my case, new Xcode compiles) to Sequoia Security's "Local Network Privacy". My only options seem to be to:

1. Use the Apple Dev portal to apply for the Multicast Entitlement (com.apple.developer.networking.multicast) which my app DOES NOT NEED

• or -

2. Manually launch my app from Terminal to test it. This works, but it's only a matter of time before Apple closes this as a Security hole. Plus, I can't debug my app from within Xcode if I encounter any problems.

Does anyone have any thoughts on how to work around this annoying problem? For example, is there some way for my local Mac to host Sparkle's AppCast and new build? Or is it possible to run an Apache server locally, but somehow trick Local Network Privacy to think the server is outside of my LAN?

Thanks.