iPhone 16 pro

I am having a rare crash when calling FileHandle(forWritingTo:) initializer with a file that does not exist. In the documentation, I see that the expected behaviour is to return nil, but in my app, in rare cases I have a crash. You're passing in a URL object that's already been released. The key clue is here: Exception Subtype: KERN_INVALID_ADDRESS at 0x00000000deadbeef Exception Codes: 0x0000000000000001, 0x00000000deadbeef The address 0xdeadbeef isn't accidental. It's a sentinel value that the system commonly uses when it wants to set a pointer to something that's recognizably known to be invalid. In the particular case, CFURL's* deallocate function sets the pointer that points to the actual string bytes to 0xdeadbeef just before it returns. Your app crashes like this the next time you try to use that URL object. In terms of tracking the issue down, testing with ASAN or the Zombie’s instrument are your best options. *NSURL and CFURL share their underlying implementation. As an aside, and not directly releva

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 us

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

I tried some more myself and I was able to solve the issue by adding Apple Vision Pro to the Supported Destinations of the extension. Previously I had only added it to the main app.