missing package product

Thanks for the clarification about Developer ID vs Apple Development and for the links. Previously I started with Developer ID and the dns-proxy-systemextension entitlement, but per your advice I’ve now switched both the host app and the DNS Proxy system extension to Apple Development signing and the legacy dns-proxy value. Current Apple Development setup macOS: 15.7.3 (24G419) Xcode: 26.2 (17C52) Host: com.example.agent.MyMacProxy DNS Proxy system extension: com.example.agent.MyMacProxy.dnsProxy System extension entitlement: xml com.apple.developer.networking.networkextension dns-proxy System extension Info.plist (built .systemextension inside the host app): xml NSExtension NSExtensionPointIdentifier com.apple.system_extension.network_extension NSExtensionPrincipalClass MyMacProxy.DNSProxyProvider There is no NetworkExtension key in this plist (confirmed with plutil -p on the built .systemextension in both DerivedData and /Applications). The system extension is embedded at: MyMacProxy.app/Contents/Library/Sy

OK. I don’t think you can optimise beyond that. Rather, I think you should use that as a baseline for performance work as you evolve your program. Speaking of that, An Apple Library Primer has links to various WWDC talks where the linker team discusses various topics. Most notably, the 2022 talk discusses launch times. It’s well worth a watch. Finally, just for context, the libSystem initialiser does a bunch of really critical stuff. For example, it has the code that sets up the App Sandbox, if the executable enables it. If you want to see this initialiser in action, open your true clone project, set a symbolic breakpoint on libSystem_initializer, and run it from Xcode. When you stop at the breakpoint, Xcode will show a page of disassembled code, but that’s not too hard to understand. And most of the symbols are present, so you can look up the source code in Darwin. IMPORTANT The Darwin open source isn’t guaranteed to match the source used to build the OS, but it’s usually close enough to be quite instructive

Each system log entry has time to live (TTL) value. You can see evidence for this in various places within the UI. For example: % sudo log stream … TTL … 0 fseventsd: (libsystem_info.dylib) Resolve user group list … … 7 WindowServer: (SkyLight) [com.apple.SkyLight:KeyboardEvent] kCGSEventKeyUp … AFAIK there’s no supported way to override that, but if you poke around in /System/Library/Preferences/Logging on your Mac it’s not hard to see how it works. WARNING As with all implementation details, there’s no guarantee that this will actually work, or that it hasn’t worked differently in the past, or will work differently in the future. So don’t build knowledge of this into a product that you ship to a wide range of users. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

Good morning, thank @DTS Engineer for your comment. The fact that we have been able to solve our problem does not mean that the logic of the system functions has changed since iOS 26.2. For this reason, we would like to know if this loss of functionality is going to be consolidated or if Apple will restore coverage in later versions of iOS. @DTS Engineer could you please give us an answer? Thanks.

But the funny thing is, I just tried to reproduce it again because you requested the sysdiagnose logs and ... today the issue is gone. The helper now works just fine on this Mac too. This is speculative, but this is a kind of thing that happens when there are issues with the LaunchServices database. That database is how the system maps bundle IDs to file system locations, which can obviously be a problem if/when something goes wrong in the database. These issues often have exactly the kind of pattern you’re describing— something stays broken quite persistently, then suddenly starts working for no apparent reason. I have an extended post about this sort of issue here, however, the two points I’d pull from that post: While I've seen these issues happen to many developers, they're much, MUCH rarer on end-user systems. The unique dynamics of the development process are the single biggest factor here. The fact this keeps happening is a side effect of LaunchServices’ basic role, NOT a lack of attention or maintenan

I asked Gemini about marketing a free iOS app two weeks ago, and it said Product Hunt is the one to use. You have to keep your account for at least one week to have your app profile posted if I remember correctly. What they do is publish a new letter every day, which will be sent out to subscribers, I think, to feature software products. I haven't had my iOS posted there. So don't trust me and take my word for it.

Can't say for sure which steps you are missing, but something in your list of actions must not be connecting: create App ID select PN capability create Provisioning Profile for the app if signing automatically, let Xcode select the appropriate profile if signing manually download the profile and install it into Xcode That should be the process.