Local Network Privacy breaks Application

Question

Created 5d

Replies 3

Boosts 0

Participants 2

With the new macOS 15, Apple introduced the new Local Network Privacy feature. This is causing issues for our customers as - even though they granted the required permission for our software - connections to a server in their local network are being blocked. The situation is not fixed by recent macOS updates.

As far as I know, this issue exists for machines running on Apple Silicon. Systems running macOS versions (e.g. Sonoma) are not affected.

Currently, the workaround is to re-enable the permission under Settings > Privacy & Security > Local Network. The list shows our application with an enabled checkbox. Users now have to de-select the box and then re-select it again for the application to work. They have to do this after each and every reboot of their system, which is slightly annoying (so at the moment we recommend to not upgrade macOS to Sequoia, if possible)

I did some research and saw that other products are also affected by this bug. Is there a solution to this issue or any plans to fix it?

Boost

Answer 1

DTS Engineer OP

Apple

4d

Have you filed a bug on this? If so, what's the bug number?

__
Kevin Elliott
DTS Engineer, CoreOS/Hardware

0

Answer 2

AdvoSimon OP

3d

Thank you for your reply - and the help on filing a bug report. I created one now: FB16112111

0

Answer 3

DTS Engineer OP

Apple

1d

Thank you for your reply - and the help on filing a bug report. I created one now: FB16112111

Looking over your bug, the one thing that did jump out at me is that this is a Java application. Java application tend to use "launcher" architecture, where the executable (often a shell script) the system is initially launching is NOT what actually end "running". It's possible that you're bundle is laid out in a way that's causing the system to incorrectly treat your app as a "new" app every time it's restarted. What does the console log show when you launch post-restart and the system denies authorization?

Also does, is your app quit before the restart occurs or is it running when you start the restart process? If it's the second case, make sure the issue still happens if you specifically quit your app before the restart.

__
Kevin Elliott
DTS Engineer, CoreOS/Hardware.

0