build disappears

I have a small update, when upgraded to Xcode 26 (instead of Xcode 16), the appclip did not build right away. The reason was Apple has changed how we need to create the .entitlements files. So I had to do the following: com.apple.developer.parent-application-identifiers - $(PARENT_APP_IDENTIFIER) + $(AppIdentifierPrefix)com.mydomain.parentID i.e add AppIdentifierPrefix + parentID instead of PARENT_APP_IDENTIFIER With this fix, the appClip got build with Xcode 26. My issue with appClip invocation is not yet fully fixed, but hope this will help someone. Let me know if someone found a better solution. Note: I have seen it works in some phones with iOS 26 (like iPhone 14) when I use the appClip code (circular code), but not with plain QR code, and that too not on all phones (still not works on 14 pro max). But once it works on a given phone, it worked on normal QR code too (weird, I know). My best guess is that it' a cache issue.

Hey there! I saw your post about trying to hide the Save to another device option during Passkey registration—and I’m dealing with the exact same issue right now! We’re building a financial app, so restricting Passkey creation/use to the current device is non-negotiable for security and compliance reasons. I noticed your post was a bit back, so I wanted to check: did you ever figure this out? If you did, any little tips or fixes you could share would be a total lifesaver. Thanks so much in advance!

The Info.plist in my Extension is: Is that the actual value? Or did you substitute this line in: com.example.example-extension I've tried tracking your build down on the App Review side but there have been a number so submission and it looks like they've all been approved, so I'm not sure where to find the build that's being rejected. __ Kevin Elliott DTS Engineer, CoreOS/Hardware

To be more clear than my post from August 2025, the solution is to rebuild all of your upstream dependencies with a version of XCode that includes the same version of clang that your version of XCode includes. The easiest way to be sure that upstream and your app uses the same clang is to build them both with the same XCode. If you rely on a library that you cannot rebuild, you need to file a bug with the maintainer for them to do that rebuild. Until those things have ALL been built with the same version of clang, you will not be able to see code coverage data.

Kevin and ssmith_c for your assistance. I fortunately managed to file in the bug: FB20677188 Thank you! Looking over the bug, there was one point I wanted to comment on: For the Matter Media Device Basic Video Player Type Apple Home does support the commissioning (adding the device to the list of accessories displayed in Home App), but no controls are displayed. Not even the mandatory required controls: ... This type of Matter Device, which is part of the standard, should at least expose the mandatory controls and commands. The idea that Apple (and general ecosystem vendors more broadly) should try and support the full range of the Matter specification is, IMHO, one of those ideas which sounds reasonable on the surface but is, in fact, a very bad idea. First off, quoting myself: The Matter specification itself is sufficiently broad and complex that, in practice, I'm not sure it will ever really be possible to create a high-quality controller app* that actually supports EVERY possible accessory configuration i

I am working on a Gaussian Splatting App using the UnityGaussianSplatting package and building for Apple Vision Pro. I want to be able to load splat (.ply / .splat) files from the Vision Pro's storage into the application. OK. So the main issue to be aware of here is the difference between works fine for a developer and works well for a user. For development purposes, you can basically just set the two keys (UIFileSharingEnabled/LSSupportsOpeningDocumentsInPlace) and then use your Documents directory as your working storage. There could be issues if you edited or deleted those files while your app was actively running, but you will just avoid those issues... by not doing that. On the other hand, if you're planning to ship this to end users then you'll need to use things like file coordination to avoid those issues. Similarly, apps that are more viewer oriented (meaning, they don't edit the files they're working with) often use an import model where they copy (actually clone, so they don't use additio