Okay - turns out the Compressor 300 kbps limit is for the "Apple Device" presets. I guess folks must be tweaking the "Live Streaming" presets to get the desired 192 kbps rate...

I've been seeing this crash as well. That is, attempting to using a custom url scheme to retrieve an HLS key results in crash on simulator. iOS device appears to run fine, however.

I was able to stop the crash by adding KEYFORMAT="indentity" to the #EXT-X-KEY tag in the .m3u8 files. (I'm guessing the bug involves an Xcode assumption that we're using FairPlay for encryption when utilizing a custom url scheme.) Still can't get AVAssetResourceLoaderDelegate to fire in the Simulator, though...

Yep. No alerts in App Store Connect, however. Appears like a huge mistake...

I've been looking into this as well. You can add a custom header for your CDN rules via AVURLAssetHTTPUserAgentKey (and other non-official methods for < xOS 16), however, be warned some devices (ie. Roku) will strip the header out. See related discussion here: https://stackoverflow.com/questions/55945320/how-to-authenticate-an-airplay-session

Feedback report: FB13225766 (Xcode excessive CPU with interface builder (tvOS)). Includes sample project as per described above.

Not sure if related, but I'm seeing 100% CPU use on tvOS projects. Soon as I open up Interface Builder (storyboards), launchd_sim and PineBoard processes wind up and peg physical CPUs at 100%. On Intel MacBook Pro. Xcode latest release. iOS projects are fine. FB13225766

Minor update: Deleting "derived data" from ~/Library/Developer/Xcode changes behavior so that the processes causing high CPU use go away once closing Interface Builder or moving to view a text file. Returning to IB to view storyboards re-triggers high CPU use in all instances.

As I understand it, if a user installs your app on a new device and hits your purchase button instead of "restore purchases", there is a chance they would be double-billed if you have separate subscription groups for the same product. This would result in a terrible customer experience, to say the least. From Apple: "creating a single group is the best practice for most apps as it prevents people from accidentally purchasing multiple subscriptions." You can create a subscription offer in App Store Connect to attract legacy users for renewals. See: https://developer.apple.com/help/app-store-connect/manage-subscriptions/set-up-promotional-offers-for-auto-renewable-subscriptions/

I am seeing the same warning. Does not appear to affect my app so I am regarding it as an Xcode / tvOS bug. (Setting the Category to moviePlayback had no effect, either, btw.)

I am getting a "No internet connection" error in my TestFlight build. (Xcode sandbox works fine)

Having this issue with TestFlight internal builds. (Worked fine in Xcode sandbox)

Any progress on this? I have a subscription which I submitted too early (new app business model) and now it is locked. I uploaded a new binary, but am not sure how to "unlock" the subscription so I can add it to the app to submit for review...

I have the same issue. But it works perfectly fine with Xcode and sandbox users, so I figure it must be a problem with TestFlight (which is what the reviewers user, no?) At any rate, I figure if I get a rejection, I will pull the feature and use the old-fashioned "manage subscription URL" instead.

PS. Feedback case number is FB14835294