missing package product

That sample doesn't quite work out of the box. Here is how you can get it to work on macOS 26 with Xcode 26 (and earlier versions of both, but that's what I'm using). Download the sample from https://developer.apple.com/documentation/driverkit/communicating-between-a-driverkit-extension-and-a-client-app?. Follow only some of the directions under Configure the sample code project: (turn off SIP) - skip this, it is no longer necessary Set Automatically manage signing for both the driver and the app targets Select a development team. Xcode will tell you that you cannot select an individual for this type of signing. ignore the advice about Sign to run locally and AD_HOC_CODE_SIGNING_ALLOWED. ignore all the other stuff. You don't need to make profiles, add capabilities, manually download profiles or add them to Xcode. Now go the Build Settings for the driver and app target, and change the Product Bundle Identifier. The download project uses a disambiguation string that doesn't work, and you end up with ve

We are setting the expiration header as following apns-expiry=0, so from my understanding it should not be delivered if the device was not able to receive the notification in the first attempt. Theoretically, yes, it does that and it certainly does better than setting a longer expiration. However... I have read the following thread https://developer.apple.com/forums/thread/778512, from which I understand this is a long-standing issue. Yes, it is. If you haven't already, please file a bug on this and then post the bug number back here. As part of that bug, please note how long you think a push submission should last after our server receives it before being discarded. For example, is 15s too long? I'd like to get this fixed this year and additional bug reports help drive that process. Hence my question is, is there any way we can notify the call kit that the call is actually no longer valid, and do not display the call to the user at all? No, there is not*. You can report the call and immediately end it, but t

I tried many things, but I can't seem to be able to pass through the check to allow the application to communicate with the dext. What am I missing? So, as it happens, I have a post here that's specifically about getting this sample to work. Try what that post suggests and let me know if you're still having issues. __ Kevin Elliott DTS Engineer, CoreOS/Hardware

Apologies I am now having troubles getting this to recreate again even using the exact same submission. I will keep trying and hopefully get you something you can work with. What do you consider building with Apple tools? This is our process for building as we are a golang application developed outside of xcode. For each inner PKG: create universal binary sign and verify the binary codesign --sign Developer ID Application: --deep --timestamp --options=runtime codesign --verify --verbose build and sign the inner pkg pkgbuild --root ConcealBrowse.pkg --scripts --sign Developer ID Installer: --install-location /Applications --identifier io.conceal.helper --version pkgutil --check-signature signed-installers/ConcealBrowse.pkg Notarize and staple the PKG xcrun notarytool submit --key --key-id -i ConcealBrowse.pkg --wait xcrun stapler staple ConcealBrowse.pkg After we repeat the above process for all three of our inner PKGs I build and sign the Distribution PKG

Until you have a release in production, access to the production APIs is not allowed. Once you have a release in production this will be unlocked.

The key error here is the could not be extracted one. The fact that the package couldn’t be extracted explains the has no signed executables or bundles failure. You’re building this package with Apple tools, right? If so, I’m gonna have you file a bug against the notary service. Include the notary log and a copy of the package that you submitted. Once you’re done, reply here with the bug number and I’ll take things from there. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

To quote every domain expert, ever: It depends |-: The full answer depend on how your framework is packaged, how the third-party library is packaged, and how it uses that third-party library. For example, imagine that the third-party library is packaged as a non-mergeable framework within an XCFramework. In that case, the Xcode build system can only record a reference to that framework. It can’t embed the code from that third-party library in your framework because it only has access to a dynamic library. OTOH, if the third-party library ships as a static library or framework, a mergeable library or framework, or a Swift package, Xcode could potentially merge the code into your framework. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

[quote='864815022, deteam444, /thread/805996?answerId=864815022#864815022, /profile/deteam444'] issue … was cause by a previously installed … iOS version of the very same app [/quote] Oh, wow. That makes sense [1], but it’s not something I would’ve thought of. Thanks for the titbit. [quote='864815022, deteam444, /thread/805996?answerId=864815022#864815022, /profile/deteam444'] at the moment the app is distributed on our own with Developer ID signing + notarizing. [/quote] OK. In that case you need to get on to the sysex train, because we only support appex packaging in Mac App Store apps. Again, TN3134 is a key reference here. I really need to write up a doc that explains… oh wait, Past Quinn™ has done as a solid here! See Network Extension Provider Packaging. Finally, watch out for the pitfall described in Exporting a Developer ID Network Extension. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com [1] TN3134 explains how ma