Any progress here? I'm looking into if it's possible to get around a similar issue - perhaps if it's possible to disable https for dns.

I'm having ongoing similar problems with the Mac mini 2018 I got two years ago (in 2020). For these two years hdmi and thunderbolt cablr both leave the screen unable to turn on after startups from turned off state, or starts from sleep state. The latest release of macOS 12.3.1 seems to actually have fixed the thunderbolt connection part such that the screen turns on properly (tested a few days for now, it seems stable so far). However with 12.3.1 the hdmi connectivity is not fixed and the problem is still there; I assume hdmi connectivity is not addressed (usb-c/thunderbolt is). But the bigger problem with 12.3.1 now is the computer is "half bricked". Many of the times the computer freezes halfway or a few minutes after boot. And when it freezes it reboots after awhile and then after finally being able to log in it complains about some system extension being unloaded, and that it saw panic mode. Mind that I had the OS completely replaced with a fresh macOS install just a few days ago when this same computer came back from Apple support. I'm so tired of this Mac Mini 2018 joke that has been haunting me for two years.

I've also seen that HLS-AES seems broken since iOS 16.

seems like this might be fixed as of iOS 16.1 beta 4. But please don't take my word for it and test yourself. In any case users would have to wait for the final release of iOS 16.1 but this seems promising.

For some reason I just got it to work. The weird thing is I first started the companion iOS app on the iPhone, and then while still running that app on the iPhone, I switched scheme in Xcode to the watch app, and ran it, and for whatever reason it installed and launched properly on my watch. First time this worked in Xcode 14.

Me too. I never used this before, and am trying to port an existing iOS app, that plays music, to macOS. It seems that MediaPlayerItem etc APIs are not available on macOS so I am now trying out Mac Catalyst. Most of things seem to work well but when it comes to playing back music content (via Apple Music), I get this same error.

I bumped into the same problem. Working on an app, but before I can get it into a remotely releasable state I see no reason to pay for a development program. Work first, pay day later!

Thanks but it seems you just linked to sandbox settings when I'm looking for settings and/or information regarding the subscription times when using subscription testing in code.