if((sd = socket(PF_INET, SOCK_STREAM, 0)) 1) { perror("Socket Creation"); //log_msg(LOG_ERR, "Socket creation failed"); return ERROR_SOCKET; } if ( connect(sd, addr, sizeof(addr)) == 0 ) { conn_success = 1; break; } else { log_msg(LOG_ERR, "errno = %d, %s", errno, strerror(errno)); } The above chunk of C code is used to open TCP sockets on public and private servers on many platforms including Android and Mac OS. On iOS, it works if the device, an XR running 14.4.2, has an internal IP address when connecting to a public server. However, if the XR has a public IP address as it does when not connected to wifi, it fails with this in the log calling the same public server (or any public server) and errno = 1, Operation not permitted: Sandbox: extension name(5616) deny(1) network-outbound*:port no Why does the network extension, a packet tunnel provider, connect to a public server when the device has a private IP address and denied network outbound access when it has a public IP address?

I got the message in the title when I made a new provisioning profile for this year which has a privileged file operations profile because the old one expired and the Mac app wouldn't build. Before this, I also had to get new Mac installer and Apple distribution certs which I would assume are in the prov profile since I made it after the new certs. After importing the new prov profile, the app builds, but app won't run because of message in title. I also had to do this in 2020 and 2021, but creating a new prov profile and importing it into XCode was all I had to do - everything just worked. In Xcode the 2021 and 2022 profiles look like they have the same content except the 2022 one isn't expired and has the latest cert. So why am I getting "Message from debugger: Terminated due to code signing error" when updating it this year? Larry

I have a Packet Tunnel Provider that works ok in development, but fails calling NETunnelProviderManager.saveToPreferencesWithCompletionHandler with "permission denied" upon being opened by App Review. If it means anything, I just switched my account from personal to company/organization so I could distribute a VPN app, and the app is signed with an Apple Distribution cert created for the company. The provisioning profiles for the container app and the extension are both signed with this cert and both have Network Extensions and Personal VPN entitlements. What is missing that is preventing the distribution to the App Store from working properly?

I have had content blockers in the Mac App Store for years. Ever since moving to Sonoma, doing a clean build or archive in XCode deletes the extension from Safari settings since it never gets into the built app. The only way for me to get it back is to remove the DerivedData and target, reboot, and create a target with a different name. That works and stays around in Safari settings as long as I only build and don't clean. However, a clean or an archive removes it again. Restoring a version of the project from Time Machine that was posted to the App Store weeks or months ago doesn't work. However I can download the version of the app in the App Store, and it works, but I can't build it now from the source code that was used to build that version without going through the above process. Moving from Sonoma 14.7.1 to 14.7.2 didn't work. I would move to Sequoia if I had reason to believe that would work, but I don't. Safari 18.2, Sonoma 14.7.2, 32GB, 2.2 GHz 6-Core Intel Core i7