We are unable to process your request

Hello, Is it possible to perform your processing on the texture in place? If I understand your question properly you should be able to 'lock' your texture, run a kernel over the data in that texture then 'unlock' the texture and use it to draw, having never converted to CGImage. Discover Metal 4 along with the sample code: Processing a Texture has the Metal 4 way to do this kind of thing. Here is another sample that shows a similar approach in RealitKit: https://developer.apple.com/documentation/visionOS/generating-procedural-textures-in-visionos Please post back here if I've misunderstood your question.

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 macOS. Be

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 how you expect your app to behave when the use

I was able to change the age rating by making minor changes to my original app, checking “Yes” for the “Unrestricted Web Access“ question, uprating the age to 18 yrs and resubmitting. The app has no objectionable materials and aimed at adult and teen windsurfers and kite-boarders. This process seems a bit contrived, but it worked for me. Not sure it was necessary to actually change the code. Re-archiving and validating the original code may have been enough.

I would like to know the answer to this. I want to integrate Visual Intelligence in processing text using my application from screenshot UI entry point.