missing package product

Thanks for following up, and apologies for the delay-- this slipped past me. Here’s a repro asset I wrote that you can test directly: https://github.com/alexchuber/Assets/raw/refs/heads/main/Repros/triangleNegScale.usdz For additional reference, here's the USDA content of the asset (material omitted for clarity): #usda 1.0 ( defaultPrim = Root metersPerUnit = 1 upAxis = Y ) def Xform Root { def Mesh Triangle { matrix4d xformOp:transform = ( (-1, 0, 0, 0), (0, 1, 0, 0), (0, 0, 1, 0), (0, 0, 0, 1) ) uniform token[] xformOpOrder = [xformOp:transform] int[] faceVertexCounts = [3] int[] faceVertexIndices = [0, 1, 2] normal3f[] normals = [(0, 0, 1), (0, 0, 1), (0, 0, 1)] ( interpolation = vertex ) point3f[] points = [(0, 0, 0), (1, 0, 0), (0, 1, 0)] uniform token subdivisionScheme = none } } The steps to reproduce are just: Add the asset to a new Reality Composer Pro scene. Open the same asset in QuickLook on iOS/macOS. Compare the facing direction in both views. You should see that the triangles appear to have opp

Yeah! It's working! I have a macOS 26.0 host. In UTM I have a macOS 15.7 guest with a Provisioning UUID that has never been added as a device in the developer portal. In my developer account I added a new device with the guest VM's UUID. It's the longer style with lowercase hex digits. I then edited my existing manual provisioning profile with the new device. In Xcode (26.1 beta 2) I changed my app's signing from automatic to manual and referenced the updated provisioning profile. I built the app and copied the new app to a share I use for the VM. I ran the VM and tried to run the updated app. It failed. I missed one step that maybe some others might miss. In Xcode, go to Settings, Apple Accounts. Select your account. Then select your team. Then click on Download Manual Profiles. Once I did that, I rebuilt the app with the now properly updated provisioning profile and recopied the app to the share. And now the app runs in the guest VM! Key steps for those that are not starting from scratch:

I was asked to follow up on FB19449747 after this was supposedly fixed, so I did. I can't see a DriverKit PCI Transport (development) entitlement in the list of available Capabilities. Huh. Can you double-check on the portal just to be sure? I've checked on three different teams I have access to, and all of them are showing it. A few things to note: It's actually called DriverKit PCI (development), simply to keep the name length a bit more manageable. I just noticed that it doesn't currently include the extra Development only. Learn more Provisioning support required. label on the portal (I'm working on fixing that). I also noticed that it's offering iOS as a platform, which turned out to be one example of a much broader bug (r.162380702). It turns out that several DriverKit entitlements also include extra platforms, which means they can be included in targets they should not be included with. I don't think including them will actually cause any problems (macOS will just ignore them), but it's definitely some

Having the same problem. I am using my MacBook as a hotspot over ethernet. I can get it to upload the app once and it will work. Also when I am debugging my app, Xcode will lose connection to the watch the moment the watch screen goes dark.

To troubleshoot product failure, see TN3186: Troubleshooting In-App Purchases availability in the sandbox.

Update seems like this was related to the Notary service being unavailable. It has since resolved itself and my Distribution PKG is being notarized like normal. It would be useful if in the future we could get more actionable error messages to know what is happening.