“We are unable to process your request”

Thanks for the post, hope some RealityKit experts jump quickly on this thread. However I wanted to be the first to tell you: Welcome to RealityKit and Metal! Transitioning into 3D graphics and procedural generation is exciting. Here comes my simple disclaimer. I’m not an expert at RealityKit, however I got before the tips that made my simple tests extremely successful and I would like to share those with you, if you require more in detail I would open up this thread to any RealityKit expert that wants to jump in here. When you add hundreds or thousands of individual rocks, trees, and bushes as separate RealityKit Entity objects, you are overwhelming the CPU. Even if the meshes are simple, RealityKit has to calculate the transform, bounding box, and physics for every single entity, every single frame, and then send individual instructions to the GPU. To fill dense background spaces without killing performance, you need to shift the workload. So, instead of creating 1,000 separate Entity bushes, you sh

I attach this log to the FB. Thanks for investigating. Failed to request default share mode for fileURL:file:///var/mobile/Containers/Data/Application/453B6EDB-3C76-4D2D-8355-702D4BD0263A/Documents/name%20accentue%CC%81.pdf error:Error Domain=NSOSStatusErrorDomain Code=-10814 (null) UserInfo={_LSLine=1796, _LSFunction=runEvaluator} Only support loading options for CKShare and SWY types. error fetching item for URL:file:///var/mobile/Containers/Data/Application/453B6EDB-3C76-4D2D-8355-702D4BD0263A/Documents/name%20accentue%CC%81.pdf : Error Domain=NSCocoaErrorDomain Code=256 The file couldn’t be opened. error fetching item for URL:file:///var/mobile/Containers/Data/Application/453B6EDB-3C76-4D2D-8355-702D4BD0263A/Documents/name%20accentue%CC%81.pdf : Error Domain=NSCocoaErrorDomain Code=256 The file couldn’t be opened. Received port for identifier response: <(null)> with error:Error Domain=RBSServiceErrorDomain Code=1 Client not entitled UserInfo={RBSEntitlement=com.apple.runningboard.process-st

@lateef Please file a code-level support request including your Team ID for assistance.

I have created a Feedback Assistant for this: https://feedbackassistant.apple.com/feedback/22266931 Prefect, thank you. Also created a Code-Level Support case, with the same title as with Feedback Assistant but it seems to be private. Yep. I've replied to that with a summary of the situation as well. Please inform if I may have missed anything. Everything looks good to me. At this point, I think you should ignore the issue and proceed with development. This warning won't have any effect on the certification process. __ Kevin Elliott DTS Engineer, CoreOS/Hardware

Unfortunately, it didn't seem to have the desired effect, and non-functional write actions still show up in places like the Finder :( (FB22267894) If your extension is receiving these actions or are they failing above you without ever reaching your extension? I want to differentiate between: The volume is mounted RW, so my extension gets requests it's not going to handle. The volume is actually mounted RO (blocking all modification), but the Finder isn't noticing that correctly, so it lets the user try things that can't work. I think you're seeing #2, but I want to confirm that. __ Kevin Elliott DTS Engineer, CoreOS/Hardware

In the callback, I can see that the failure occurs on a .DS_Store file inside the folder. So for a .DS_Store, it is simple enough for me to just ignore the error and return COPYFILE_SKIP, but the somewhat more concerning issue here is that the true error reason is seemingly not reported? In the callback, if I read errno, it is 0. When copyfile returns, it returns -1 after I return COPYFILE_QUIT (and errno is 0), so I don't know what the error is or the appropriate way to handle it. FYI, the code to copyfile is actually open-source, so you can fairly easily find all of the places where your callback would have been called by looking for COPYFILE_ERR in the source. However: For .DS_Store, just skipping seems reasonable, but when copying a folder, it may be appropriate to get the true failure reason. ...I'd ignore all .DS_Store errors and, potentially, just skip copying them all together. The system will generate the file anytime it needs/wants to, and it's very likely that it won't consider the copied file vali

You can see the status of your feedback in Feedback Assistant. There, you can track if the report is still being investigated, has a potential identifiable fix, or has been resolved in another way. The status appears beside the label Resolution. We're unable to share any updates on specific reports on the forums. For more details on when you'll see updates to your report, please see What to expect after submission. Albert Pascual
  Worldwide Developer Relations.

Thanks for the post, can you provide me the correct URL for the AASA file? the links above are not correct. If you prefer provide me this information in private. Go ahead and submit a code-level support request so we can discuss this further privately. When you create the request, indicate that you were referred by me at Apple and make sure to include a link to this thread. Thanks Albert Pascual
  Worldwide Developer Relations.

Hello - In order to resubmit your three IAP subscription products, the status of each needs to change from Developer Action Needed to Ready to Submit. We recommend editing each of them, in order to save an update (e.g.: add a note to the Review Notes section like [Date] Updating IAP to resubmit with new binary of Version 1.x of [App Name]. Once the status of the IAPs has been successfully updated, proceed to submit a new version of the app - and attach the three IAPs for review as documented here under Submit an In-App Purchase of the first time. If you are still unable to resubmit the IAPs with a new app build, please file a detailed ticket (including screenshots and/or video) via Feedback Assistant, and reply back to this thread with that ticket number - and we will follow-up. Thank you.