When restarting a PC with macOS15, communication on the local network is denied for the target app even though "Local Network" in "Privacy and Security" is allowed.

Question

Created May ’25

Replies 2

Boosts 0

Participants 2

We are developing a desktop app for macOS, built with Electron + Angular + Node.js. The app has the ability to access devices on the local network. We are having some trouble with the behavior of the "Local Network" feature added in macOS 15.

Procedure: MacBook Pro 14inch (M1Pro) 2021, 16GB memory - macOS Sequoia15.4.1 Network Environment: The PC and the access point are connected by wire, and the target device and the access point are also connected by wire.

Not connected to an external network
1. Install the target app
2. Start the application and allow the "Local Network" dialog that appears
3. Open the "Local Network" item in "Privacy and Security" and make sure the target app is allowed.
4. Confirm that you can access the target device on the local network
5. Restart the PC
6. Open the "Local Network" item in "Privacy and Security" and make sure the target app is allowed.
7. Start the app and access the target device on the local network

Result: Access to the target device may fail (this does not occur 100% of the time) If you turn the target app in the "Local Network" section of "Privacy and Security" OFF and then ON, you will be able to connect

However, it seems that the problem may occur again if you restart your PC.

According to our research, the probability of this happening increases if the target app is the only app allowed on the "local network". This happens not only with our app, but also when you follow the above steps in "Google Chrome".

Based on the above investigation results, I suspect that this is a problem with the OS. What do you think?

Answered by DTS Engineer in 838762022

I suspect that this is a problem with the OS.

I agree.

In general, local network privacy shouldn’t change behaviour after a restart. However, I’ve seen various reports that it does, both in the case you’re reporting (restarting makes it fail) and in the opposite (restarting fixes things).

This happens not only with our app, but also when you follow the above steps in "Google Chrome".

And this is critical. It indicates that this problem is not specific to your app.

I encourage you to file a bug about this. Make sure to include a sysdiagnose taken shortly after reproducing the problem. Follow the Network Diagnostics for macOS instructions on Bug Reporting > Profiles and Logs to enable additional logging.

Once you’re done, please post your bug number here, just for the record.

Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"

Boost

Answer 1

DTS Engineer OP

Apple

May ’25

Recommended

I suspect that this is a problem with the OS.

I agree.

In general, local network privacy shouldn’t change behaviour after a restart. However, I’ve seen various reports that it does, both in the case you’re reporting (restarting makes it fail) and in the opposite (restarting fixes things).

This happens not only with our app, but also when you follow the above steps in "Google Chrome".

And this is critical. It indicates that this problem is not specific to your app.

I encourage you to file a bug about this. Make sure to include a sysdiagnose taken shortly after reproducing the problem. Follow the Network Diagnostics for macOS instructions on Bug Reporting > Profiles and Logs to enable additional logging.

Once you’re done, please post your bug number here, just for the record.

Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"

0

Answer 2

TakumiMorimoto OP

May ’25

Thank you for your reply.

Follow the Network Diagnostics for macOS instructions on Bug Reporting > Profiles and Logs to enable additional logging.

I installed the profile described in this procedure and tried to obtain a log, but the problem could no longer be reproduced when the profile was installed. I deleted the profile and checked to see if the problem could be reproduced again, and confirmed that it could be reproduced in this case.

the probability of this happening increases if the target app is the only app allowed on the "local network".

Our research has confirmed that the issue becomes less likely to occur when the number of target apps increases, but it is also possible that installing a profile will make the issue less likely (or not) to occur.

0