build disappears

Ah, yes, Chrom{e,ium}. There’s definitely something weird going on there, but I’ve yet to see a definitive answer as to what it is. It certainly isn’t as simple as ‘local network using build UUIDs for everything’, because if that were the case then all apps would lose their local network privacy privilege after every update. However, it’s also true that the network subsystem uses build UUIDs in ways that I’m not super happy with. [quote='859253022, poluyanov, /thread/800879?answerId=859253022#859253022, /profile/poluyanov'] a new …/Versions/A.B.C.D folder with the updated version is added [/quote] Wha? You’re relying on framework versions? That is… well… not what I’d do. That’s not been best practice for a long time, and our docs are now clear about that. Is the local network call being made by the process running your app’s main executable? Or by, perhaps, a helper tool embedded in this framework? Is this issue causing grief for your users? Or only during development? After reproducing the

Having same issues. App Icon show up on device and under builds (Included Assets), but not visible in the App Store app on device or App Store Connect. Feedback: FB20338606

We have a customer reporting a bunch of problems with our (Transparent Proxy Provider-based) suite. Looking at a sysdiagnose, I see that our GUI applet was killed: Termination Reason: Namespace PORT_SPACE, Code 14123288431434181290 (Limit 305834 ports) Exceeded system-wide per-process Port Limit Looking at the top.txt file from it, I see that it has 193,086 ports -- compared to about ~250 on one of my test systems. So, let me just say that crashing like this is the BEST possible outcome for an issue like this. Mach port communication is so fundamental to the system’s function that Mach port leaks can basically break anything in your app. Crashing is the good failure here, as that is much easier to investigate than hangs randomly in different places for no apparent reason. Has anyone run into this? Yes, I've seen Mach port leaks before. Historically, they were a consistent long-standing source of bugs through the entire system. Indeed, one of the major reasons XPC exists was to provide a slightly higher-level

Thanks for your response Quinn @DTS Engineer . You’re correct, my VPN isn’t based on a Network Extension provider, but I do use a Transparent Proxy to divert some traffic outside the tunnel. Based on your suggestion, I’m considering building entirely on the NetworkExtension framework with two providers: NETransparentProxyProvider – intercepts app sockets so I can decide what to bypass. NEPacketTunnelProvider – encapsulates and encrypts the rest according to my VPN protocol. My goal is that each TCP/UDP socket first reaches the Transparent Proxy callback, and if diverted to the tunnel, then it flows the data through the Packet Tunnel provider for encapsulation before hitting the physical adapter. Is this the expected pipeline when both providers are active ? Thanks !

[quote='859098022, kallookoo, /thread/801301?answerId=859098022#859098022, /profile/kallookoo'] you can't manage certificates without being a paying member. [/quote] Correct. Usually this isn’t a problem because Xcode’s automatic code signing takes care of everything for you. But it certainly does make it harder to investigate weird issues. Are you actually having problems running your app? Or are you solely concerned with the presence of this extra certificate that you can’t delete? If it’s the latter, I think that this’ll fix itself. Eventually this certificate will expire and thence disappear from the list. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com