@joshgrant All I've found in iOS 18 is even more bugs. The most bizarre of these is that when calling "play" on the application player, it plays for about half a second then self-enters the INTERRUPTED state. For good measure, the event is sent twice. This event is documented as being used for an incoming call. Yeah. Right. Obviously, there's no incoming call. Icing on the cake to get sent the event twice in rapid succession. My application is now incapable of starting music playback when it starts up. The user must un-pause manually. And then, you have all the same nonsense with detecting end-of-playback, after several years. Further, previous heuristics now have more "undetected end" bugs arising so even more problems exist with iOS 18 that I have yet to track down. I think this speaks for itself in terms of software quality and Apple's attitude to developers - total contempt. Other platforms are less hassle, cheaper to develop on and have a bigger user base.

So here we are, another year goes by, another new operating system release and no fix. Apple have abandoned developers for Music; the API where implemented is incredibly unreliable with basic design frustrations all over it, while the vendor-provided applications are rife with bugs and bewildering, inconsistent UI design and navigation choices. Apple doesn't care. I'm abandoning Apple Music in all application development from this point and moving it to Spotify, and will be recommending Spotify as a preferred service henceforth.

Was answered in that other thread - another server-side problem that Apple fixed a couple of days later.

This issue has recurred. Previously working integrations with new developer tokens are return 500 responses. I even tried issuing myself an entirely new API key and unfortunately it still returns 500 responses. New Zealand region, if it makes a difference. Apple service status page shows all-green. It is a little disappointing that the API, the most mission critical interface for any developer, should break in this way just one month ago, then break again in apparently the same way just a few weeks later. This breaks the world for music apps. It makes developers of iOS music apps look like idiots, with frustrated users who cannot be given a good answer on what's gone wrong or when it'll be resolved. When will this be fixed, please, and what steps are Apple taking to ensure that this does not break without Apple noticing again in future (e.g. ensuring that the Apple Service Status page correctly reflects a broken API condition)? Thanks,