Once the connection is made it will appear as a MIDI destination. You need to send MIDI to this device using Core MIDI.

Why would my app not have permission to view the document when it's from the files app? Error Domain=NSCocoaErrorDomain Code=257 "The file “afile.pdf” couldn’t be opened because you don’t have permission to view it." UserInfo={NSFilePath=/private/var/mobile/Containers/Shared/AppGroup/xxxxxxxx/File Provider Storage/afile.pdf, NSUnderlyingError=0x281f4f150 {Error Domain=NSPOSIXErrorDomain Code=1 "Operation not permitted"}}

I understand that, but the share icon and open in.... should pass the document via the inbox right?

Here is the answer. There's an option to access the sandboxed url. Hope this helps others. Wrap your NSData call with this: BOOL isAcccessing = [url startAccessingSecurityScopedResource]; // access NSData here  if (isAcccessing) {                 [url stopAccessingSecurityScopedResource];   }

This is not working for me. I received approval and did the following. 1: I added the capability and it is there enabled in Certificates, Identifiers & Profiles->indentifiers->myID->additional capabilities->User Assigned Device Name is enabled,. 2:In Xcode 13 and later, once the capability is enabled for your App ID, you can configure Xcode to support automatic signing. In your app’s .entitlements file, add the assigned entitlement key and value pair. OK where is the key and value pair shown? In my Xcode provisioning/Xcode managed profile, I see "com.apple.developer.device-information.user-assigned-device-name" OK assuming this is the key and value as described somewhere online, not in documentation that I can, I put that into my entitlements file along with Boolean YES I get this: Automatic signing failed. Xcode failed to provision this target. Please file a bug report at https://feedbackassistant.apple.com and include the Update Signing report from the Report navigator. Provisioning profile "iOS Team Provisioning Profile: com.xxxxx.xxx" doesn't match the entitlements file's value for the com.apple.developer.device-information.user-assigned-device-name entitlement

Find the provisioning profile that Xcode is using. How do you find this? I thought whole point of automatic signing is to not have to do this manually. In any case assuming it's in ~/Library/MobileDevice/Provisioning Profiles I see a xxxxxx.mobileprovision file. But Inside Code Signing doesn't show any type of example using the mobile provisioning file. Incredible that it is this difficult to enable an entitlement. When I tried to open a TS for it, the default entry was a question about entitlement. Sorry that enabling something that Apple took away is so painful to enable.

Never mind, it's still not working

I don't get it. Where can I look at this? "iOS Team Provisioning Profile" Provisioning profile "iOS Team Provisioning Profile: com.xxxx.xxxxxx" doesn't match the entitlements file's value for the com.apple.developer.device-information.user-assigned-device-name entitlement

I tried downloading manually the provisioning profiles and it's there with "com.apple.developer.device-information.user-assigned-device-name" assigned to true.

OK I did what you said. Just to be clear, I am looking at the settings by doing a quick look (spacebar on the file) which seems to work! That is handy and I am seeing exactly the same: com.apple.developer.device-information.user-assigned-device-name:  true This is a copy of the text shown when doing a quick look on the dragged profile. And I haven't heard back from my technical support incident. The one that I pay for :-( Thanks!

Thanks. I just sent email.

So no answer as to the missing energy logs or the removal of this in instruments..... hmmmm

At this point it's completely embarrassing. Even if you PAY for the help, you get NONE. I appreciate Quinn's help but I paid for help and none came. I got the auto ack and that's it. NO FOLLOW UP NOTHING! They used to care. for real. I have the proof. Not anymore. I'm going to write Mr. Cook. You laugh, but I did before and got results fast.

I changed nothing and I just tried it again and it worked. So this matter is closed now.

Nothing. And no way to get clarification on what my app might be missing. Incredible.