I have a sandboxed Mac App Store app that uses Apple’s MultipeerConnectivity framework for a local peer-to-peer “mesh” feature.
The app advertises itself as a nearby peer and accepts inbound invitations from other nearby devices so users can do local collaboration, chat, shared workspace sync, and multiplayer game sessions. This is local peer-to-peer only; the app is not running a public web server, FTP server, or similar service.
When I remove the App Sandbox Incoming Connections entitlement:
com.apple.security.network.server
nearby peer discovery / inbound connections stop working in the sandboxed Mac build.
Is com.apple.security.network.server the correct entitlement for this MultipeerConnectivity use case on macOS, assuming the app clearly exposes this local peer-to-peer feature in the UI?
Is com.apple.security.network.server the correct entitlement for this MultipeerConnectivity use case
Yes.
Well, you should set both it and com.apple.security.network.client
Multipeer Connectivity is based on UDP and, as we call out in the docs, com.apple.security.network.server is required for UDP apps.
Having said that, Multipeer Connectivity was formally deprecated in Xcode 27 beta and thus not something I recommend for new products. Rather, my advice is that you switch to Network framework. See Moving from Multipeer Connectivity to Network Framework.
Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"