file uri scheme

There are no known issues around this in Xcode 26. If you are using XCTest UI Automation style tests, please ensure you are accessing environment variables set in a test plan from your test runner process and not from the process of an app-under-test. If you believe this is a regression, please file a Feedback with Apple and include the .xcresult bundle from Xcode's Report navigator if possible.

We parse the locationID out of the AVCaptureDevice.uniqueID and then find the IORegistry node with that locationID. Is there's a document declares how AVFoundation generate the unique_id for USB camera, no so I can assume this convert will always work? you can't Or is there's a way to send a PTZ control request to AVCaptureDevice? not that I know of. As far as I know, the only way is what you're doing. It looks that the unique_id provided is (locationID<<32|VendorID<<16|ProductID) as hex string, but I'm not sure if I can always assume this behavior won't change. Correct - it has changed in the past, it might change at any time in the future. Not all AVCaptureDevices are UVC, but they all have uniqueIDs. If you would like an API to clearly identify an AVCapture device in the IORegistry, please file a bug. I already did (in 2019, FB6146541)

Hi @thanhnd24 Yes, to use the entitlement (in your case, main camera access), you need to include both the entitlement and a corresponding license file in your app. After Apple approves your app for one or more entitlements, you receive a license file, along with additional instructions. People who are part of the Apple Developer Program are eligible to apply for the Enterprise license; an Enterprise account is not a requirement. For more information on obtaining and configuring the license, see Building spatial experiences for business apps with enterprise APIs for visionOS. Refer to Accessing the main camera for more information on using the main camera API.

Please file a feedback report with your store files and a sysdiagnose.

This is unexpected. Please may you file a feedback report with a sample project exhibiting this issue.

Hi @iOS-LI, Please file a feedback at https://feedbackassitant.apple.com and post the number back here. You should expect the first time you connect to any device to take a bit of extra time to load symbols but that should only happen once. From your description it sounds like it happens quite often. A feedback will help us track down and prioritize your findings. Thank you

Hi Kevin, Thank you for the suggestions. We have conducted a test of your third proposal regarding the IOKit User Client Class Temporary Exception. Our test procedure was as follows: We started from a known-good baseline commit where our DEXT loads correctly and the/dev/diskX node appears (though it reports 0 bytes, which is a separate issue we are debugging). We made only one change: we updated our App's .entitlements file to include the temporary exception. For absolute clarity, the exact content of the .entitlements file used for this test was: com.apple.security.temporary-exception.iokit-user-client-class IOUserUserClient com.apple.security.app-sandbox com.apple.developer.system-extension.install After a full clean, build, and reboot, the IOServiceGetMatchingService(DriverKitAcxxx) call still fails at runtime, returning IO_OBJECT_NULL. This result seems to indicate that the temporary exception entitlement is not sufficient to grant our app visibility of the active IOKit service on

Hello @alexander295, It would be helpful to file a feedback for this issue at https://feedbackassitant.apple.com. Once you do, please post the number here. Thank you

Thanks for the reply, yes Radar filed with ID: FB20611108

When a Binary Data attribute is marked as “Allows External Storage”, large image files are stored as separate files on the device rather than inline in the SQLite store. That is correct. There is a threshold when the data will get stored in external files next to the SQLite database, similar to the approach that you described with URLs, but that process is managed by CoreData and transparent to your app you. How effective is this mechanism in keeping the Core Data store size small on the device? It depends on what you mean by the store. The SQLite file will be smaller, but the files are still stored on the device. Are there any recommended size thresholds or known limits for how many externally stored blobs can safely be managed this way? There is in general no limit. CoreData will decide when it's worth using an external file. If the blob you are storing is only a few bytes, it'll remain inline. If you expect to have a lot of assets, you should consider h