build disappears

No, its not there. That's one of the things that is so confusing. Not in the build but still generates an error.

Thanks @DTS Engineer for your quick & detailed answer!! So, my immediate question here is what your larger goal here actually is? 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. This won't work. The primary goal of the App Sandbox is to protect user data, which is exactly the kind of data you want access to. Yeah, that was also what I suspected. Hence my question what the intended way to access files from an app would be. apps get access to files through one of two broad mechanisms: Thanks for referring to these, I think I stumbled upon it while researching, but did not consider them further yet because they are solutions that require editing the code in Xcode. Which poses two problems for me: 1 - I don't have a lot of experience with Swift and how Xcode apps are structured. 2 - The Xcode project is generated from Unity, s

@xcc-developer I filed a feedback request and attached the Xcode Cloud diagnostics that contain the build logs. The feedback request number is FB20676007

Hello! Could you file a feedback report in Feedback Assistant and attach the built app products? You can find the built products in Xcode’s Derived Data folder, to which you can navigate by selecting Product > Show Build Folder in Finder from Xcode’s menu bar. Please include details about the specific target device or simulator that’s experiencing the issue and reply to this thread with the feedback ID so that we can follow up. Thanks!

Is there a supported way to clear per-app consent so the system prompts again? There is no supported way to achieve the desired functionality given the currently shipping system configurations. If you would like for Apple to consider adding support for such features, please submit your suggestion request via Feedback Assistant. For more information on Feedback Assistant, please visit https://developer.apple.com/bug-reporting. Under what conditions should the “Share Age Range Again” control appear in Settings, and is there an equivalent way to trigger it for testing? It appears prior to the anniversary of the original request, and when a user previously declined or a user has aged out of a current age range. Are there best practices for QA (e.g., using Ask First at the system level, testing on real devices vs. Simulator, using a separate bundle ID for dev builds, or other steps)? Testing in the Simulator is unsupported. If you use a separate bundle ID, the system treats it as a different app. Any othe

Part 2... That leads to here: and how can I make sure my app will be allowed to update when I need it too. The first thing I'd do here is shift the way you're thinking about this issue from how do I remove/bypass quarantine to how do I make sure my update process always works. You've focussed on quarantine because it's a fairly common edge case; however, the problem with focussing on solving it is: The system’s behavior is opaque and undocumented. This means, as you're already experiencing, it's hard to make this work right at all, and even if you succeed, it's very likely that something will change in the future, leaving you back with the same problem. Quarantine is only one failure source of many. For example, what if the actual problem is that the app is being run from a read-only location like a network share? That second point is what makes this problem so tricky. The full range of valid macOS configuration is so large that it's effectively impossible to fully test or predict. This means you end up trapp

Thanks again @RickMaddy I nicely added items to the File Menu using your example. As it turns out I was way overthinking this. I thought there would be a unified menubar in multitasking, not a per window one. This is much simpler and answered my, where is it in Vision, question. I don't really know how I missed this point in the intro video. The only other note I will point out for any other dinosaurs following along is that this line [super buildMenuWithBuilder:builder]; only works with supers that are UIResponder subclasses. So if you started your project in iOS 4.x your AppDelegate might still be an NSObject subclass, and you should upgrade to eliminate some build warnings.