missing package product

The problem is, if I try to archive the app, I will get the previous warning message as an error: Xcode 14 and later require a DriverKit development profile enabled for iOS and macOS. Visit the developer website to create or download a DriverKit profile. Any idea what I'm missing? So, as background, DriverKit has the most complicated code-signing configuration on our platform, which means its support in Xcode has lagged behind other technologies. This has been further complicated by a lack of documentation on the newer development only flow, along with misinformation/misunderstanding around what Xcode's errors actually mean. However... the good news is that I don't think you actually need to deal with this. More specifically, if you're: Using Xcode 16+. You've only been granted 1 entitlement value for a given family (this is true for you). ...then automatic code-signing should Just Work™. Here is what I would do next: Change the configuration of all targets from manual to automatic. Hit build and the

Is our inability to have a Target ID greater than 0 fully probed by macOS a bug in our own code, or could there be another reason we are unaware of? It's a bug in your code. If we do indeed need a one-after-another creation mechanism for AsyncCreateTargetForID, what is the correct way to implement a chained creation using OSAction completion handlers in DriverKit? You do NOT need to do this. The snippet in our documentation has a model of one event per ID, but our production DEXT is just using a single call with a set of nested loops checking IDs and calling UserCreateTargetForID. In terms of what could be going wrong, a few thoughts: Looking through the method list, what do you return for UserReportHBAHighestLogicalUnitNumber? If you didn't implement it or return 0, then I think you'd get exactly the behavior you're seeing. Make sure you check this first, as this is the best idea I've come up with. Look at your iig and audit it for QUEUENAME. Most DEXTs use VERY few of these and they shouldn't be on

Thanks for the quick feedback, super appreciated. I tested this suggestion, and the result seems to be much closer to what I was expecting. But, to my eyes, it looks like the .exr lightmap loses a lot of dynamic range. Please see the two images attached below, where the lower sofa uses a normal png texture map where both texture and lighting is baked into the BaseColor texture in Blender, while the upper sofa uses the tiled fabric texture as BaseColor with the exr lightmap multiplied using the Image(vector3f) approach you suggested. The loss of dynamic range in the .exr multiplied as Image(vector3f) is quite apparent.

I just ran into an issue where NSScrollView got stuck mid scroll. I answered in another thread here: https://developer.apple.com/forums/thread/748826?answerId=865833022#865833022 My simple override of scrollWheel: fixed the issue for me but I do lose the rubber band bounce back effect shouldn't be too hard to implement it but I'd rather not right now. I'll give up the rubber band bounce back in exchange for having a scroll view that doesn't freeze mid-scroll. I tried overriding +isCompatibleWithResponsiveScrolling and returning NO but it was never called on my NSScrollView subclass for some reason.

SceneKit is soft-deprecated and we suggest using RealityKit if you are thinking about making new games. To learn how to bring your existing SceneKit projects to RealityKit, see Bringing your SceneKit projects to RealityKit. This article and sample code project are associated with the WWDC25 session Bring your SceneKit projects to RealityKit. If you see any issues bringing over your projects to RealityKit or see any missing features, please file a request via Feedback Assistant.

Thanks for the context @psqv , I understand better now what you are trying to do. Can you try sampling both images, your base color and your light map, using Image(vector3f)? Then multiply those values together, then use a Convert node to convert the product from Vector3f to Color3f before piping the color value into the unlit surface node. Image(float) will create grayscale because that only samples one channel, so I'd consider what you are currently seeing to be expected behavior. If using Image(vector3f) does not work, could you please send us feedback using Feedback Assistant, and then share the ticket number here so I can track it down on our end. Thank you!

I second this and agree that a OS level solution should be investigated as the software's functionality seems to have been broken on OS level. Even though official xquartz support was abandoned some 10 years ago, xquartz continues to be used on Apple systems in many productive work environments.

Thank you for following up on this and I did submit a bug report with the specific PKG submitted 78407997. However thanks to you and the notary developers I do believe I found the problem within my Distribution.xml I went and synthesized a new Distribution.xml using productbuild --synthesize --package ConcealConnect.pkg --package ConcealUpdate.pkg --package ConcealBrowse.pkg Distribution.xml and I did notice that the result was drastically different from what I had. The main difference is that the synthesized PKG does not by default show the choices to the user so that they can pick and choose what parts of the software distribution get installed. When I had added this capability I foolishly also added a second for every single PKG and this one did not contain the #. So what I think was happening is because of this poor Distribution.xml implementation sometimes everything would work fine because the proper instantiation was first in the file and other tim

Hello, Thank you for the quick and in-depth reply. I will dig into the unlit shader for Petite Asteriods and see if I can modify it to suit my needs. I will do my best try to explain what I am trying to do in more detail. My plan is to separate BaseColor texture and baked light and use a tiling UV set (st) for BaseColor and an unwrapped non-overlapping UV (st1) set for the baked lightmaps. This way texture resolution (and the surface detail) will not be dictated by the lightmap resolution, allowing for closeup viewing of surfaces without losing detail, while preserving the baked light for shading. This would allow for creating much more realistic environments that take advantage of the fantastic resolution of the VisionPro, combined with beautiful prebaked light. This is the way baked light works in Unity and Unreal Engine. I was expecting to be able to do this by baking out the lightmaps as exr with base 1, so that dark areas of the lightmaps would, when multiplied with the BaseColor texture darken

Even more annoying is that XCode 26.1.1 doesn't recognize any of my older platform installations. To work around this, I tried to boot and use an iOS 26.0 simulator still on my Mac but XCode refuses to acknowledge that it exists. Even if I use the Devices & Simulators window to create a new iOS 26.0 device, XCode will not let me use it without having iOS 26.1 downloaded first. With all of the 26.1 beta issues with the simulators reported on these forums over the last 2 weeks, it's insane to me that this was still pushed out to production in such as broken state.