“We are unable to process your request”

Dear Quinn, In February 2021, when an Entitlement was added to Team ID WEJZZZZZZZ, I received the following email from Apple and learned how to add the Entitlement to a provisioning profile: Hi, Does Apple add entitlement to my team ? (== App ID: WEJZZZZZZZ) Yes, the entitlement was actually added to your “team”. That gives you the ability to add the entitlement to any app that’s managed by your “team”. Here is the configuration information you can use to check the current status and/or configure your own project: -To use the entitlement, you need to codesign your app with a provisioning profile that includes it. In the Apple developer portal website, you’ll need >to do the following: In the “Provisioning Profiles” section, click the “+” and to create a new profile In the “What type of provisioning profile do you need?” section, select “iOS App Development” Walk through the creation process and directly after the “Select devices.” section, you should see a new section titled “Do you need additiona

> I have a custom hardware board that I want to communicate serially with from an iPad. Should I use the DriverKit route or the MFi route? Depends on exactly what your needs are and the hardware you're working with. Starting with MFi, the biggest advantage is that the software side (ExternalAccessory framework) is far simpler to use and includes support for background access (DriverKit does not). The main downside is that it requires a certain amount of custom hardware and the certification process. Comparing it with DriverKit is... complicated. The software side of DriverKit is FAR more complicated. To start with, the DriverKit API is a somewhat odd derivative of the IOKit kernel API. For someone who's familiar with IOKit, it's similar enough to be understandable, but for a new developer, the learning curve can be quite significant. None of this is helped by the fact that DriverKit is poorly documented[1], to the point that my standard advice to new developers is to study the IOKit kernel API (wh

Do I need to submit the code-level support like everyone else too? These are my request Id 7P8645AYBX 3JW6U957WD 8B2943ZAUY

Your code that wraps UIActivityViewController with UIViewControllerRepresentable and presents it in SwiftUI looks good to me. I've tried running the code on my iOS simulator (iOS 26.2 23C54) and here is the behavior I see: When sharing one single item, the code demonstrates the behavior as I described. When sharing two items (by using var shareItems: [Any] { [textItem1, textItem1] }), the Save as field isn't editable, and so there is indeed no way to specify the file names. Also, two files are generated, one for each item. So it's not that the way you present UIActivityViewController has anything wrong; it's that UIActivityViewController doesn't allow you to specify the file names when sharing multiple items. I don't see any way that can change the behavior because the UI of UIActivityViewController is system-provided. Please feel free to file a feedback report to request the feature you would like to have. For now, you might consider sharing one single item, if that is appropriate to your use case.

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