Post not yet marked as solved
To clarify my use case: my app is an e-reader app focused on Biblical materials, with a cross-referencing system that can surface content from any downloaded books related to any verse or entity (people, places, things, ideas). There are lots of atlas-like resources with maps of the ancient near east in Biblical times, and it would be amazing to be able to select the name of a city on a map image and feed it into my existing functionality to find content related to that city name - verses, encyclopedia articles, etc.
[edit: this should have been a comment, but now I can't find a way to delete this "reply"]
Post not yet marked as solved
I ran into this on Xcode 13 building and exporting a Mac app as Developer ID. At first I had the issue "You haven't been given access to cloud-managed distribution certificates" and that led to a Stack Overflow question that said I had to get my Team Agent to give me access to cloud-managed Developer ID certificates in App Store Connect. I did that and then got this error - the provisioning profile that Xcode generated for the app during export didn't include my Developer ID certificate in my keychain.
What eventually fixed it was deleting the Developer ID certificate out of my keychain. Then Xcode used the cloud-managed certificate that was in the provisioning profile that it generated.
I would advise exporting the Developer ID certificate before trying this, though, in case you need it back for some reason.
This is now solved with a new API in iOS 15.
https://developer.apple.com/documentation/uikit/uideferredmenuelement/3857602-elementwithuncachedprovider?language=objc
I got an answer to this elsewhere. The enabling or disabling of the Siri capability (and others) is actually stored in the project's Entitlements file. So I duplicated my existing Entitlements file, removed Siri from it, and set that Entitlements file as a variation for the macOS SDK in the project's "Code Signing Entitlements" build setting.
I actually figured this out with the App Store Connect UI. In my scenario above, when adding the introductory offer, it displays "every 6 months for 12 months". I'd attach a screenshot here if the forums allowed images.
Same issue here. Probably worth a feedback. I've filed it as FB8285319.
Post not yet marked as solved
I have the same issue. I tried making a new project in Xcode, started with the single-view app template, put one button in the middle of the screen, and tried to record tests and click on it. Recording appeared to start, but no output was recorded. Tried both Objective-C and Swift tests, and I set an accessibility identifier and label and such on the button in IB.
Post not yet marked as solved
I just discovered that, at least in iOS 13 beta 4, WKWebView doesn't automatically set the Content-Type header to application/x-www-formurlencoded for POST requests the way UIWebView does. Could that be the issue?
Post not yet marked as solved
It may be because AirPlay doesn't allow you to use a persistent key. You have to check the canProvidePersistableContentKey property on AVContentKeyRequest, and/or check if it's an instance of AVPersistableContentKeyRequest, and if not, fetch a new key from the key server instead of using a previously downloaded persistent key. In AVAssetResourceLoaderDelegate-land, this was accomplished by checking if AVAssetResourceLoadingRequest's allowedContentTypes property (an array) contained AVStreamingKeyDeliveryPersistentContentKeyType.Also, try setting allowsExternalPlayback on your AVPlayer instance to NO. From my conversation with some AVFoundation engineers at WWDC 2018, this means that the audio will be streamed to the origin device, decrypted, re-encrypted, and re-streamed to the target device. I think this actually means you *can* use persistent keys for AirPlay. It also fixes an unrelated issue where old AppleTV hardware can't change playback speed.
Post not yet marked as solved
Turns out the reason I was having an issue with allowsExternalPlayback set to YES was that I was passing YES for AVAssetResourceLoadingRequestStreamingContentKeyRequestRequiresPersistentKey in the options passed to streamingContentKeyRequestDataForApp, even when persistent keys weren't allowed (i.e. AVStreamingKeyDeliveryPersistentContentKeyType wasn't in loadingRequest.contentInformationRequest.allowedContentTypes). Pass NO there or omit it from the options and everything works great.
Post not yet marked as solved
I asked about this in the labs at WWDC 2018. My scenario is playing FairPlay-encrypted audio, using persistable content keys for offline playback. Persistable content keys only work on iOS, so the AppleTV can't handle them. I was told to file a radar about getting an error back from streamingContentKeyRequestDataForApp. The reason turning allowsExternalPlayback to NO works is that it causes the iOS device to stream the audio, decrypt it with the persistable content key, then re-encrypt it and stream it over AirPlay. Happiness all around.
Post not yet marked as solved
I'm working on playing FairPlay-encrypted audio, supporting offline playback via persistent keys. When I try to AirPlay, I get an error that the AVAssetResourceLoadingRequest's contentInformationRequest's allowedContentTypes (iOS 11.2+) doesn't contain AVStreamingKeyDeliveryPersistentContentKeyType. It won't accept my persistent key. And when I try to request a non-persistent key from my KSM, I get an error back from streamingContentKeyRequestDataForApp:.Hilariously, if I set my AVPlayer's allowsExternalPlayback to NO, everything works.
Post not yet marked as solved
I have this issue in Xcode 9.2, trying to add an App Group to one of my apps. And the code using the App Group does not work for me. And the app group I'm trying to add gets listed twice when I select it in the list.
