In one of the biggest developer-hostile moves I've ever seen from Apple, mid-release-cycle, on a minor version update only, Apple have: Not allowed XCode 14.2 to work with iOS 16.4, so if you want to debug on a 16.4 device you're screwed Forced XCode 14.3 to insist on Ventura, so if you want to use Monterey you're screwed Apple continue to have no support for Music on simulator, so if you want to debug on sim you've always been screwed. To give an example of why I don't want to ruin my machine with Ventura: I do a lot of web stuff, and that uses GIFs amongst other image types. If I QuickLook a GIF on Ventura 13.3, QuickLook will crash. That's the quality level of Ventura. It's not fit for purpose as a daily driver for the dev work I do. Hopefully, there's plist hackery or similar that can make XCode 14.3 launch anyway? Pretty sure there's nothing in a minor version bump that needs the entire OS to be updated. So, is it possible? After all the other abuses for longevity of support (or lack thereof), lack of Apple Music APIs on macOS / Catalyst / simulator, number of bugs in it and so-on, this is just about the tipping point where - for the first time since 2008 - I drop my developer sub entirely, write off a huge number of hours of my life trying to make a music app work as total wasted time on a junk API on a crumbling OS offered by a borderline psychotic company, and run screaming from this clusterfuck into the stable API arms of Spotify & Android/Kotlin, never to return. "Frustrated" doesn't even come close.

Posting as a new thread as an update to https://developer.apple.com/forums/thread/693310?page=1#697161022 got no traction. See there for details. TL;DR - working code suddenly starts getting a 500 response from the Apple Music back-end; new tokens etc. don't help. Previous resolution came from Apple, claiming a server fault was to blame. Just me, or are others seeing this fault now recurring?